Problem bots from Literumble
← Thread:Talk:Diamond/Version History/Problem bots from Literumble
Hey, I just thought you should know that the Literumble pairings are just about complete (which is where all of my CPU cycles have been going).
It seems that both of us have very low scores against rtk.Tachikoma. Something to look into.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page.
Return to Thread:Talk:Diamond/Version History/Problem bots from Literumble/reply.
Cool, thanks for the heads up! I think this will be a great way to find bots to improve against.
Could the Tachikoma thing be a discrepancy in Robocode versions? Are you using 1.7.3.0 or something newer?
It could be. I'm running 1.7.4.2 Alpha2 at the moment as it accepts gzip/deflate encoded data for the rumble and helps cut down on my bandwidth. A lot of the earlier results are from 1.7.3.0 though, so it could be related.
Some quick tests show that DrussGT typically gets 80-85% on my 1.7.3.2 dev Robocode, so it seems the the results on Darkcanuck's server are a bit odd... I see in it's Tachikoma.properties file it is built for 1.7.3.2, but I don't think that could be giving it bad battles on 1.7.3.0.
Here is a more telling result: Tachikoma details sorted by date. Scroll down and keep an eye on the survival. Only the latest battles have any survival at all. The time they started getting survival corresponds with the time I switched my clients from 1.7.3.0 to 1.7.4.2_A2. So it seems it is a client issue.
I recall Wompi discovered some bots acting differently from 1.7.3.0 to 1.7.3.2. I'd forgotten, but Tachikoma was one of them: Talk:RoboRumble#Rumble_Client_1.7.3.2_vs_1.7.3.0_1092.
