Thread history
Viewing a history listing
Time | User | Activity | Comment |
---|---|---|---|
20:45, 22 March 2013 | Rednaxela (talk | contribs) | New reply created | (Reply to LiteRumble 1.7.4.2 superpack) |
20:29, 22 March 2013 | Voidious (talk | contribs) | New reply created | (Reply to LiteRumble 1.7.4.2 superpack) |
20:28, 22 March 2013 | Skotty (talk | contribs) | New reply created | (Reply to LiteRumble 1.7.4.2 superpack) |
21:05, 16 March 2013 | Skilgannon (talk | contribs) | New reply created | (Reply to LiteRumble 1.7.4.2 superpack) |
18:45, 16 March 2013 | Voidious (talk | contribs) | New thread created |
I created a fresh "superpack" pointing at Skilgannon's rumble server: LiteRumble 1.7.4.2 superpack (31.5 MB) ... We can put this somewhere more prominent if we want to make the transition more official.
I fixed the participant list links to darkcanuck.net to point to Rednaxela's archive instead and downloaded most bots for all the rumbles in the above zip. There are still some stragglers with broken links that we should fix on the participants pages. I also set all the configs to ITERATE=NOT and updated the shell scripts to loop, which is my preferred setup. Just change your name at the top of roborumble/*.txt before running.
I don't know how many clients Skilgannon's server can handle - last I heard it was just a few. For now I'm just running 1 client for General 1v1.
Thanks. My client is in my university lab and I need the processing power during the day for the next few months at least, so feel free to run as many as you like. It should also have a more graceful quota-exceeded behaviour than it used to, but we'll actually have to hit that before I can be sure.
If you remove the CPU constant from the robocode.properties file, won't it automatically recalculate it? If so, might be a good idea to remove the CPU contant from the robocode.properties file in the superpack. Otherwise, anyone who runs the superpack without thinking about updating the CPU constant will be running with the CPU constant packaged in the superpack.
Ah, good call. I'm not sure it works that way but I'll test it. I'll also shore up the missing bots.
Alternatively what about just outright removing robocode.properties? That's what I always did when I made superpacks.