LiteRumble 1.7.4.2 superpack

Jump to navigation Jump to search

LiteRumble 1.7.4.2 superpack

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

 

Return to Thread:Talk:LiteRumble/LiteRumble 1.7.4.2 superpack.

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.

Skilgannon22:05, 16 March 2013
 

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.

Skotty21:28, 22 March 2013
 

Ah, good call. I'm not sure it works that way but I'll test it. I'll also shore up the missing bots.

Voidious21:29, 22 March 2013
 

Alternatively what about just outright removing robocode.properties? That's what I always did when I made superpacks.

Rednaxela21:45, 22 March 2013