View source for Talk:RoboRumble/Participants/GigaRumble

Updated ScalarR, WhiteFang and Neuromancer to the latest versions used in RoboRumble. Removed Midboss, Seraphim and PulsarMax as they don't qualify in the top-30 anymore. Re-added Garm and GresSuffurd. The only problem I have is with Raven. I added it, but I am unable to run battles for it as I use Java 8.

Hi,

I compiled Raven with Java 8 but I am not sure if I actually did =) (I have had issues with IntelliJ similar to this before)

There is always a little chance I made an accidental change to the robot so it would be better to wait for rumble rankings to stabilize.

After almost a year, we have new entrances

{'aaa.ScalarBot 0.012n2.9.14b',
 'aaa.n.ScalarN 0.011d.149',
 'dsekercioglu.mega.WhiteFang 2.5.0',
 'jk.mega.DrussGT 3.1.6',
 'jk.melee.Neuromancer 7.3'}

and also some bots disappearing

{'aaa.ScalarBot 0.012n2.8.14c',
 'cs.Mint 0.16',
 'gh.GresSuffurd 0.3.25',
 'jk.mega.DrussGT 3.1.4',
 'jk.melee.Neuromancer 7.0'}

I'll update the list accordingly and run the client then.

Btw I have a script to calculate the list difference, and may have an automated one latter, and then we may set up some daily task to update the list whenever the ranking is stable.

import json
from pprint import pprint

with open('giga.json') as f: # http://literumble.appspot.com/Rankings?game=gigarumble&api=true
  old = json.load(f)

with open('giga_new.json') as f: # http://literumble.appspot.com/Rankings?game=roborumble&order=PWIN&limit=30&api=true
  new = json.load(f)

olds = set(a['name'] for a in old)
news = set(a['name'] for a in new)

pprint(news - olds)
pprint(olds - news)

however this script cannot process tie broken rule automatically yet.

Snif, I disappear from GigaRumble . . . and one day later I am on par again with Midboss. Oh well, see it as a kick in the ass to do something about it.

Well, that randomness in PL adds some opportunism, but making your bot strong enough will definitely make it more guaranteed.

Seems like the following adaptions should be made:

• Update: BlackBox -> 0.0.2, Nene -> 1.0.5, XanderCat -> 1.2.9, DrussGT -> 3.1.4 (?)
• Removed: SilverSurfer(34), Firebird(33), Toad(32) and Midboss(30, but Hydra has better APS)
• New: ScalarBot(8), Roborio(17), Mint(19) and Neuromancer(25)

Whether these last ones (except Mint) should be added now, or that that has to wait for a 'stable' version, seems up to the developer.

Is there a problem specifically about GigaRumble on adding a non-stable version then update it along the way?

About Roborio: it will be retired as soon as Knight surpasses it, and that won't take too long since I used this an opportunity to rewrite parts of Roborio from scratch (I'll retire it because they have too much in common). Therefore, I think it shouldn't be added.

The others make sense, GigaRumble seems to be a quite interesting rumble.

These all look good to me =)

Looks good to me. I approve of these changes, especially since GigaRumble hasn't been updated since 2014.

We will need copies of gigarumble.txt and meleetop30rumble.txt, as well as the accompanying .bat/.command/.sh files to run the rumbles, though...

Looks good to me =)

Current version of ScalarBot is already a "stable" version, althrough optimized for APS not PL. I would like to update it one more time in the gigarumble after the gun is reworked (not touched since initial), but that would be long after...

I think we can always add or drop a bot from GigaRumble. Once you tuned the bot up, just switch the version at the wiki page.

The real challenge is to retune your clients so they run the GigaRumble.

that's true. afaik the RumbleSuperPack contains everything you need to run that, but i don't know whether the RumbleSuperPack is still available...

It is fairly easy to do yourself. Modify or copy and edit roborumble.sh to point to Gigarumble config, i.e. make something like

#!/bin/sh
pwd=`pwd`
cd "${0%/*}"
java -Xmx1024M  -Djava.awt.headless=true -cp libs/robocode.jar:libs/roborumble.jar:libs/codesize-1.1.jar roborumble.RoboRumbleAtHome ./roborumble/GigaRumble.txt
cd "${pwd}"

Create 'roborumble/GigaRumble.txt' with the following content and change the 'USER'

#===============================================================================
# GigaRumble..txt - Configuration file for GigaRumble (1v1 battles)
#===============================================================================

#-------------------------------------------------------------------------------
# Username. It's highly recommendable that you change this to use your name
#-------------------------------------------------------------------------------

# USER      The username used when uploading the results to the RoboRumble
#           server. Hence, you should replace 'Put_Your_Name_Here' with your
#           name, which could be the initials you use for your robot(s).

