On removing bots worse than SittingDuck

Jump to navigation Jump to search

My thoughts on removing are that we should only remove if:

  • We don't have a .jar in the robocode-archive


  • It is broken in new JVM / Robocode versions, and closed source so we can't try to fix, or open source but the fix would be really complicated, or the bot has no historical significance and nobody cares.
Skilgannon (talk)21:13, 7 September 2017

Ok. I sign under it. Bad score is not a reason to be out of rumble.

My apologies to everyone for acting without discussing it first.

Beaming (talk)21:32, 7 September 2017

Shall, we instruct liteclient to look at the robocode-archive automaticly, if primary link is down?

I can probably cook up a patch for it rather quickly.

Beaming (talk)21:33, 7 September 2017

Maybe better would be a script which transforms the Participants page? This way we aren't hardcoding new URLs in the client that will need more maintenance, and we can easily run the script again to see which bots need fixing, and we know from the changelog of the participants page which ones don't have hosting anymore. This script could be made available on the wiki page. And it is 100% compatible with current rumble client.

Skilgannon (talk)22:11, 7 September 2017