Robocode News

Robocode 1.7.1.3

2009-07-08T15:05:00.000-07:00

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

Robocode 1.7.1.3 Beta

2009-06-08T14:10:00.000-07:00

Please welcome a new robot type, the RateControlRobot. This new robot type has been provided by Joshua Galecki and is an extension of the AdvancedRobot. Currently, the RateControlRobot is in its Beta stage.

The RateControlRobot class has been created in an attempt to allow more realistic robots. That is, many real/physical robots are given commands in terms of rates ("move forward one meter per second"). Hence, the RateControlRobot helps simulating a real robot.

The RateControlRobot provides these new methods:

setVelocityRate(double)

setTurnRate(double)

setGunTurnRate(double)

setRadarTurnRate(double)

These methods overrides setAhead(),setBack(), setTurnRight(), setTurnGunLeft() etc.

For an example, please look into the source code for the new sample.VelociRobot.

We ask the community for feedback for the new RateControlRobot and we will announce it as stable in one of next major releases. So please report issues or change requests etc. for this new robot type.

Bugfixes

AdvancedRobot.setMaxTurnRate() did not work properly since version 1.5.4

Bug [2799165] - Wrong survival scores sent by rumble client

Bug [2802227] - Funny behaviors with robot graphics/paintings

Changes for RoboRumble

Added validation of each of the participant lines of the participant list. If a participant line is invalid due to e.g. wrong format/syntax or bad URL, then an error message is written out and the participant is ignored.

The format of the lines in the participant lines is the same as usual.

Accepted lines must follow this format: {robot+version},({http-url}|{repository-id}), where {robot+version} must match the regular expression "[\\w\\.]+[ ][\\w\\.-]+", the {http-url} must be a HTTP URL pointing at the robot .jar file, and the {repository-id} must be a number. The {http-url} and {repository-id} are mutual exclusive. Example of accepted lines:

johndoe.SomeRobot 1.0,http://somewhere.com/SomeRobot_1_0.jar

johndoe.SomeRobot 1.0,321

Removed the info message "Trying to download {botname}" from the console output.

Other changes

The Development Options has become more usable, as Ruben Moreno Montoliu has added a list of paths and buttons for adding and removing directories, full resizable.

Updated the javadoc with a note for the setAdjust*() robot methods, which are ignored when turning with infinite values.

Download Robocode 1.7.1.3 Beta from here

Robocode 1.7.1.2

2009-05-24T15:26:00.000-07:00

With this release some additional bugs have been eliminated compared to the beta version.

Bugfixes

Bug [2791007] - FontMetrics StackOverflowError

Bug [2791010] - Graphics2D.setFont() has no effect

Bug [2793464] - setMaxVelocity(lower than current) + reverse direction bug

Bug [2785448] - Wrong file path used for development bots. Refixed.

Bug [2795854] - Installer says to run robocode.jar

Bug [2795883] - Nanobot rumble not sending melee or team parameters. Thanks goes to Jerome Lavigne aka. Darkcanuck for this fix.

Fixed three bugs introduced with the Beta version found using new test units:

One bug where the speed would immediately drop to max. velocity when calling setMaxVelocity() - disregarding the acceleration and deceleration rules.

Another bug where the turn rate was a bit wrong when moving back and turning left in the same time.

A third bug where the robot continued to move backwards when it should have stopped due to setAhead(0) or setBack(0).

Download Robocode 1.7.1.2 from here

Robocode 1.7.1.2 Beta

2009-05-08T15:08:00.000-07:00

With this beta, we corrected an old bug in Robocode with the robot speed and movement in some situations when a robot is decelerating. That is, a robot would only move 99% according to it's own rules. E.g. it could end with a distance remaining on -0.2 instead of 0, it could have a velocity higher than the set max. velocity, and it could take an extra turn to stop movement when decelerating. However, these 3 caveats does not occur that often. Hence, they should not have a big impact on the robot behavior and rankings on the RoboRumble etc.

If you do experience big differences since version 1.7.1.1, then don't hesitate with contacting us with detailed information about the scenario, so it is possible for us to reproduce and fix.

Bugfixes

Bug [2077512] - Bug in RobotPeer.updateMovement? Robocode was not moving 100% according to it's own rules. Now it is.