USER=Put_Your_Name_Here

#-------------------------------------------------------------------------------
# Exclude filter used for excluding participants. Use with care!
#-------------------------------------------------------------------------------

# EXCLUDE   A comma separated list of all the participants you want to exclude
#           from the competition. Excluded participants will not be downloaded
#           or take part in battles. This way you can exclude participants that
#           cannot be downloaded due to web servers that are down or hanging,
#           the repository is down, robots/teams that crashes for some reason or
#           cause other trouble. 
#
#           You can use the filename wildcards * and ? in the filter. Example:
#
#           EXCLUDE=xyz.*v1.?, *Nano*

EXCLUDE=

#-------------------------------------------------------------------------------
# Properties for controlling the rumble. Use YES or NOT
#-------------------------------------------------------------------------------

# DOWNLOAD  Download data like participants, missing robots, rating files etc.
#           from Internet if these have not been downloaded for 2 hours.
#
# EXECUTE   Execute battles. Battles files are first created and old battles
#           files are deleted before the battles are executed.
#
# UPLOAD    Upload results to the RoboRumble server specified by the RESULTSURL
#           property.
#
# ITERATE   If set to NOT, the rumble will only execute battles once.
#           If set to YES, the rumble will restart with new battles every time
#           the battles have been executed, and it will run infinitely until
#           terminated.

DOWNLOAD=YES
EXECUTE=YES
UPLOAD=YES
ITERATE=YES

# MELEE     Must be set if this rumble is meant for melee battles.
#
# TEAMS     Must be set if this rumble is meant for team battles.
#           This flag is necessary, as jar files for robot teams are different
#           from jar files for ordinary robots.

# MELEE=NOT as this property file is not meant for melee battles.
# TEAM=NOT, as this property file is not meant for team battles.

# Do not modify these properties!

MELEE=NOT
TEAMS=NOT

#------------------------------------------------------------------------------
# Properties for the battle engine
#------------------------------------------------------------------------------

# FIELDL      Battlefield width measured in pixels.
# FIELDH      Battlefield height measured in pixels.
#
# NUMBATTLES  Number of battles performed per rumble.
# ROUNDS      Number of rounds per battle.

# These are standard values for the RoboRumble. Do not modify these properties!

FIELDL=800
FIELDH=600
NUMBATTLES=50
ROUNDS=35

# INPUT     Input battles file that is generated by the rumble automatically.
#           The rumble uses this file for selecting which robots that must
#           battle against each other.
#
# OUTPUT    Battle results file, which is the output of running the rumble.

INPUT=./roborumble/temp/battles1v1GigaRumble.txt
OUTPUT=./roborumble/files/results1v1GigaRumble.txt

#-------------------------------------------------------------------------------
# Properties for retrieving robots from Internet
#-------------------------------------------------------------------------------

# BOTSREP   The robot repository where downloaded robots are put.
#
# TEMP      Directory containing all temporary files for RoboRumble.

BOTSREP=./robots/
TEMP=./roborumble/temp/

#-------------------------------------------------------------------------------
# Properties for updating participants from Internet
#-------------------------------------------------------------------------------

# PARTICIPANTSURL
#           URL to the web page containing all participants of the competition,
#           which will be used for updating the participants file specified with
#           the PARTICIPANTSFILE property.
#
# PARTICIPANTSFILE
#           File containing all the participants for the competition.
#
# STARTAG   Tag marking the start and end of the participants on the web page
#           pointed to with the PARTICIPANTSURL property.
#
# UPDATEBOTSURL
#           URL used for removing old participants, which is used for updating
#           the participants file specified with the PARTICIPANTSFILE property.

PARTICIPANTSURL=http://robowiki.net/wiki/RoboRumble/Participants/GigaRumble&action=raw
PARTICIPANTSFILE=./roborumble/files/particip1v1GigaRumble.txt

STARTAG=pre

UPDATEBOTSURL=http://literumble.appspot.com/RemoveOldParticipant

#-------------------------------------------------------------------------------
# Properties to control the way battles are run 
#-------------------------------------------------------------------------------

# RUNONLY   If left black or set to GENERAL, a new battle file is created where
#           robots from the participants file are paired at random. The number
#           of robot pairs will match number of battles defined the NUMBATTLES
#           property. 
#
#           If set to MINI, a new battle file is created similar to the one
#           for GENERAL, but it will only contains robots that are MiniBots,
#           which has a code size < 1500 bytes (calculated by the codesize tool).
#
#           If set to MICRO, a new battle file is created similar to the one
#           for GENERAL, but it will only contains robots that are MicroBots,
#           which has a code size < 750 bytes (calculated by the codesize tool).
#
#           If set to NANO, a new battle file is created similar to the one for
#           GENERAL, but it will only contains robots that are NanoBots, which
#           has a code size < 250 bytes (calculated by the codesize tool).
#
#           If set to SERVER (recommended), a new battle file is created which
#           will first of all contain priority battles for robots that that has
#           priority over other robots until they have fought a specific number
#           of battles specified by the BATTLESPERBOT property. The number of
#           battles fought by the individual robots are extracted from the
#           rating files, which are downloaded from the server if the DOWNLOAD
#           property is set to YES. When no more priority battles are left,
#           robots from the participants file are paired at random similar to
#           GENERAL.
#
# BATTLESPERBOT
#           The number of battles a robot has to fight before it will no longer
#           have priority over other robots in battles. Prioritizing a robot
#           makes its rating more reliable faster as its number of fought
#           battles increases faster than when it is not prioritized.
#
# PRIORITYBATTLESFILE
#           The priority battles file that is generated automatically by the
#           rumble when the RUNONLY property is set to SERVER.

RUNONLY=SERVER

BATTLESPERBOT=2000

PRIORITYBATTLESFILE=./roborumble/temp/priority1v1GigaRumble.txt

#-------------------------------------------------------------------------------
# Properties for uploading the results to the server
#-------------------------------------------------------------------------------

# RESULTSURL
#           URL used for uploading the results to the server. 
#
# BATTLESNUMFILE
#           File containing the number of battles fought by the robots, which is
#           returned by the server when results are uploaded to the server.

RESULTSURL=http://literumble.appspot.com/UploadedResults

BATTLESNUMFILE=./roborumble/temp/battlesnumber.txt

#-------------------------------------------------------------------------------
# Properties for related competitions
#-------------------------------------------------------------------------------

# Related competitions are competitions where participants are a subset of the
# participants in the general competition.
#
# The MiniBots (code size < 1500) are participants of the MiniRumble.
# The MicroBots (code size < 750) are participants of the MicroRumble.
# The NanoBots (code size < 250) are participants of the NanoRumble.

# Do not modify these properties!

MINIBOTS=minirumble
MICROBOTS=microrumble
NANOBOTS=nanorumble

# CODESIZEFILE:
#           The code size file that is generated automatically by the rumble in
#           order determine the code size of each individual robot.
 
CODESIZEFILE=./roborumble/files/codesize1v1GigaRumble.txt

#-------------------------------------------------------------------------------
# Properties for URLs and file names for the rating files to download
#-------------------------------------------------------------------------------

# RATINGS.URL:
#           URL to where ratings files are located on Internet.
#
# RATINGS.GENERAL:
#           File name for the rating file of the general RoboRumble.
#
# RATINGS.MINIBOTS:
#           File name for the rating file of the MiniRumble.
#
# RATINGS.MICROBOTS:
#           File name for the rating file of the MicroRumble.
#
# RATINGS.NANOBOTS:
#           File name for the rating file of the NanoRumble.

RATINGS.URL=http://literumble.appspot.com/RatingsFile

RATINGS.GENERAL=./roborumble/temp/ratings_roboGigaRumble.txt
RATINGS.MINIBOTS=./roborumble/temp/ratings_miniGigaRumble.txt
RATINGS.MICROBOTS=./roborumble/temp/ratings_microGigaRumble.txt
RATINGS.NANOBOTS=./roborumble/temp/ratings_nanoGigaRumble.txt

nanoGigaRumble ? Are you kidding?

I think giga rumble is very different from the general rumble. We should try to find the official one

This file is destroying minirumble. You should remove

MINIBOTS=minirumble
MICROBOTS=microrumble
NANOBOTS=nanorumble

for it to work.

All proposed changes are made, GigaRumble is running fine now. Also mn.Combat is updated from 3.23.1 to 3.25.0 (December 2016). I have only one problem: Roborio and XanderCat are Java 8 specific, and I am running from Java 7, so I can't run battles for those bots.

Can you post the gigarumble.txt? Maybe we can even ask Fnl to add it to the default robocode install.

#===============================================================================
# gigarumble.txt - Configuration file for top-30 RoboRumble (1v1 battles)
#===============================================================================

#-------------------------------------------------------------------------------
# Username. It's highly recommendable that you change this to use your name
#-------------------------------------------------------------------------------

# USER      The username used when uploading the results to the RoboRumble
#           server. Hence, you should replace 'Put_Your_Name_Here' with your
#           name, which could be the initials you use for your robot(s).

USER=GrubbmGait

#-------------------------------------------------------------------------------
# Exclude filter used for excluding participants. Use with care!
#-------------------------------------------------------------------------------

# EXCLUDE   A comma separated list of all the participants you want to exclude
#           from the competition. Excluded participants will not be downloaded
#           or take part in battles. This way you can exclude participants that
#           cannot be downloaded due to web servers that are down or hanging,
#           the repository is down, robots/teams that crashes for some reason or
#           cause other trouble. 
#
#           You can use the filename wildcards * and ? in the filter. Example:
#
#           EXCLUDE=xyz.*v1.?, *Nano*

EXCLUDE=

#-------------------------------------------------------------------------------
# Properties for controlling the rumble. Use YES or NOT
#-------------------------------------------------------------------------------

# DOWNLOAD  Download data like participants, missing robots, rating files etc.
#           from Internet if these have not been downloaded for 2 hours.
#
# EXECUTE   Execute battles. Battles files are first created and old battles
#           files are deleted before the battles are executed.
#
# UPLOAD    Upload results to the RoboRumble server specified by the RESULTSURL
#           property.
#
# ITERATE   If set to NOT, the rumble will only execute battles once.
#           If set to YES, the rumble will restart with new battles every time
#           the battles have been executed, and it will run infinitely until
#           terminated.

DOWNLOAD=YES
EXECUTE=YES
UPLOAD=YES
ITERATE=YES

# MELEE     Must be set if this rumble is meant for melee battles.
#
# TEAMS     Must be set if this rumble is meant for team battles.
#           This flag is necessary, as jar files for robot teams are different
#           from jar files for ordinary robots.

# MELEE=NOT as this property file is not meant for melee battles.
# TEAM=NOT, as this property file is not meant for team battles.

# Do not modify these properties!

MELEE=NOT
TEAMS=NOT

#------------------------------------------------------------------------------
# Properties for the battle engine
#------------------------------------------------------------------------------

# FIELDL      Battlefield width measured in pixels.
# FIELDH      Battlefield height measured in pixels.
#
# NUMBATTLES  Number of battles performed per rumble.
# ROUNDS      Number of rounds per battle.

# These are standard values for the RoboRumble. Do not modify these properties!

FIELDL=800
FIELDH=600
NUMBATTLES=10
ROUNDS=35

# INPUT     Input battles file that is generated by the rumble automatically.
#           The rumble uses this file for selecting which robots that must
#           battle against each other.
#
# OUTPUT    Battle results file, which is the output of running the rumble.

INPUT=./roborumble/temp/battlesgiga.txt
OUTPUT=./roborumble/files/resultsgiga.txt

#-------------------------------------------------------------------------------
# Properties for retrieving robots from Internet
#-------------------------------------------------------------------------------

# BOTSREP   The robot repository where downloaded robots are put.
#
# TEMP      Directory containing all temporary files for RoboRumble.

BOTSREP=./robots/
TEMP=./roborumble/temp/

#-------------------------------------------------------------------------------
# Properties for updating participants from Internet
#-------------------------------------------------------------------------------

# PARTICIPANTSURL
#           URL to the web page containing all participants of the competition,
#           which will be used for updating the participants file specified with
#           the PARTICIPANTSFILE property.
#
# PARTICIPANTSFILE
#           File containing all the participants for the competition.
#
# STARTAG   Tag marking the start and end of the participants on the web page
#           pointed to with the PARTICIPANTSURL property.
#
# UPDATEBOTSURL
#           URL used for removing old participants, which is used for updating
#           the participants file specified with the PARTICIPANTSFILE property.

PARTICIPANTSURL=http://robowiki.net/wiki/RoboRumble/Participants/GigaRumble?action=raw
PARTICIPANTSFILE=./roborumble/files/participgiga.txt

STARTAG=pre

UPDATEBOTSURL=http://literumble.appspot.com/RemoveOldParticipant

#-------------------------------------------------------------------------------
# Properties to control the way battles are run 
#-------------------------------------------------------------------------------

# RUNONLY   If left black or set to GENERAL, a new battle file is created where
#           robots from the participants file are paired at random. The number
#           of robot pairs will match number of battles defined the NUMBATTLES
#           property. 
#
#           If set to SERVER (recommended), a new battle file is created which
#           will first of all contain priority battles for robots that that has
#           priority over other robots until they have fought a specific number
#           of battles specified by the BATTLESPERBOT property. The number of
#           battles fought by the individual robots are extracted from the
#           rating files, which are downloaded from the server if the DOWNLOAD
#           property is set to YES. When no more priority battles are left,
#           robots from the participants file are paired at random similar to
#           GENERAL.
#
# BATTLESPERBOT
#           The number of battles a robot has to fight before it will no longer
#           have priority over other robots in battles. Prioritizing a robot
#           makes its rating more reliable faster as its number of fought
#           battles increases faster than when it is not prioritized.
#
# PRIORITYBATTLESFILE
#           The priority battles file that is generated automatically by the
#           rumble when the RUNONLY property is set to SERVER.

RUNONLY=SERVER

BATTLESPERBOT=200

PRIORITYBATTLESFILE=./roborumble/temp/prioritygiga.txt

#-------------------------------------------------------------------------------
# Properties for uploading the results to the server
#-------------------------------------------------------------------------------

# RESULTSURL
#           URL used for uploading the results to the server. 
#
# BATTLESNUMFILE
#           File containing the number of battles fought by the robots, which is
#           returned by the server when results are uploaded to the server.

RESULTSURL=http://literumble.appspot.com/UploadedResults

BATTLESNUMFILE=./roborumble/temp/gigabattlesnumber.txt

#-------------------------------------------------------------------------------
# Properties for URLs and file names for the rating files to download
#-------------------------------------------------------------------------------

# RATINGS.URL:
#           URL to where ratings files are located on Internet.
#
# RATINGS.GENERAL:
#           File name for the rating file of the general RoboRumble.
#
# RATINGS.MINIBOTS:
#           File name for the rating file of the MiniRumble.
#
# RATINGS.MICROBOTS:
#           File name for the rating file of the MicroRumble.
#
# RATINGS.NANOBOTS:
#           File name for the rating file of the NanoRumble.

RATINGS.URL=http://literumble.appspot.com/RatingsFile

RATINGS.GENERAL=./roborumble/temp/ratings_gigarumble.txt

Also, I was running Melee Top 30 for ages with the following 'meleeTop30rumble.sh' script

#!/bin/sh
pwd=`pwd`
cd "${0%/*}"
java -Xmx1024M  -Djava.awt.headless=true -cp libs/robocode.jar:libs/roborumble.jar:libs/codesize-1.1.jar roborumble.RoboRumbleAtHome ./roborumble/meleeTop30rumble.txt
cd "${pwd}"

and config 'meleeTop30rumble.txt'

#===============================================================================
# meleeTop30rumble.txt - Configuration file for MeleeRumble (meleeTop30 battles)
#===============================================================================

#-------------------------------------------------------------------------------
# User property. It's highly recommendable that you change this to use your name
#-------------------------------------------------------------------------------

# USER      The user name used when uploading the results to the RoboRumble
#           server. Hence, you should replace 'Put_Your_Name_Here' with your
#           name, which could be the initials you use for your robot(s).

USER=Put_Your_Name_Here

#-------------------------------------------------------------------------------
# Exclude filter used for excluding participants. Use with care!
#-------------------------------------------------------------------------------

# EXCLUDE   A comma separated list of all the participants you want to exclude
#           from the competition. Excluded participants will not be downloaded
#           or take part in battles. This way you can exclude participants that
#           cannot be downloaded due to web servers that are down or hanging,
#           the repository is down, robots/teams that crashes for some reason or
#           cause other trouble. 
#
#           You can use the filename wildcards * and ? in the filter. Example:
#
#           EXCLUDE=xyz.*v1.?, *Nano*

EXCLUDE=

#-------------------------------------------------------------------------------
# Properties for controlling the rumble. Use YES or NOT
#-------------------------------------------------------------------------------

# DOWNLOAD  Download data like participants, missing robots, rating files etc.
#           from Internet if these have not been downloaded for 2 hours.
#
# EXECUTE   Execute battles. Battles files are first created and old battles
#           files are deleted before the battles are executed.
#
# UPLOAD    Upload results to the RoboRumble server specified by the RESULTSURL
#           property.
#
# ITERATE   If set to NOT, the rumble will only execute battles once.
#           If set to YES, the rumble will restart with new battles every time
#           the battles have been executed, and it will run infinitely until
#           terminated.

DOWNLOAD=YES
EXECUTE=YES
UPLOAD=YES
ITERATE=YES

# MELEE     Must be set if this rumble is meant for melee battles.
#
# TEAMS     Must be set if this rumble is meant for team battles.
#           This flag is necessary, as jar files for robot teams are different
#           from jar files for ordinary robots.

# MELEE=YES as this property file is meant for melee battles.
# TEAM=NOT, as this property file is not meant for team battles.

# Do not modify these properties!

MELEE=YES
TEAMS=NOT

#------------------------------------------------------------------------------
# Properties for the battle engine
#------------------------------------------------------------------------------

# FIELDL      Battlefield width measured in pixels.
# FIELDH      Battlefield height measured in pixels.
#
# NUMBATTLES  Number of battles performed per rumble.
# ROUNDS      Number of rounds per battle.
#
# MELEEBOTS   Number of robots that participate in a melee battle.

