RoboRumble/Contributing to RoboRumble
|
To collaborate with RR@H
If you entered a bot into the competition, you could consider to collaborate running the competition by using your computer to execute battles and upload results (similar to Seti@home project). The process is fully automated, so there is no pain on doing it.
- Make a separate installation of Robocode in a different directory (like c:\robohome), so running the client will not influence your own development and vice versa. Please only use versions 1.5.4 or 1.6.0, as they are proven stable.
- Edit "roborumble\roborumble.txt" file and change the Put_Your_Name_Here to your nick.
- Extract all the zip-files below into the "robots" directory
- Start the client using roborumble.bat or roborumble.sh (depending on the OS). The first time it can take more than 15 minutes before all jar-files are examined!
- Or, on your first time you can start robocode with robocode.bat or robocode.sh (depending on OS), wait for the robocode database to be updated, then close robocode and run roborumble.bat/roborumble.sh normally.
- Run it as much time as you can. The more you run it, the more you contribute. It is fully automated, so you don't have to care at all.
- If you find problems, refer to RoboRumble related pages, or post your issue and we will try to solve it.
To get a reasonably up-to-date set of robots for the rumble to start with, grab the following zip file and move the 300 jars inside it to your RR@H robots directory:
- http://robowiki.net/robocode/rrath_participants.zip
- http://www.krillrfiles.com/robocode/rrath_participants.zip
And get the 308 updates since 20041017 till 20070929:
And get the 117 updates since 20070929 till 20080711:
The same for the meleerumble:
And also for the teamrumble:
Issues on starting off with RoboRumble can be discussed on the talk page.
Old issues are archived at RoboRumble/StartingWithRoboRumbleOld.
Useful options in roborumble.txt
- "USER": Your name/handle, used for identification of your roborumble client.
- "BATTLESPERBOT" is the minimum number of battles a bot needs before it stops getting priority.
- "NUMBATTLES", the number of battles fought on each run of roborumble.
- If you want the roborumble client to run battles indefinitely, use one of the following scripts.
Batch script for Windows users
@echo off title RoboRumble@Home Client :run java -Xmx512M -Dsun.io.useCanonCaches=false -cp libs/robocode.jar;libs/codesize.jar;libs/cachecleaner.jar robocode.Robocode 2>> ./log.txt echo --- goto run
Appends stderr output only to log.txt.
Isn't this a Robocode script? Maybe you mean this one:
@echo off title RoboRumble@Home Client :run java -Xmx512M -Dsun.io.useCanonCaches=false -cp libs/robocode.jar;libs/codesize.jar;libs/roborumble.jar roborumble.RoboRumbleAtHome ./roborumble/roborumble.txt 2>> ./log.txt echo --- goto run
-- Nat 18:08, 27 December 2008 (UTC)
Bash script for *nix users
This bash script will be good for unix "roborumbler". Run forever battles, it catch standard and error stream and put it to a file in the directory ./log/tempNUMBER_OF_BATTLE.txt (the script have to be in the roborumble directory). For Linux: save it to a file in the roborumble directory, right click and set the file executable, create a directory called "log", then run the script from shell:
#!/bin/bash echo # new line count=0 while [ "$var1" != "fine" ] # forever do let "count=count+1" echo "battle n: " $count sh roborumble.sh &> ./log/temp$count.txt echo done exit 0