Bug [2740708] - Fair Play! With two identical robots in a battle against each other, the first robots was much more likely to win, which was not fair.

Bug [2779557] - Client tries to remove all participants. When RoboRumble, TeamRumble, and/or MeleeRumble downloaded the participants list and did not receive a HTTP_OK or an empty list, the participants list was emptied. This caused problems with the RoboRumble server.

Bug [2785448] - Wrong file path used for development bots. Added option -DALWAYSUSECACHEFORDATA for anyone who liked it better.

Bug [2785456] - Melee rumble doesn't use "smart battles" (aka. priority battles). Thanks goes to Jerome Lavigne aka. Darkcanuck for this fix.

Fixed several ArrayOutOfBoundsExceptions occurring when starting a battle with fewer robots than a battle just played with more robots.

Changes for RoboRumble

The participants URL for RoboRumble, MeleeRumble, and TeamRumble have been updated to use the participant lists from the new RoboWiki:

RoboRumble: http://robowiki.net/w/index.php?title=RoboRumble/Participants

MeleeRumble: http://robowiki.net/w/index.php?title=RoboRumble/Participants/Melee

TeamRumble: http://robowiki.net/w/index.php?title=RoboRumble/Participants/Teams

Other changes

Updated the Help menu to point at the new RoboWiki regarding the Online Help and FAQ.

RobocodeEngine control class: Added additional runBattle() method where it is possible to specify the initial positions of the robots when starting a battle.

The about box was updated, where contributors are now written in bold and in a green color.

Download Robocode 1.7.1.2 Beta from here

Robocode 1.7.1.1

2009-04-10T14:43:00.000-07:00

With this release we have focused on eliminating as many problems seen with RoboRumble as possible. Hence, this version should hopefully prove stable as the new RoboRumble client.

Bugfixes for RoboRumble

Bug [2727675] - Meleerumble using 2 bots instead of 10. Now the MELEEBOTS (number of robots that participate in a melee battle) works as expected.

Bug [2742554] - TeamRumble uploading result for Robot instead of team.

Bug [2727667] - Not enough java memory allocated in launch scripts. The launch scripts for RoboRumble and TeamRumble were changed so it is allowed to use up to 512 MB heap memory, and MeleeRumble is allowed to use up to 1024 MB.

Bug [2740403] - EOFException during repository rebuild. Exception is now reported in a simplified way.

Bug [2742891] - JarJar multi-registration. RoboRumble was not reusing the same RobocodeEngine instance.

Other bugfixes

Bug [2627698] - pe.SandboxDT_3.02 stoped working. We had broken semantics of getTeammates() to return empty array when there is no team.

Bug [2738985] - Robocode API: Cannot subclass Event in 1.7.1.

Bug [2738993] - Errors with some robot classes when rebuilding database.

Bug [2711605] - Webpage button lay over robot description.

Bug [2723228] - Round number set by user was not saved between run.

JuniorRobot changes

Bug - The event variables scannedXXX and hitXXX on the JuniorRobot was not reset to -1 (or -99) when nothing was scanned or hit.

Bug/Req [2500129] - Prevent JuniorRobot to be unresponsive.

Change: JuniorRobot will now automatically scan for enemies when it is not moving.

Download Robocode 1.7.1.1 from here

Startup tips - harvesting from you

2009-03-25T14:17:00.000-07:00

Hi All,

We plan to implement startup tips and we are looking for good ones. I mocked up pictures of solution. We would like to implement panel with multiple fonts and links to web. It will be probably driven by XML similar to HTML, we don't have it yet, so the final solution may look different.

Now you come, we need your help. Please share your best tips with us.

You could do it by commenting here or on ticket or just send us email.

We would like to see nice, well formed, short, informative TIPs about Robocode.

Thanks !
Pavel & Flemming

Robocode 1.7.1 (final)

2009-03-24T15:39:00.000-07:00

Robocode 1.7.1 has now finally been released.

Beta releases prior to this final release:

Beta 1

Beta 2

Version 1.7.1
(24-Mar-2009)
---------------

Bugfixes

Bug [2643448] - Editor UNDO does delete the line when no is undo left.

Bug [2664844] - Editor: Find/replace dialog (set cursor position).

