Difference between revisions of "Thread:Talk:LiteRumble/Some scores in TwinDuel have shifted a lot/reply"

From Robowiki
Jump to navigation Jump to search
 
m (Teams were broken from 1.9.3.8 to 1.9.4.1)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
To update, some change between Robocode versions has *severely* broken LunarTwins. LunarLeader is now going after it's own LunarRover droid, which is absolutely didn't do in older versions.
+
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.
  
Need to figure out what's broken in Robocode 1.9.3.9, and depending on what it is (i.e. could if have affected any other bots in TwinDuel/TeamRumble) we may want to clear results from those versions in the LiteRumble server if possible.
+
This bug appears to have been introduced to 1.9.3.8 as a side effect of the fix to [https://sourceforge.net/p/robocode/bugs/412/ this bug].
 +
 
 +
[https://github.com/robo-code/robocode/blob/master/versions.md#version-1942-10-05-2021 Version 1.9.4.2] fixes a bug with getTeammates/isTeammate.
 +
 
 +
So [[User:Skilgannon|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. :)

Latest revision as of 23:07, 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. :)