archive by month
Skip to content

CIG 2018 - Overkill was broken

Did Overkill actually perform much worse in CIG 2018 than in past years? Here are the bots carried over from 2017 to 2018, with win rates in both years, with numbers from the official results. We see that Overkill collapsed in win rate from 2017 to 2018, a far bigger change than any other bot. Iron performed poorly in 2017 because it failed on the map Hitchhiker. Other bots mostly had modestly lower win rates in the stronger field this year. My 2017 crosstable was calculated from the detailed results, which included some corrupted data and are a little different from the official results—except for Sling, which was a lot different: 26.07% in 2017 versus its official 18.08%, reducing its year-over-year difference.

bot20172018
UAlbertaBot65.59%60.58%
Overkill62.75%34.68%
Ziabot61.75%51.08%
Iron61.62%74.31%
Aiur59.83%51.54%
TerranUAB36.78%34.40%
SRbotOne34.14%24.37%
OpprimoBot30.69%27.11%
Bonjwa30.67%23.57%
Sling18.08%26.52%
Salsa4.64%1.54%

Was the difference due to the maps? N0. In 2017, Overkill scored 57% or more on every map (CIG 2017 bots x maps). In 2018, Overkill scored 38% or below on every map (official results). And 3 of the 5 maps were the same: Tau Cross, Andromeda, and Python.

Did they run different versions of Overkill? The source that they distributed for Overkill is identical in both years. Theoretically they might have run something different by mistake—but it produced the expected files in the write directory, so it would be a surprise.

Finally I downloaded the Overkill replays and watched some. The poor bot’s build orders were severely distorted, skipping over drones and buildings. It would do things like take gas on 7 and then stop all construction, or follow a normal-ish build but drop many drones so that its economy was anemic. Sometimes drones moved erratically instead of mining. It looked similar to play I’ve seen from Steamhammer when latency stuff is way out of whack. Of the games I looked at, some were hopelessly muddled, some were close to normal with only occasional dropped drones, and none were 100% good. I don’t know what the problem was, something corrupted or a server setting that Overkill could not cope with, but whatever it was, Overkill was badly broken and far short of its normal strength.

43864-OVER_ZIAB.REP (Overkill’s last game of the tournament) is an example replay that shows the problems.

It’s possible that some other bots may have been affected. If the difference was in a server setting that Overkill was not ready for, then it would be surprising if every other bot was ready.

Trackbacks

No Trackbacks

Comments

Dan on :

CIG was run on LF6 this year. Perhaps it was run on LF3 in previous years?

Dan on :

Changes to the TM setting which controls whether bots can disable latcom could also cause issues like this. Potentially also a switch between BWAPI 3.7.4 3.7.5 (though I'm not at all familiar with the differences between the two).

Jay Scott on :

Your suggestions make perfect sense—a change to latency settings seems like a strong candidate for the difference. But close relative UAlbertaBot was apparently not affected, which makes me wonder. Has anybody found another bot which was affected?

MicroDK on :

I think LF6 (fastest speed) could be the reason like you mention. You can try to replicate this running some games with sc-docker. Run headless to get LF6 and run with showall to get LF3. Overkill could have been changed enough so it effects it more than UAB.

Add Comment

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

Form options

Submitted comments will be subject to moderation before being displayed.