Bug [2699018] - roborumble.sh and teamrumble.sh were broken.

Bug [2699028] - NullPointerException in BattlesRunner.runBattlesImpl.

Bug [2703301] - Custom event priority was broken.

Changes

The New Battle dialog is now larger per default.

The layout of the View Options and Sound Options tab in the Preferences has been improved. An error dialog is shown when the input field for the desired TPS is out of range.

Download Robocode 1.7.1 (final) from here

Robocode 1.7.1 Beta 2 - few bugs left?

2009-03-11T14:07:00.000-07:00

We fixed more bugs for the version 1.7.1 Beta 2. There are a few bugs left that are not considered critical, and which will be available with the final 1.7.1 release. Please try out this version and try to find as many bugs you possible can and report issues on the tracker for Robocode.

Bugfixes

Bug [2658090] - Typing to find bot no longer works.

Bug [2666598] - API: Typo in Documentation onBulletMissed(BulletMissedEvent).

Bug [2658167] - Put back setTime() method of Event, the security is now handled other way, not by hiding the field.

Fixed the problem with loading team robots from nested .jar files.

On Ubuntu (Linux) the "Default window size" did not work properly.

Internal Changes

On SUN's JVM enabled caching of .jar files opened thru URLConnection. Solved problem with closing such files by implementing URLJarCollector.

Download Robocode 1.7.1 Beta 2 from here

Robocode 1.7.1 Beta - lots of improvements

2009-03-01T15:09:00.000-08:00

With this release we give BIG thanks to Nat Pavasant who have put in great effort in testing and finding as many bugs in Robocode as possible. He has been a great help with testing especially RoboRumble@Home functionality.

Currently, there is one known issue, which will be fixed with the next Beta or in the final release of version 1.7.1. This is critical for e.g. the TeamRumble, so please notice the known issue below.

Known issue

With this version Robocode cannot handle team packages containing robot .jar files, i.e. robot packages.

Bugfixes

Bug [2626148] - Bots referencing robocode.robocodeGL broken. Now, we are now not following refrences to robocode packages.

Bug [2626164] - Don't ever punish robots in devel directories by removing from repository.

Bug [2634807], [2632874] - Robot console was wrongly synchronized with battle.

Bug [2634123] - Robot packager can be activated once per running.

Bug [2643395] - Development robots cause problems with data files.

Bug [2628346] - A battleview size exceed 800x600 filled with black.

Bug [2618169] - NullPointerException when using -battle option from the cmd-line.

Bug [2628217] - Robot Colors don't stick between rounds.

Bug [2649954] - Open battle menu dialog is not loading robots.

The command line usage of Robocode was not printed out at all when using the -? or -help option.

New features

Added getCurrentWorkingDir() + getRobotsDir() to the robocode.control.RobocodeEngine.

Request [2446276] - Ranking Panel should be visible when Robocode is minimized. This feature has been added and it is possible to control the behavior from Common Options in the Preferences with the "Don't hide Rankings when main window is minimized", which is enabled per default.

Request [2467545] - Command Line option for saving a battle record file. Two new command line options have been added for Robocode, i.e. - record and -recordXML . The -record option records the battle as a binary and zipped battle record. Here I propose that the specified filename should is something like record.br. The -recordXML does the same as the -record option, but saves the battle record as an XML file. Here I suggest that you use a filename like record.br.xml.

Request [1749483] - Speedup time required for rebuilding robot database.

RoboRumble changes

Changed the link for http://rumble.fervir.com/rumble into http://darkcanuck.net/rumble as the RoboRumble server fervir is down and with unstable ranking. The current ranking at Darkcanuck's server is alive. Almost all clients are point to Darkcanuck's now. Hence, it is updated now.

discussion

Internal Changes

The robot repository has been updated. It is no longer extracting .jar files.

It also remembers last timestamp on file so detection of the changes is really fast. Only data files are extracted now.

Data files for non-packed robots were moved to .robotcache as well.

VersionManager is now able to detect if the Robocode version was upgraded since last run.

Blocking security issue with relative path in getDataFile() method.

Improved security in RobotClassLoader.

Reimplemented RobotPackager.

BulletSnapshot has now method getBulletId which gives identity of bullet for UI.

Download Robocode 1.7.1 Beta from here

