Thread history
Viewing a history listing
| Time | User | Activity | Comment |
|---|---|---|---|
| 00:11, 10 December 2013 | Chase-san (talk | contribs) | New reply created | (Reply to RoboRunner GUI) |
| 23:02, 9 December 2013 | Chase-san (talk | contribs) | Comment text edited | |
| 23:01, 9 December 2013 | Chase-san (talk | contribs) | Comment text edited | |
| 22:54, 9 December 2013 | Chase-san (talk | contribs) | New reply created | (Reply to RoboRunner GUI) |
| 21:30, 9 December 2013 | Voidious (talk | contribs) | New reply created | (Reply to RoboRunner GUI) |
| 14:34, 9 December 2013 | Chase-san (talk | contribs) | New reply created | (Reply to RoboRunner GUI) |
| 23:43, 7 December 2013 | Chase-san (talk | contribs) | New thread created |
I wrote a custom GUI for RoboRunner, it directly interfaces with a modified RoboRunner. It is in early early alpha. The feature set is nowhere near complete. Please let me know of any bugs.
Robots are not automatically copied to robocode directories. Nothing is saved. Paths cannot (at the moment) be altered. Results do no update automatically, they need to be closed and reopened to update them (I plan to fix this). Thread count cannot be changed after starting (for now, changing this would be involved).
I guess I should mention its advantages over RoboJogger, the other GUI for RoboRunner, also over RoboRunner itself.
It has a queue that runs challenges in whatever order they happen to be in the queue. This means once you start it, you can run multiple challenges without robocode needing to restart, and you can also reorder the queue after starting the battle threads.
It is better to consider it's limitations compared to RoboResearch. Aside from the first post, you cannot start and stop threads individually. I may support this eventually, but at the moment it would require rewriting RoboRunner's BattleRunner class. Which also means once you start the threads, you cannot alter the number of threads running.
Congrats on the first release! I'll try to have a look tonight or tomorrow.
Do we need any setup instructions? Or are the roborunner.properties and empty Robocode installs already in the zip?
I am working on automating the runner creation and robot jar copying process today. As well as adding an options dialog to configure the paths and jvm arguments.
The GUI won't use the properties as the standard roborunner. But the current version doesn't use any at all.
But for the current version, you need to create the robocodes/r[0-9]+ directories yourself (or use the script you wrote). You can pick the thread count in the program itself (but only up to the number of runners you created). Make sure to copy the robots into robocodes/r[0-9]+/robots directories as well.
v0.9.2-Alpha
Adding options (that save), automatic robocode runner creation (based on threads), and automatic robot jar copying.
