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

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

Return to Thread:User talk:Clipka/broken bots/reply (3).

 

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