# These are standard values for the MeleeRumble. Do not modify these properties!

FIELDL=1000
FIELDH=1000
NUMBATTLES=3
ROUNDS=35
MELEEBOTS=10

# INPUT     Input battles file that is generated by the rumble automatically.
#           The rumble uses this file for selecting which robots that must
#           battle against each other.
#
# OUTPUT    Battle results file, which is the output of running the rumble.

INPUT=./roborumble/temp/battlesmeleeTop30.txt
OUTPUT=./roborumble/files/resultsmeleeTop30.txt

#-------------------------------------------------------------------------------
# Properties for retrieving robots from Internet
#-------------------------------------------------------------------------------

# BOTSREP   The robot repository where downloaded robots are put.
#
# TEMP      Directory containing all temporary files for RoboRumble.

BOTSREP=./robots/
TEMP=./roborumble/temp/

#-------------------------------------------------------------------------------
# Properties for updating participants from Internet
#-------------------------------------------------------------------------------

# PARTICIPANTSURL
#           URL to the web page containing all participants of the competition,
#           which will be used for updating the participants file specified with
#           the PARTICIPANTSFILE property.
#
# PARTICIPANTSFILE
#           File containing all the participants for the competition.
#
# STARTAG   Tag marking the start and end of the participants on the web page
#           pointed to with the PARTICIPANTSURL property.
#
# UPDATEBOTSURL
#           URL used for removing old participants, which is used for updating
#           the participants file specified with the PARTICIPANTSFILE property.

PARTICIPANTSURL=http://robowiki.net/wiki/RoboRumble/Participants/MeleeTop30&action=raw
PARTICIPANTSFILE=./roborumble/files/participmeleeTop30.txt

STARTAG=pre

UPDATEBOTSURL=http://literumble.appspot.com/RemoveOldParticipant

#-------------------------------------------------------------------------------
# Properties to control the way battles are run 
#-------------------------------------------------------------------------------

# RUNONLY   If left black or set to GENERAL, a new battle file is created where
#           robots from the participants file are paired at random. The number
#           of robot pairs will match number of battles defined the NUMBATTLES
#           property. 
#
#           If set to MINI, a new battle file is created similar to the one
#           for GENERAL, but it will only contains robots that are MiniBots,
#           which has a code size < 1500 bytes (calculated by the codesize tool).
#
#           If set to MICRO, a new battle file is created similar to the one
#           for GENERAL, but it will only contains robots that are MicroBots,
#           which has a code size < 750 bytes (calculated by the codesize tool).
#
#           If set to NANO, a new battle file is created similar to the one for
#           GENERAL, but it will only contains robots that are NanoBots, which
#           has a code size < 250 bytes (calculated by the codesize tool).
#
#           If set to SERVER (recommended), a new battle file is created which
#           will first of all contain priority battles for robots that that has
#           priority over other robots until they have fought a specific number
#           of battles specified by the BATTLESPERBOT property. The number of
#           battles fought by the individual robots are extracted from the
#           rating files, which are downloaded from the server if the DOWNLOAD
#           property is set to YES. When no more priority battles are left,
#           robots from the participants file are paired at random similar to
#           GENERAL.
#
# BATTLESPERBOT
#           The number of battles a robot has to fight before it will no longer
#           have priority over other robots in battles. Prioritizing a robot
#           makes its rating more reliable faster as its number of fought
#           battles increases faster than when it is not prioritized.
#
# PRIORITYBATTLESFILE
#           The priority battles file that is generated automatically by the
#           rumble when the RUNONLY property is set to SERVER.

RUNONLY=SERVER

BATTLESPERBOT=2000

PRIORITYBATTLESFILE=./roborumble/temp/priorityTop30melee.txt

#-------------------------------------------------------------------------------
# Properties for uploading the results to the server
#-------------------------------------------------------------------------------

# RESULTSURL
#           URL used for uploading the results to the server. 
#
# BATTLESNUMFILE
#           File containing the number of battles fought by the robots, which is
#           returned by the server when results are uploaded to the server.

RESULTSURL=http://literumble.appspot.com/UploadedResults

BATTLESNUMFILE=./roborumble/temp/meleeTop30battlesnumber.txt

#-------------------------------------------------------------------------------
# Properties for related competitions
#-------------------------------------------------------------------------------

# Related competitions are competitions where participants are a subset of the
# participants in the general competition.
#
# The MiniBots (code size < 1500) are participants of the MiniRumble.
# The MicroBots (code size < 750) are participants of the MicroRumble.
# The NanoBots (code size < 250) are participants of the NanoRumble.