Robocode 1.7.0.2 - fixes yet another compiler path problem

2009-02-19T14:03:00.000-08:00

Robocode 1.7.0.2 fixes a new major bug introduced with version 1.7.0.1 when trying to get rid of Bug 2597046.

Bugfixes

The fix for "Bug [2597046] Compiler classpath not quoted" backfired, as the entire text field in the window with the compiler properties would now be quoted. Hence, the compiler would not be able to compile, and it was not possible to cheage the compiler preferences from the GUI.

Download Robocode 1.7.0.2 from here

Robocode 1.7.0.1 - fixes major bug with starting Robocode

2009-02-14T14:06:00.000-08:00

Robocode 1.7.0.1 fixes a major bug that some users have experienced when trying to start Robocode.

Bugfixes

Bug [2596947] Fix needed to Robocode.bat: Some users experienced problems with starting Robocode. Hence, all startup batch and shell files for Windows, Linux, Mac OS X etc. have been corrected.

Bug [2597046] Compiler classpath not quoted: When running Robocode in a folder with spaces, the compiler classpath was not quoted. Hence, the compiler would not work.

Download Robocode 1.7.0.1 from here

Robocode 1.7 Beta 2

2009-01-26T14:23:00.000-08:00

This version contains bugfixes for bugs found in the previous 1.7 Beta.

Bugfixes

Bugfix [2527112] Ubuntu throws NullPointerException in main when trying to startup Robocode.

Bugfix [2528467] Installation fail on windows if directory contain space(s).

Changes

Improved the version checking for new Robocode versions available for download.

Download 1.7 Beta from here

Robocode 1.7 Beta - modularization

2009-01-19T15:05:00.000-08:00

This version represents a completely new infrastructure of Robocode making it easier to extend and maintain for the future, while staying 100% backward compatible. The goal of this release has been to introduce the new platform for Robocode and getting it tested carefully by the community before we add features to it for version 1.7.1 and newer.

By omitting new features, we hope that we'll be faster in locating and fixing any issues introduced with this version compared to the previous version 1.6.2. When such issues have been eliminated, we will concentrate on the new features, which includes support for more programming languages and also some of the pending feature requests reported on the SourceForge site for Robocode

Bugfixes

Bug [2497164] Spammy output on robot console windows.

Internal changes

Robocode was modularized using the dependency injection framework PicoContainer. This work includes introduction of many interfaces to existing components.

Introduced Maven2 as build setup where the whole directory layout is based on the standard Maven structure.

Rewritten the RobotClassLoader so it is able to load .jar file in the future.

Rewritten security layer to use AccessController and CodeSource for detection of trusted code.

Redesigned RobocodeProperties to SettingsManager and introduced ISettingsListener.

Implemented RbSerializer to be able to implement IPC (Inter-Process Communication) in future. This should make it possible to extend Robocode for more platforms like e.g. Microsoft .NET.

Redesigned RepositoryManager and nearby to hide implementation details.

Moved all implementation of Robocode to the package 'net.sf.robocode'. The old package 'robocode' is now used only for API to outer world in order to keep backwards compability.

Download 1.7 Beta from here

Robocode 1.6.2

2009-01-04T15:03:00.000-08:00

This is the final release of Robocode 1.6.2, which contains 3 bugfixes compared to the recent Beta 4 version.

Bugfixes

Bug [2467536] Robot name was missing when replaying XML record.

Bug [2465580] Junior Robot turnAheadRight() bug. When a JuniorRobot was calling turnAheadRight(), turnAheadLeft(), turnBackRight(), or turnBackLeft() - the following exception occurred causing the robot to be terminated: java.lang.ClassCastException: robocode.peer.proxies.StandardRobotProxy

Bug [2449081] Exception when changing between Robot to AdvancedRobot. When a robot was changed from a Robot into an AdvancedRobot and recompiled, the game would cast a ClassCastException if a battle was started or restarted including that particular robot. However, this bug did not occur with new battles where the list of robots was refreshed (by pressing Ctrl+R).

Download 1.6.2 (final) from here

Robocode 1.6.2 Beta 4

2008-12-23T14:43:00.000-08:00

With this release 5 more bugs have been fixed compared to the 1.6.2 Beta 3.

Bugfixes

