Robocode

File Release Notes and Changelog

Release Name: 1.4.7

Notes:


Changes:
Version 1.4.7
(10/09/2007)
o Bugfixes
  -- Some robots did not receive any score even though they won the battle due
     to Robocode did not always detect correctly that the robot's thread(s)
     had been properly terminated.
     -- Thanks goes to Eric Simonton, David Alves, and "AaronR" for help solving
        this issue!
  -- Teams located in the .robotcache dir were still put into the robot.database
     file. Thus, these teams located in the .robotcache dir were shown in the
     New Battle dialog
  -- When stopping a battle while recording was enabled and then replaying the
     recorded battle, Robocode would show the last rounds of the battle even
     though no recording occurred for these rounds, i.e. "ghost" rounds
  -- When using the -battle option Robocode would run at full speed, i.e. the TPS
     set to maximum, even though the GUI was enabled with a predefined TPS
     -- Now, the TPS is only set to maximum when the -nodisplay option is used
  -- Robocode was wasting time on trying to wake up robots that was dead
     -- Robocode was blocked for the amount of milliseconds specified by the CPU
        constant when a robot was killed in a battle, as Robocode was waiting for
        the dead robot to wake up for exactly this amount of time
o Robocode changes
  -- The Stop button is now only enabled when a battle is running and disabled
     afterwards
  -- When starting Robocode, and the saved window locations (x and y coordinate)
     of a window does not fit into any of the available screens/displays (e.g.
     virtual desktop), when Robocode will center that window into the current
     screen displayed 
o RoboRumble changes
  -- The configurations files roborumble.txt, meleerumble.txt, and teamrumble.txt
     have been improved:
     -- All properties are now documented and have been grouped more logically.
     -- The BATTLESPERBOT property has been raised to 2000 for the RoboRumble
        and MeleeRumble
  -- An exclude filter has now been added, which makes it possible to exclude
     participants that causes trouble somehow
     -- The exclude filter is controlled using the new EXCLUDE property, which
        takes a comma-separate list of participants where the wildcards * and ?
        can be used
     -- Excluded participants are not added to the participants file, and will
        not be downloaded or take part in battles