archive by month
Skip to content

updated bot RedRum

The first upload of RedRum was identical in play to Steamhammer 2.3 playing terran. Since then it has been updated with changes, so I took a second look. Curiously, though the bot’s idea of its own name has been updated from SteamRoll to RedRum, it still gives its version as 0.1.

The RedRum version uploaded on 4 May had complete map information mistakenly turned on. SSCAIT software did not notice, but stream watchers noticed quickly because a debug option to draw enemy unit locations was turned on. Nobody who was actively trying to cheat would turn on both options at the same time, so it truly was a mistake. Still, it makes me wonder whether any other SSCAIT bots have complete map information turned on, whatever the reason. A corrected version of RedRum was uploaded the next day, on 5 May (the complete map information setting was the only difference between the uploads). Has SSCAIT fixed their side of the error yet? [Fixed on 11 May.] The tournament manager can and should flag that setting.

Compared to Steamhammer, RedRum makes no important changes to the configuration file—it sets bot info like the name and it sets different debug options. The opening book is unchanged. RedRum’s DLL file is microscopically shorter than Steamhammer’s, 512 bytes or about 0.05%. I speculate that it may delete a small amount of code that terran does not need (there is plenty more). It’s unlikely that it deleted a lot of code and also added a lot; we’d probably see a bigger size difference.

I played a few test games to see if I could spot changes. I set Steamhammer and RedRum to play identical terran openings, to help small differences stand out. I noticed that RedRum always claims that its opening is “enemy specific”, though I set it myself and it was not. I thought there might be a difference in the SCV scout’s behavior when it reached the enemy base. And attack/retreat decisions seemed a little sharper; maybe that has been improved. Other than that I could not spot any difference. But then, I know from experience that play differences are quite hard to find by eye. I could have misinterpreted game events as skill differences, and I could easily have overlooked other differences in play.

Still, RedRum remains very similar to Steamhammer terran. In the first test game, the initial vultures met in the center of the map and fired on each other simultaneously, and the build orders remained identical until deep into the game. That’s natural, of course; it takes time to make substantial changes.

It’s good that we’re getting at least some new bots. I have the idea that Ayran Olckers, author of RedRum, is still at the exploring stage, trying to get a firm grip on things. Bigger changes may be coming—the 0.1 version number at least says so.

Trackbacks

No Trackbacks

Comments

krasi0 on :

CMI was only possible on SSCAIT (due to a bug in the TM) with BWAPI 4.1.2 so the only potential cheating suspects would be bots using that one *older* BWAPI version.

GL to the author of RedRum and let's finally see a great Terran bot of the SH heritage! :)

Joseph Huang on :

So it won't be fixed?

krasi0 on :

No, it does not mean that. Your "interpretation" is wrong

Joseph Huang on :

Well no fix for Chrome out of memory error or DLL mismatch....

krasi0 on :

The 4.1.2 TM bug that didn't disallow CMI has been fixed today thanks to Quatari. :)

Jay, please mention it in somewhere your newest post in case people are no longer monitoring this post's comments.

Jay Scott on :

I updated this post to mention it.

Antiga / Iruian on :

It's another reason added to the list why I'm requiring 4.4 or later for AIST S3 in the spring of next year. Alot of the older BWAPI versions have competitive issues that are fixed in the more recent releases.

Dan on :

I don't think BWAPI version has anything to do with this -- if the tournament module was bugged then the BWAPI version shouldn't matter.

Joseph Huang on :

No timing for client bots is fixed in 4.4 tho.

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.