Fixed the Open Battle dialog, where the robots were not being loaded, but which instead behaved the same way as the New Battle dialog.

Fixed NullPointerException with the new Record and Playback (Replay) feature, when trying to play a recorded battle.

Fixed serialization problems with scan arcs (Arc2D), when robot paintings with scan arcs are being recorded.

Fixed problem with reloading robot repository on each next battle dialog. Now the user must press Ctrl+R in order to refresh the robot repository as this is not done automatically anymore.

Fixed two ArrayIndexOutOfBoundsExceptions occurring when opening a new battle with fewer robots, when a battle with more robots are ongoing.

Download 1.6.2 Beta 4 from here

Robocode 1.6.2 Beta 3 - more bugfixes

2008-12-18T14:18:00.000-08:00

With this release 5 bugs have been fixed compared to the 1.6.2 Beta 2. In addition, new battle events and battle snapshots in the Control API have been published, i.e. in the robocode.control package, and we added missing javadocs (HTML documentation) to public Robocode API classes.

Changes

Published new battle events and battle snapshots in the Control API, i.e. in the robocode.control package.

Added missing javadocs (HTML documentation) to public Robocode API classes.

Bugfixes

The current scoring (not the total scoring) was calculated wrong from version 1.6.1. The current Ramming Kill Bonus was set to current bullet kill bonus, which gave wrong ranking in the Ranking Panel.

Bug [2410856]: wrong bullet power could be reported back from Bullet.getPower(), which could be > Rules.MAX_BULLET_POWER or < Rules.MIN_BULLET_POWER.

Bug [2405844]: gunHeat could be negative, which should never occur.

Bug [2412707]: Replay exception, where an ArrayIndexOutOfBoundsException occurred in some situations.

Fixed problem with RobocodeEngine.setVisible(true), where the RobocodeEngine would hang forever.

Download 1.6.2 Beta 3 from here

Robocode 1.6.2 Beta 2

2008-12-07T09:57:00.000-08:00

The Beta 2 release is mostly about cleanup of code and improved documentation. But there are some fixes and changes as well.

Removed _AdvancedRadiansRobot,_AdvancedRobot, and _Robot! Change renders some robots unusable, but I don't see why people inherited from that classes. We clearly indicated that they are internal and may be removed. Please discus, if you have good reason why you inherited from them in the past.

Improved compatibility with RobocodeJGAP

Development robot version names into repository

Fixed problem with Bullet identity

Fixed battle cleanup concurrency issue

Fixed problem with robots without package

Fixed AWT AppContext cleanup

Robocode 1.6.2 Beta is out

2008-11-23T07:34:00.000-08:00

We are proud to present new version of Robocode for community testing.

User visible changes

We now support excellent record/replay functionality, including export/import to XML. Record also contains paintings of robots, so you can replay them. Because recording is resource consuming, it is switched off by default, go to preferences dialog to turn it on.

