broken bots

Jump to navigation Jump to search

broken bots

This means that mn.SuperSittingDuck should also be removed. He throws an exception, just like cli.PerfectLoser.

package mn;

import robocode.Robot;

public class SuperSittingDuck extends Robot {

    public void run() {
	throw new RuntimeException();
    }

}
Coscience11:14, 21 September 2012

Do you happen to know what ry.Worst does? The robocpde repository is currently unavailable, so I can't check myself right now.

Clipka12:24, 21 September 2012

If you see Worst in action, it keeps shooting in the opposite direction where the opponent is.

And moves a bit in a straight line, which is not as bad as it seems, because it ends up ramming other bots sometimes and scoring a few points. Last has the same problem, it keeps moving in a straight line until it hits a wall, ramming other bots on some battles.

MN15:31, 21 September 2012
 

Actually, it is PerfectLoser that is just like mn.SuperSittingDuck. I was the one who put all the sample bots in the rumble, including SittingDuck, put all the super sample bots, and created a bot which loses to both Worst and SittingDuck. This bot even had a Java 1.5/1.6 incompatibility bug in version 1.0.0, corrected in 1.0.1, and with team/duel versions in 1.0.2.

The purpose of all this was to add a bit of humor in the rumble. And it even gave rise to Shadow/Melee_Gun in melee (Why waste my energy trying to hit Diamond when SittingDuck is there just a little bit further asking to be killed?).

The problem is simply copy-and-pasting what I did into PerfectLoser. There is no fun in that, like there is no fun in simply copy-and-pasting DrussGT under a different name.

MN15:25, 21 September 2012

Well, submitting my PerfectLoser seemed fun enough to me, because - believe it or not - when I wrote it I didn't know your SuperSittingDuck at all (except that it ranked lower than SittingDuck in the rumble).

Clipka22:06, 21 September 2012