Thread history
Viewing a history listing
| Time | User | Activity | Comment |
|---|---|---|---|
| 17:45, 26 June 2012 | Wompi (talk | contribs) | New reply created | (Reply to Rumble Client 1.7.3.2 vs 1.7.3.0) |
| 17:30, 26 June 2012 | Voidious (talk | contribs) | New reply created | (Reply to Rumble Client 1.7.3.2 vs 1.7.3.0) |
| 17:27, 26 June 2012 | Wompi (talk | contribs) | New reply created | (Reply to Rumble Client 1.7.3.2 vs 1.7.3.0) |
| 15:35, 26 June 2012 | MN (talk | contribs) | New reply created | (Reply to Rumble Client 1.7.3.2 vs 1.7.3.0) |
| 10:59, 26 June 2012 | Wompi (talk | contribs) | New thread created |
Hi mates. I recently spotted some robots that might only work well under 1.7.3.2 (Wolverine, Tachikoma) and i'm not sure how to deal with it. By now the score of these bots are dependent of the contribution version and this inflicts the overall score i guess. I'm running on 1.7.3.2 and mainly contributed to MeleeRumble so i guess all my results vs those bots are ok. On the other hand KID_RINZLER (the new main contributor, great job btw.) is running 1.7.3.0 and now these bots get worse. So the overall ranking now depends a little on how many games vs those bots my client (MN as well) picks and i'm quite unhappy with it. What do you think is the best way to handle this. I guess the best solution would be to change the RumbleServer to 1.7.3.6 but until Darkcanuck find the time to do this could we maybe think of a quick fix somehow.
Take Care
The quick fix would be making bots compatible with Robocode 1.7.3.0 and Java 1.5.
Usually, bots which are incompatible with the official versions in the rumble are removed from the participants list.
I dont think the rules are 1.7.3.0 only. Or did i miss something? Otherwise this would be a big surprise to me because i build my bots on 1.7.3.6 and have no idea what methods 1.7.3.0 supports and what not.
It seems very strange, especially considering Wolverine is an ancient bot. There should be no rule or API changes between those versions. If those bots are unstable, I guess I'd vote to remove them, at least temporarily until we can figure out what's up.
For some open source bots like SilverSurfer, people have fixed issues introduced by new versions of Robocode and posted the fix to the rumble, which is a cool solution when possible.
Wolverine is open source and he uses get...Events() to utilize his bot instead of overloaded eventMethods. My guess is, this is the issue somewhere between the versions. I only can say that every result uploaded by an 1.7.3.2 client leads to good behavior and 1.7.3.0 leads to "sitting duck" the bot.
Its up to you Voidious to remove the bots, i think it concerns you the most. Because Diamond would jump up and down his rankings. I personally don't care that much for now - they are not my weight class.
