CIG 2019

For anyone who hasn’t noticed, the CIG 2019 tournament is announced. The key info:

Registration date: 17 June
Submission date: 10 July
BWAPI versions: 3.7.4, 4.1.2, 4.2.0, 4.4.0
Latency setting: LF6 (“Fastest”)

As I hoped and expected, they are supporting the latest BWAPI 4.4.0.

Last year, CIG 2018 had some issues. (Note: One item I listed as a tournament issue, Ziabot’s problem, was likely Ziabot’s own doing, and the build order breakdowns were apparently due to the LF6 latency setting that bots were supposed to be ready for, and can also blamed on the contenders—though you have to wonder why they decided to change the ground under the feet of returning bots.) The build order breakdowns affected Steamhammer and messed up its play in every game. Making the debacle worse, Steamhammer suffered a severe crashing bug, which was of course on me. All in all, it left me with an impression of unfairness and it was not a fun experience. I’m not inclined to play in CIG this year.

I do expect to analyze the results, though. If all goes well, maybe next year.

Trackbacks

No Trackbacks

Comments

Tully Elliston on Thursday, April 4. 2019:

That's a shame that you won't contend because of your bad experience last time, is the LF6 latency setting in place again this year? I'd hope you would re-consider, its a small community and every bot taking part in these events makes them more interesting, and its enjoyable to track SH performance against the field.

Jay Scott on Thursday, April 4. 2019:

Yes, it is LF6 again this year in the rules.

MicroDK on Friday, April 5. 2019:

The only thing CIG could be blamed for was isues with learning data for some bots... was SH affected by that?

Jay Scott on Friday, April 5. 2019:

No, the issue that was unambiguously theirs did not affect Steamhammer. I also blame them for not explaining how to set up the execute file for EXE bots. Authors had to get it right and had no guidance on how to get it right; with more info, not so many would have gone wrong.

Add Comment

Name*

Homepage

Comment*

In reply to

E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA