View source for Talk:Tron
|Thread title||Replies||Last modified|
|Tron 3.11 seems broken in current Robocode/Java versions?||6||10:07, 19 June 2021|
|Diagonal Movement||3||23:16, 1 August 2017|
I'm unsure why, but I'm noticing that Tron 3.11 is currently broken under Robocode 184.108.40.206 and OpenJDK 11. It seems to always start up in "Reference" or "Challenge" mode, never in "Normal" mode. This is the reason for Tron's recent underperformance against updated/new rumble entrants. Need to figure out the cause of this. There's a good chance this could point to a regression in Robocode.
UPDATE: Confirmed that Tron is working fine in 220.127.116.11 and 18.104.22.168, but not in Robocode 22.214.171.124. This is unfortunate and I doubt Tron is truly the only bot affected.
Looks like there's some incompatible change in the logic of robot name in 126.96.36.199, and anything depend on that is broken to some degree. This frequently happens to bots with Team capacity.
Every single bot now receives a "($i)" suffix where i is absolute index of all robots. The suffix was only added to bots with same name and was related to the specific bot. This change breaks the way some Team bots know which is leader (an example of depending on undocumented feature). Team battles should be partially broken now, so does some of the bots with Team capacity.
I've ran some tests and confirmed that Tron's change in behaviour seems to be a rather troublesome side-effect of the change in what getName() returns.
To confirm this, I repackaged Tron with " (1)" added to it's version field, and it misbehaved in even in 188.8.131.52, in the same manner the regular version misbehaves in 184.108.40.206.
It's rather strange that " (1)" appended to the end of getName() causes problems for Tron, because neither "*" appended nor " (1)*" appended does.
Considering this further, I believe the most likely thing is that ABC was using the result of getName() specifically to detect the special case of multiple instances of Tron versus itself, to behave in a special way for development purposes in that scenario.
Most team bots used the suffix to determine a "leader"? Curious. Most teams I spent time looking at either did not have an explicit leader, or were using a different bot class for that.
In any case, this change in what getName() returns really breaks too many things in my opinion.
I am using the bot name suffix to determine the position of current bot in the team, as well as switching colors. Not remembering where did I see someone using similar tricks. Anyway anything like this now breaks.
I'm very strongly of the opinion the change to what getName() returns should be reversed. Even if the new numbering is used for display or internals, it just breaks too much to return to bots in getName(). It seems there are too many historic bots that are broken even in 1v1, that are more or less infeasible to update, and we may never really be certain if we've found all of them that may be affected. It's very possible some changes in bot behavior may not be immediately obvious.
Why doesn't Tron use Diagonal Movement instead of Orthogonal Movement when doing so will multiply speed by the square root of 2
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.Dsekercioglu (talk)
Return to Thread:Talk:Tron/Diagonal Movement/reply.
Actually it would slow him down because wall smoothing would become harder. That's why Trons uses Orthogonal Movement.