Some scores in TwinDuel have shifted a lot
I'm noticing that some of LunarTwins' scores in TwinDuel have shifted dramatically from what they were as of RumbleArchives:TwinDuelRumble_20200126, despite the robots involved in said pairings not having been updated since. Particularly versus the following four:
- bvh.two.Valkiries 0.44tmk3b
- bvh.two.Ravens 0.2
- gh.twin.GrauwuarG 0.41
- krillr.mini.JointStrikeForce 2.0c
which are four bots that have been unchanged since 20200126, that LunarTwins used to win decisively against, but appears to no longer do so in the TwinDuel LiteRumble. Also appears those for some reason appear to have had their pairing count versus LunarTwins reset more recently than some others for some unknown reason? Not sure. I'll be looking into it more some time, but it makes me wonder if this was due a change in robocode version.
To update, it seems robocode version 188.8.131.52 through 184.108.40.206 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 220.127.116.11 as a side effect of the fix to this bug.
Version 18.104.22.168 fixes a bug with getTeammates/isTeammate.
So Skilgannon if you're reading this, we should probably update the literumble version to 22.214.171.124, 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 126.96.36.199 to 188.8.131.52 in LiteRumble, it looks like it's just the 184.108.40.206 results that need to be cleared from TeamRumble/TwinDuel pairing data. :)
So, while updating to 220.127.116.11 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 18.104.22.168 and Robocode 22.214.171.124 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.