Codesize Restriction

I haven't seen this element in any of the other programming games I've checked out.

I haven't yet decided how to address weight classes in BerryBots, but I am planning to have something for it eventually. :-) Emulating Robocode's code size is definitely an option. I also want to make the CPU constraints more configurable. So instead of one static value for BerryBots on your system, different stages or configs could have different CPU constraints, and you could do weight classes that way.

If you ever start a "Berryrumble" (ideally with a better name), please use more consistent weight classes than 250, 750, 1500. It would make more sense to have something like 250, 500, 1000, 2000. Or, try resurrecting the femto system.

I'll keep it in mind, but it will also depend on what people are doing with BerryBots. I'd rather let things happen organically with people writing bots however they like before trying to force categories on them. Though some structure might encourage competition, and in turn, bot authoring. I certainly would love to have a BerryRumble and have plans for a battle runner API to support those type of use cases.

It's kind of funny how official the 250/750/1500 thresholds became. They started as the rules for some weekly tournaments (MiniBot Challenge and Robocode Little League). I wonder if those guys ever thought the divisions would remain unchanged for 9+ years. =)

If you have interest in 500 or 1000 code size classes, I say you just start making bots and go from there. I'm not sure what RoboRumble client modifications would be necessary, but they shouldn't be too hard. If the classes are interesting, other folks might follow suit. And until then, it would be kinda cool to crush MicroBots with your, uh, MicnoBots (?).

I say we name weight classes with official Metric prefixes.

I've been thinking about trying pico bots. Retreat is only three bytes shy of counting as one.

I'll just be annoying (There is a reason I chose this username.) and say deci- should come before centi-.

We already have a NeoRumble. :)