Difference between revisions of "Thread:Talk:Tron/Tron 3.11 seems broken in current Robocode/Java versions?/reply (3)"
m |
|||
Line 1: | Line 1: | ||
− | I've | + | 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 | + | To confirm this, I repackaged Tron with " (1)" added to it's version field, and it misbehaved in even in 1.9.4.1, in the same manner the regular version misbehaves in 1.9.4.2. |
It's rather strange that " (1)" appended to the end of getName() causes problems for Tron, because neither "*" appended nor " (1)*" appended does. | It's rather strange that " (1)" appended to the end of getName() causes problems for Tron, because neither "*" appended nor " (1)*" appended does. |
Latest revision as of 09:51, 19 June 2021
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 1.9.4.1, in the same manner the regular version misbehaves in 1.9.4.2.
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.