In UI we have new button for main battle log, where you can watch systems messages (if you don't like to look at system console). The dialog also contains tab with XML representation of last battle frame, which might help with debugging your robot.

Robot dialog was enhanced by new tab page with dump of current robot properties. Hope you will love it, because you can add your own properties from your robot by calling setDebugProperty() method of your robot. See sample.PaintingRobot for example usage.

Robot dialog could hint which robot is trying to paint something, paint button becomes green.

Robot button was given life-bar + score-bar, so that you can easily see who is winning. You see small red bar on Corners sample button ? That's energy below 25 points. Blue bar is score.

Robot visible changes

New method setDebugProperty()

Classes of event arguments are more strict now. They are final, so you can't inherit from them, they also hide methods setPriority() and setTime() for security reasons.

Team messages are deserialized on receiver robot thread.

Robots which are wrong behaving are removed from repository and are not given other chance to run. This is for skipped turns, for unstoppable robots and for robots with class loading troubles.

During painting robots can paint only such things which are Java Serializable.

Bug fixes & Feature requests

[2214620] Robots are given unlimited time when recording, painting or debugging with -Ddebug=true

[2117285] we now upload version of client and game mode with results from roborumble

[2208374][2026098][1829282][1609494][1577588] are mostly described above

Implementation details

Communication from user robot to battle is 90% redesigned!

We use serializable messages instead of sharing and locking robot state and intentions.
We spend months to do it correct way. The presented solution was preceded by three unsuccessful trials. As reward we have cleaner architecture, less synchronization overhead, better security, better speed, code is much more readable I hope.
We have now potential to run robots in sandbox and let them communicate using IPC or over network in future versions.

The code is still in branch. We plan to merge it to trunk when we reach full release. We need YOUR feedback and testing support.

Robocode 1.6.1.4 - new maintenance release

2008-11-15T15:06:00.000-08:00

This maintenance release contains 1 new feature, 4 bug fixes, and 1 change.

Bugfixes

Loosing robots were not receiving onBattleEnded(BattleEndedEvent) events.
A new security issue fix for robots that were able to execute malicious code thru the Event Dispatch Thread (EDT).
[2210749] drawArc() does not work as expected: This bug has been fixed. In addition, both drawArc() and fillArc() are now using the Robocode coordinate and angle system.
[2157167] Blank console window when compiling. Some systems still had this issue, so a new fix has been applied.

New feature

The results and current rankings (during a battle) is now showing the score as percentage(s) in parenthesis right beside the score points like e.g. '7875 (12%)' for the total score in the results and '21 / 2900 (7 / 14%)' with the current rankings.
- Thanks goes to Endre Palatinus, Eniko Nagy, Attila Csizofszki and Laszlo Vigh for this patch/contribution!

Changes

The option EXPERIMENTAL (true/false) allowing access to the robot interface peer is now working for the RobocodeEngine class also.

Download 1.6.1.4 from here

Robocode 1.6.1.3 - maintenance release

2008-10-24T14:58:00.000-07:00

This maintenance release fixes 5 bugs and contains 2 minor changes.

Bugfixes:

[2157167] Blank console window when compiling. This bug was introduced in 1.6.1.2. When trying to compile a robot which gave a compiler error, the output console window for the compiler could be blank on Windows system, and even hang. Now the compiler error is output correctly as in previous versions.
[2070840] Roborumble "ITERATE" broken: When running RoboRumble with ITERATE=YES, DOWNLOAD=YES, and RUNONLY=SERVER, the ratings were only read once, not per iteration. This bugfix removes a very old bug and the need of using a batch file as workaround in order to do the loop with updated ratings.
[2121034] The -DROBOTPATH= option did not work: Now it works.
[2134416] Broken .sh files: An misplaced colon character was included in the teamrumble.sh file.
Fixed issue with first time access to a robot's data directory after startup, where the robot was not allowed to write to it's file.

Changes:

The list of available robots in the 'New Battle' dialog is now automatically refreshed before it is being shown, when a new robot has been compiled or a robot has been removed.
The 'Save' and 'Save As' in the File menu of the Robot Editor is now enabled and disabled depending if there is anything to save or not.

Download 1.6.1.3 from here

Robocode 1.6.1.2 - more bugfixes for 1.6.1

2008-09-12T14:26:00.000-07:00

This maintenance release fixes some critical bugs for the rankings of RoboRumble@Home.

Bugfixes for RoboRumble:

Sometimes results were given to the wrong robots, which gives a problem with the robot rankings in the RoboRumble, TeamRumble and MeleeRumble. Thanks goes to Joachim Hofer AKA Qohnil for fixing this issue! :-)
Robots that read their data file got the following error message: 'Preventing unknown thread from access: (java.io.FilePermission...'.

Other bugfixes:

ArrayOutOfBoundsException could occur when accessing the Graphics2D object returned by the getGraphics() method on the Robot.
The draw(Shape) method on the Graphics2D object returned by the getGraphics() method could not draw lines.
The onMousePressed() event was called twice instead of only one time per mouse press.

Download 1.6.1.2 from here

Robocode 1.6.1.1 - bugfixes for 1.6.1

2008-08-27T15:36:00.000-07:00

Lot's of bugfixes have been made for Robocode 1.6.1 and therefore this maintenance release has been released with the current fixes.

Bugfixes

