10/10/2019 Robocode Remove Team From List
Okay, Rednaxela, I'd agree with you.One day, I've write robot that mistakenly do infinite iteration (for Circular Targeting) and I surprised that my robot removed from repository and from battle! I go through robo-code.blogspot.com and OldRobocodeNews page and saw somewhere that a bad-behavior robot will be forced to stop and removed from repository.
So I admit that and recompiled every time I faced that. (With eclipse, just save again!)But, removed from repository is good on:When people don't recognized that his/her robot skipped many turn. They will press restart and watch his/her robot stop again, again and again until robocode freeze of OutOfMemoryError!I don't know what is better but both make senses to me. Well, I think if someone notices their robot stop moving when watching battle, the first thing they'd check would be the robot console which would TELL them that their robot skipped too many turns and was stopped.
Circular targeting is the next step after you've mastered linear targeting. Using slightly more advanced mathematics, this system allows you to hit robots that travel in circles with perfect accuracy, all the while retaining effectiveness against those that travel in straight lines. Alisdair Owens shows you how to implement this technique and provides an example bot to take out for a test drive. Both your TwinDuel teams seem to be running for me, so they should get results once my client uploads some. But there is a problem with DuoLedByDroid: the team references the development version of BlindMan, while BlindMan 1.0 is what's packaged in the JAR, so Robocode says Can't find robot: jeremyreeder.collective.BlindMan. and it's a 1v2 battle. If you want to see what I mean, unzip the JAR.
Thus I don't think current behavior helps that.However, if I know my robot is sometimes freezing and stopping I battle I want to restart a few times in order to see the various conditions that are triggering the bug. This behaviour makes this testing considerably more irritating than it needs to be. Ahh, didn't know of the -debug option, however that doesn't solve this issue because that would make it even harder to debug issues of the robot in certain situations using too much time.Maybe instead of automatically when running in the GUI, add an option to the 'development options' dialog, which makes makes it so bots running from those paths are never removed from the database?Or perhaps the simplest solution would be to plain make it so robots in the custom 'development options' path are never removed from the database?
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |