Nominations 2017-09
From Talk:RoboRumble/Participants/GigaRumble
← Thread:Talk:RoboRumble/Participants/GigaRumble/Nominations 2017-09
Jump to navigation
Jump to search
← Thread:Talk:RoboRumble/Participants/GigaRumble/Nominations 2017-09
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.
GrubbmGait (talk)
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.
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
Tomorrow I will check an older unused computer for the stuff, have been away from home for a few days, so no possibility to run the rumble. Plus I think that the file looks more like TeamRumble, no weightclass f.e.
GrubbmGait (talk)
The only important line is
PARTICIPANTSURL=http://robowiki.net/wiki/RoboRumble/Participants/GigaRumble&action=raw
The rest is just renaming of temporary files to avoid clashing with melee and roborumble if you run it in the same directory. At least similar renaming worked for MeleeTop30 which I use to run.
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.
GrubbmGait (talk)
Can you post the gigarumble.txt? Maybe we can even ask Fnl to add it to the default robocode install.
Skilgannon (talk)
#=============================================================================== # 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
GrubbmGait (talk)
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
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page.
Return to Thread:Talk:RoboRumble/Participants/GigaRumble/Nominations 2017-09/reply (14).
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
GrubbmGait (talk)
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.
GrubbmGait (talk)
