Robocode 1.7.1.6 Beta

This is a maintenance release of Robocode with the bug fixes and changes described below.

Bugfixes

• Bug [2897215] - Robot Editor doesn't accept packagename with dot (.) in it.


• Bug [2876395] - Source is not included.


• Bug [2867326] - Lockup on start if too many bots in robots dir (cont'd).

Requests

• Req [2641759] - Scrollable properties. All console windows including the Robot Console and Properties are now scrollable, and all have the same look.

Changes

• It is now possible to add paths to robot project inside an Eclipse workspace under the Development Options in the Preferences. Robocode will read the .classpath file in the project in order to locate both class files, properties files, and java files. This means that the Robot Packager is now able to include your source files when you use Eclipse, and it supports multiple source paths. Notice that Robocode does not support linked sources or include and exclude filters.


• Changed the messages given when creating a new robot with the Robot Editor regarding robot name and package name.

Download Robocode 1.7.1.6 Beta from here

Robocode 1.7.1.5

This is the final release of 1.7.1.5 that fixes two bugs compared to the beta version.

Bugfixes

• RobocodeFileOutputStream.getName() always returned null instead of the filename.


• Robots listed in e.g. the New Battle window was sorted like: 1.1.1, 1.1.10y, 1.1.2, 1.1.10 (alpha-numerical). But version numbers with an ending letter like in "1.1.10y" like in the versions just listed, were not placed in the correct order. Notice that 1.1.10y is between 1.1.1 and 1.1.2. This bug has been fixed so the versions in the example now will be sorted correctly like: 1.1.1, 1.1.2, 1.1.10, 1.1.10y

Download Robocode 1.7.1.5 from here

Robocode 1.7.1.5 Beta

This is a maintenance release of Robocode, which fixes the bugs below.

Bugfixes

• Bug [2871138] - Graphics2D.getTransform() throws NPE


• Bug [2872781] - "Teleport" - occurs when robot's distance remaining is very large


• Bug [2876395] - Source is not included, robot.java.source.included was not set

Download Robocode 1.7.1.5 Beta from here

How do you test your robot ?

Philip Johnson from University of Hawaii uses Robocode in his computer science course.

He came with idea of unit testing Robocode robots and prepared excellent video guide to show you how to do that.

He reused our implementation of RobotTestBed, which we use to test Robocode engine. We will be working with him to include his idea. Probably as downloadable Robocode extension package.

Code and more could be found in pmj-dacruzer project

Enjoy this great stuff!

Robocode 1.7.1.4

This final version 1.7.1.4 is dedicated for the RoboRumble@Home community where many issues seen with the RoboRumble client have been solved.

In the following the bug fixes and changes compared to the 1.7.1.4 Beta are listed.

Bugfixes

• Bug [2845608] - java.io.FileNotFoundException in RobotFileSystemManager.init


• Bug [2845612] - Can't load Katana 1.0 or DrussGT 1.3.1wilo


• Bug [2854692] - Lockup on start if too many bots in robots dir


• Bug [2852860] - IllegalArgumentException on painting in some robots


• Fixed NullPointerException that could occur with the -battle command-line option

Changes

Banning

• The previous 1.7.x.x versions have been very strict so that robots that could not be loaded, started, skipped too many turns etc. would be disallowed to participate in battles. With the bugfix for bug [2845612] above this policy has been changed so robots are only "banned" if the cause a security violation or they could not be loaded or started (meaning that they are not able to run). In addition, ALL security violations are always written out in both the main console and robot's console. A message will be written out in the main console like "xxx has caused a security violation. This robot has been banned and will not be allowed to participate in battles".

Painting

• With the bugfix for bug [2852860] a change was made so a robot will now receive this message in its console window, if it is painting too much between actions:
  "SYSTEM: This robot is painting too much between actions. Max. capacity has been reached."

• Notice that a robot is not allowed to perform an unlimited amount of paint operations for two reasons:


1. It takes up a lot of memory as the painting operations are recorded in a buffer before being processed, and potentially this buffer must be recorded to a file (for replays). A robot is allowed to use up to a maximum of 64 KB per action. An average painting operation like e.g. fillRect(x, y, width, height) takes up 15 bytes, meaning that more 4000 painting operations should be possible, which is a lot.


2. It takes a lot of CPU cycles to process the painting buffer to the display making the painting slow if the buffer is too large.




• It is possible to remove the limit of the robots painting buffer by using the command-line option: -Ddebug=true

Download Robocode 1.7.1.4 from here

Robocode 1.7.1.4 Beta

This version is dedicated for the RoboRumble@Home community where many issues seen with the RoboRumble client have been solved.
Thank you all for reporting as many known issues as possible, and also help out solving these - especially with the issue seen with the robot movement that had a big impact on the scores and rankings! :-)

A big thanks goes to Patrick Cupka ("Voidious"), Julian Kent ("Skilgannon"), "Positive" and Nat Pavasant ("Nat") for their combined work with developing and testing the new and improved robot movement regarding acceleration and deceleration rules (Bug [2828072]). :-)

Bugfixes

• Bug [2828072] - Accel/decel rules introduced in 1.7.1.3 causes trouble.


• Bug [2828479] - Missed onRobotDeath events.


• Bug [2819387] - Team jar files reported as corrupted.


• Bug [2809518] - Does not extract .properties files into bot data dir. This fix did not work properly as the file sizes were truncated to 0 bytes.


• Bug [2828614] - Sometimes too few results for robots are displayed.


• Bug [2820434] - NullPointerException when setting classpath directory.


• Bug [2811621] - Invalid entry point in codesize-1.1.jar.


• Bug [2833271] - IllegalThreadStateException occurring in RoboRumble.


• Bug [2831201] - Robocode enters infinite loop with the Restart button.


• The RateControlRobot (Beta) returned rates in radians instead of degrees with the methods: getTurnRate(), getGunRotationRate(), and getRadarRotationRate().

Changes for RoboRumble

• Updated the PARTICIPANTSURL in the roborumble.txt, meleerumble.txt, and teamrumble.txt

Download Robocode 1.7.1.4 Beta from here

Robocode 1.7.1.3

This version is a maintenance release of Robocode fixing more bugs.

Bugfixes

• Bug [2813513] - Bullet and Ram Damage Bonuses are wrong.


• Bug [2809518] - Does not extract .properties files into bot data dir.


• Bug [2805858] - Access denied javax.swing -DNOSECURITY=true


• Sometimes the "Show results when battle(s) ends" in the Common Options was disabled when running the RobocodeEngine, even though the setting had been enabled earlier.


• Bug [2811621] - Invalid entry point in codesize-1.1.jar.


• A NullPointerException occurred when closing the Preferences window, when no sound device is present in the system.

Changes

• The default font on the Graphics context when using onPaint(Graphics2D) or getGraphics() has been changed to the "Dialog" font.

Download Robocode 1.7.1.3 from here