Thanks for opening the code
← Thread:User talk:Skilgannon/Thanks for opening the code/reply (3)
Also Targeting Challenge RM, which I think is the most useful one.
And also RoboRunner / RoboJogger has some advantages over RoboResearch, the main one being a big speed increase because it doesn't restart the JVM after every match.
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:User talk:Skilgannon/Thanks for opening the code/reply (4).
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.
I should try it, but the question is which bots to choose? Assuming incremental improvements, should I aim to gain vs top bots or similar score ones?
The reason I ask for your wisdom is the following. I recall once I gain a couple of points against top bots, but the score was worse for majority of the medium and lower bots. This happens when I added more advance guns to be dodged to an enemy bot. This helped against top bots, but weaker bots gained on me. I still puzzled by it.
So ideal test bed, should have a representative from each group.
Also, a side note. I noticed that Diamond sometimes get disabled right at the beginning of the game. Most likely some minor bug but if you fix it, you might get to the 1st place. I think this bug happens only in melee.
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.