Issues with the scoring. Sometimes the robots were ranked incorrectly compared to their total scores given in the battle results.
When disabling the security (-DNOSECURITY=true) it would not be possible to run any battles as the following error would occur: 'RobocodeFileOutputStream.threadManager cannot be null!'
[2066996] -battle broken: When using a battle file, the battles were not displayed one the GUI.
[2064834] Robot problem after Options -> Clean robot cache: Robots that tried to access their data file, like e.g. sample.SittingDuck got a java.security.AccessControlException.
Sometimes the compiler window would hang when trying to compile, but only when the compiler gave compilation errors.
IllegalArgumentException occurred when calling setStroke() or setComposite() on the Graphics2D object returned by the new getGraphics() method on the Robot.

Change

The intro battle will only be shown if a battle file has not been specified using the -battle command-line argument and Robocode is being run for the first time since installation. Previously, the intro battle was always shown even though a battle file had been specified.

Download 1.6.1.1 from here

Robocode 1.6.1 (final) has been released

2008-08-17T14:23:00.000-07:00

The final version of Robocode 1.6.1 has finally been released after the beta versions that contained lots of changes and bugfixes.

Changes since Beta 3

The new options -DPARALLEL and -DRANDOMSEED introduced in Robocode 1.6.1 will have no effect when running RoboRumble, MeleeRumble, and TeamRumble.

Previous Beta versions

In order to get the full information about all changes and bugfixes since Robocode 1.6.0, please read the information provided for the 3 previous Beta versions:

Download 1.6.1 (final) from here

Robocode 1.6.1 Beta 3

2008-08-11T15:32:00.001-07:00

More bugfixes were made to Robocode 1.6.1 (Beta 3) compared to the previous Beta 2.

Bugfixes

[2042289] Frequent errors stopping bots: This error was introduced in one of the 1.6.1 Beta versions, where some robots got this error message: "Waiting for robot XXX to stop. Robot XXX is not stopping. Forcing a stop.".
[2022774] Various usability issues: Preferences: If TPS was changed from the Preferences during a battle, the error "SYSTEM: pause game bug!" occurred.
[2024568] Sometimes the compiler window hangs: This bug occurred on some systems when compiling a robot - especially when a compiler error was returned by the compiler.
[2034395] Battles don't open again with selected robots: When opening and starting a battle from a .battle file with selected robots (in the .battle file) the New Battle dialog was showing the robots of the previous battle instead of the selected robots from the .battle file.

Changes

[2022774] Various usability issues:

Added "Enable all" and "Disable all" button in the View Options of the Preferences.
When the TPS slider is set to 0, the game is paused, and the Pause/Resume button set to paused mode. Now, if the Pause/Resume button is pressed, the game will resume at 1 TPS, and the TPS slider will now move to 1. Previously it will set to 0.
Improved some menus a bit with better names, and did some rearrangements of the order of the menu items here and there.
In the New Battle window, the focus is now kept in the list of available robots when one of the two 'Add' buttons has been pressed. Previously the focus was lost, and you had to reselect robots in the list of available robots in order to add more robots. It is now possible to add multiple robots using only the arrow keys with e.g. the Alt+A in order to add more robots to the battle.

Download: here

Robocode 1.6.1 Beta 2

2008-07-08T15:24:00.000-07:00

Lots of bugfixes and changes were made for the Robocode 1.6.1 Beta 2 compared to the first beta of the coming version 1.6.1. Some of the bugfixes were non-trivial, and hence we have made this new Beta 2 release.

Bugfixes

[2009283] Error in bullet damage calculation: The bullets scoring was incorrect compared to version 1.6.0.1. It was too high.

The Battle Results showed scores that was doubled (in the 1.6.1 Beta) compared to the real results.

Fixed issue with robot paintings, which mirrored the paintings.

Fixed issue with painting with the alpha channel (translucent color).

The mouse y coordinate of the mouse events was not scaled correctly.

When starting up a new battle, the battle would sometimes appear to be paused, even though the user did not pause the game.

[2009432] Leaking System.out: outputting to System.out from the constructor of a robot would go to the actual console instead of being properly redirected.

Changes

The new TPS slider was readjusted, so the are more slower speeds, and less higher speeds.

The menu item for the Ranking Panel is now hidden when replaying a battle, and the panel is now being hidden, if it is visible, while the battle is being replayed. The reason for hiding the Ranking Panel is that the replay feature does not support displaying the current rankings during the replay, i.e. the current scores are not recorded.

Download: here