# Do not modify these properties!

MINIBOTS=minimeleerumble
MICROBOTS=micromeleerumble
NANOBOTS=nanomeleerumble

# CODESIZEFILE:
#           The code size file that is generated automatically by the rumble in
#           order determine the code size of each individual robot.

CODESIZEFILE=./roborumble/files/codesizemelee.txt

#-------------------------------------------------------------------------------
# Properties for URLs and file names for the rating files to download
#-------------------------------------------------------------------------------

# RATINGS.URL:
#           URL to where ratings files are located on Internet.
#
# RATINGS.GENERAL:
#           File name for the rating file of the general MeleeRumble.
#
# RATINGS.MINIBOTS:
#           File name for the rating file of the Melee MiniRumble.
#
# RATINGS.MICROBOTS:
#           File name for the rating file of the Melee MicroRumble.
#
# RATINGS.NANOBOTS:
#           File name for the rating file of the Melee NanoRumble.

RATINGS.URL=http://literumble.appspot.com/RatingsFile

RATINGS.GENERAL=./roborumble/temp/ratings_mTop30_roborumble.txt
#RATINGS.MINIBOTS=./roborumble/temp/ratings_mTop30_minirumble.txt
#RATINGS.MICROBOTS=./roborumble/temp/ratings_mTop30_microrumble.txt
#RATINGS.NANOBOTS=./roborumble/temp/ratings_mTop30_nanorumble.txt

Thank you for this effort. I'll try to make Roborio Java 7 compliant soon.

To MultiplyByZer0: seems that Chalk is getting zero scores in your setup. Could you verify that? You can ignore that bot by setting 'EXCLUDE=cjm.* in your gigarumble.txt

DrussGT, XanderCat, and Roborio bullet-shield Chalk to death, explaining the low APS and Survival. I don't see zero scores anywhere else in the ranking table, and its rank in GigaRumble (#26) is actually above its rank in RoboRumble (#34).

Lol, hadn't thought of that. I had not expected though that someone that vulnerable to bullet-shielding would get that high in the PL.

