Some scores in TwinDuel have shifted a lot
You do not have permission to edit this page, for the following reasons:
- The action you have requested is limited to users in the group: Users.
- You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.
You can view and copy the source of this page.
To update, it seems robocode version 220.127.116.11 through 18.104.22.168 had entirely broken getTeammates/isTeammate, which breaks various TeamRumble/LiteRumble bots, including but surely not limited to LunarTwins.
This bug appears to have been introduced to 22.214.171.124 as a side effect of the fix to this bug.
Version 126.96.36.199 fixes a bug with getTeammates/isTeammate.
So Skilgannon if you're reading this, we should probably update the literumble version to 188.8.131.52, and also clear all TeamRumble/TwinDuel pairing data that was from a client with one of the flawed versions. Given things appear to have went from 184.108.40.206 to 220.127.116.11 in LiteRumble, it looks like it's just the 18.104.22.168 results that need to be cleared from TeamRumble/TwinDuel pairing data. :)
Rumble is updated to only accept 22.214.171.124. I will wipe the Team / TwinDuel, unfortunately they aren't stored by upload version.
So, while updating to 126.96.36.199 fixed a badly broken TeamBot situation, it introduced a new problem that I first noticed with Tron. The precise cause is unclear to me at present and can't debug into a closed bot that isn't giving a stack trace, but some change between Robocode 188.8.131.52 and Robocode 184.108.40.206 appears to have broken bots that load data files that come preloaded in their JAR files. In the case of Tron this is used for a configuration properties file, and being unable to load this is causing Tron to start in challenge/reference mode instead of normal mode.
I'm doubtful this bug only affects Tron, and removing tainted data from the rumble could be troublesome.
Bug report: here