Thread history

Fragment of a discussion from User talk:Beaming
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
No results

Doh! Sorry about that Beaming. The script is a little quick and dirty compared to what it could be. I haven't touched RoboRunner in a while, but I'll take a look when I get a chance.

@Rednaxela - It's true you need separate robots directories for each install, but I can indeed fix the issue Beaming describes with a more sophisticated shell script. The RoboRunner setup script just uses "cp -r" to clone X copies of whatever Robocode install you point it at, which means it makes X copies of the robots dir. But when using RoboRunner, it copies bots as needed from the "bots" directory into the Robocode installs, so it would be fine to leave them empty during setup.

Voidious (talk)01:57, 16 October 2013

I think it is sufficient to make an empty robots dir for each thread to be run and add the robots directory location from the master copy to botsDirs variable in the file. It is hinted in one of the readme, but took me a while to understand that this is sufficient.

On first run engine will recreate robot.database for each of the threads.

Beaming (talk)02:17, 16 October 2013