Thread history

From Talk:LiteRumble
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
21:40, 13 June 2021 Rednaxela (talk | contribs) New thread created  
21:44, 13 June 2021 Rednaxela (talk | contribs) Comment text edited (clarify)
22:28, 13 June 2021 Rednaxela (talk | contribs) New reply created (Reply to Some scores in TwinDuel have shifted a lot)
22:34, 13 June 2021 Rednaxela (talk | contribs) Comment text edited (Ah, 1.9.4.2 fixes a relevant sounding bug...)
23:07, 13 June 2021 Rednaxela (talk | contribs) Comment text edited (Teams were broken from 1.9.3.8 to 1.9.4.1)
23:34, 13 June 2021 Skilgannon (talk | contribs) New reply created (Reply to Some scores in TwinDuel have shifted a lot)
23:37, 13 June 2021 Rednaxela (talk | contribs) New reply created (Reply to Some scores in TwinDuel have shifted a lot)
05:13, 19 June 2021 Rednaxela (talk | contribs) New reply created (Reply to Some scores in TwinDuel have shifted a lot)
05:15, 19 June 2021 Rednaxela (talk | contribs) Comment text edited (revise comment)
05:49, 19 June 2021 Rednaxela (talk | contribs) Comment text edited (Ticket link)

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.

Rednaxela (talk)21:40, 13 June 2021

To update, it seems robocode version 1.9.3.8 through 1.9.4.1 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 1.9.3.8 as a side effect of the fix to this bug.

Version 1.9.4.2 fixes a bug with getTeammates/isTeammate.

So Skilgannon if you're reading this, we should probably update the literumble version to 1.9.4.2, 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 1.9.3.5 to 1.9.3.9 in LiteRumble, it looks like it's just the 1.9.3.9 results that need to be cleared from TeamRumble/TwinDuel pairing data. :)

Rednaxela (talk)22:28, 13 June 2021

Rumble is updated to only accept 1.9.4.2. I will wipe the Team / TwinDuel, unfortunately they aren't stored by upload version.

Skilgannon (talk)23:34, 13 June 2021

Thanks for the prompt response! Should be able to get the pairings built back up again pretty quick I think.

Rednaxela (talk)23:37, 13 June 2021
 
 

So, while updating to 1.9.4.2 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 1.9.4.1 and Robocode 1.9.4.2 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

Rednaxela (talk)05:13, 19 June 2021