Thanks for opening the code

Jump to navigation Jump to search

Oh, right, I remember seeing that you used RoboRunner, which made me happy. :-)

The targeting challenges I consider pretty useful and a good predictor of rumble performance. The movement challenges, less so. My most useful Robocode testing was usually against large test beds constructed with BedMaker. I updated it in July to work with LiteRumble, if you want to give it a try.

Voidious (talk)22:42, 13 November 2015

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:User talk:Skilgannon/Thanks for opening the code/reply (6).

 

The one movement challenge which I found was a good indicator of rumble performance was the MC2K7, since there you have a gun (everybody has the same gun), and your opponent moves, so you have the same incentives to improve as in the actual rumble.

Skilgannon (talk)19:12, 15 November 2015