Seems that an update is appropriate, as rsalesc.Knight(#4) and cb.Firestarter(#5) would enter. Next to that, updated versions of aaa.ScalarBot, gh.GresSuffurd and jk.Neuromancer and the re-entrance of ags.Midboss. Alas ags.RougeDC, kc.Hydra and pulsar.pulsarMax will (temporarily ?) disappear from the list. I will update the list tonight and try to start running a client.

Updated to Java 8, but I can't run battles for rsalesc.Roborio and xander.XanderCat. Seems that they are made with Java 9 specific things. So if anyone else with Java 9 can also run Gigarumble, the ranking can become complete.

Suddenly Roborio works, with some luck XanderCat will also . . .

Team rumble and Twin Duel are broken in Java 9. I won't upgrade until the Robocode engine is fixed.

The battle bugs (Bug-389, Bug-390) have been fixed, but only with version 1.9.3.0. The rumble is still stuck on version 1.9.2.6, because the server won't be upgraded until a regression analysis is made, and no one has yet volunteered to do that.

Both works fine here in Java 8, so maybe restarting the rumble/cleaning the caches helps? btw I would like to run Gigarumble as well, may you post a working config file for it? Hope that is included in the next release of robocode.

I removed the caches from all installations (RoboRumble and GigaRumble are separate installs), and now XanderCat also works! I can't run battles till I get home though, as the firewall at work prevents download/upload of necessary files and results.

My config file is listed in the discussion below. The gigarumble.bat file contains:

java -Xmx512M -cp libs/robocode.jar;libs/roborumble.jar;libs/codesize-1.1.jar; roborumble.RoboRumbleAtHome ./roborumble/gigarumble.txt

It will be cool to see DrussGT #1 in GigaRumble be threatened as we kick BulletShielding-susceptible bots off from the top30 :P

There are 4 bots vulnerable to BulletShielding present: Phoenix (#16), Chalk (#21), CassiusClay (#22) and Seraphim (#27). They earn their presence as they kick a lot of butts. But you are right, DrussGT only clings on the first place due to its Bullet Shielding. Diamond on the other hand does not use it.

Yeah, sure they do, but these are bots we can probably assume that won't receive new updates, so they will be BulletShielding-susceptible forever and, let's be honest, they will eventually be kicked off from top30. Maybe it will take very long, but they will. And of course, they will be kicked from top30 in part because of the legacy they left behind :P

And just to clarify, I would love to be wrong about those bots not receiving updates :P

And I'm curious about why there are so many bots NOT vulnerable to BS ;)

What do you think about bringing the GigaRumble participants to the main roborumble page, and adding the gigarumble.txt and gigarumble.sh/bat files to the superpacks?

Totally cool with me, I do think it's a pretty interesting rumble. Worth noting that it requires a little maintenance to actually sort the main rumble by PL and update the participants list from time to time, but the top 30 doesn't change that often.

Also open to discussion about the number of bots/format/name and such, all of which I dictated when it was just me playing around.

Does this mean I should start keeping my own entry updated on the participants list? At the moment, XanderCat 11.4 is still in the GigaRumble, which is quite a bit out of date.

Once you are on this page, you have your ticket in. Feel free to edit.

Voidious, I'm sure you could automate the page generation?

Er, yeah, I guess I could. Sort main rankings by PWIN, take top 30, update GigaRumble participants list - right?

I really should get all this stuff running from the RoboWiki server. It's funny sometimes when I turn off my laptop for travel, then come back online and see a few @roborumble tweets come in. ;)

Could you update your gigarumble.txt file to the new URL and add it to the superpack?

As a note, I just updated robocode-archive.strangeautomata.com to ensure that participants-latest.zip always includes versions in the GigaRumble participants list as well as the other versions. This is to cover the case of the main participants list getting a new version before GigaRumble.

(Also tomorrow makes for the 1-year anniversary of the cron job for robocode-archive.strangeautomata.com being started, and hasn't failed since :))

Nice! It's a great resource, we all owe you a thanks for setting that up.

I nominate the following robots for admission into the GigaRumble: Nene, Neuromancer, CunobelinDC, RaikoMX, and SandboxDT.

If anyone else would like to nominate a robot for the GigaRumble, feel free to use this thread to do so.

Well, Nene has more than earned its place at #11 in PL. As for the others, my vote is definitely to stick to "top x bots" instead of hand picking bots we like.

Top 50 would include all those bots... I still like 30 and personally feel like even that's erring on the high side. (A bot at #30 has almost no chance vs DrussGT.) What do other people think?

For:

• Nene, top 10 bot. I have no problems with someone entering it, but its turned for simple bots.

Against:

• SandboxDT, impressive for its age. But not impressive enough.
• RaikoMX, see SandboxDT.
• Neuromancer, great at Melee, only decent in One on One.
• CunobelinDC, entering it in the gigarumble just isn't fair.

Nominating:

• Seraphim, decent post-debug, holds #10 Vote and #22 PL (PWIN). Tuned against surfers originally.

That crossed my mind too. :-) Then I thought it's kind of silly to have an active rumble for bots that never get updated. And also, how to treat a bot like Shadow? Totally classic, but updated a lot more recently than others like DT.

It's not a sign of disrespect to leave those bots out of a "strongest bots rumble". Pretty sure most of those authors would want to earn their spot anyway, if they were active.

Man, you know what's crazy, DrussGT may take the GigaRumble crown with the bullet shielding destroying Hydra and Phoenix. It's funny, this might be more likely to motivate me to add it than the RoboRumble APS gains...

I know exactly how you feel. It's a lot harder to lose something than to not have what you don't have already :-p

Yeah, I remember that feeling... vaguely... :-P

I should know better than to even look at the results after so few battles, but this already seems pretty interesting: [1].

First thing I notice is Diamond/DrussGT about even in APS, but DrussGT almost 5% ahead in survival. Of course, I start thinking, "maybe some better bullet power management would rocket me ahead of DrussGT!" But my experience is generally that more conservative bullet power selection will increase survival, but tend to lose the same in bullet damage, for the same overall score in the end. Perhaps DrussGT could even gain some score by sacrificing some survival...

Shadow is lower than I expected.

Pris does awesome, as I expected.

This LiteRumble thing is pretty cool! =)

Like I expected, GresSuffurd is dangling at last place. Btw, is there a way to check if a robot extends Robot, without looking in the source?

Given how strong GresSuffurd already is, I bet you could move up to the middle of the pack in a night's work, adding rolling average to surf stats and/or an Anti-Surfer gun.

About Robot, do you mean for accounting for wall collisions in energy tracking? I was just thinking about that the other day (very old "TODO" in Diamond's movement code)...

I'm pretty sure Robocode doesn't tell you, but you could detect it pretty quickly by noticing if a wall collision affects their energy. With gun heat tracking, since most collisions won't happen at gun heat = 0, I bet it would usually take only one wall collision to tell if they're Robot or AdvancedRobot. (A bullet being fired is the only other reason the AdvancedRobot might have lost energy, and you could rule that out.)

It is an interesting rumble. I'm surprised Scarlet does as well as it does. The movement is mostly designed to dodge simpler targeting, rather then adaptive targeting.