Ok, I'll start by freely admitting that I'm hardly a robocode guru, but I am decent at coming up with ideas - it's the implementation that normally gets me.
Anyway, I intend this to spark discussion, and hopefully get more teams made (there being all of 28 TeamRobots? in RR@H - hardly a good testing ground).
So my intial thoughts:
- A good team should never be hit by one of its own bullets, either by plotting the bullets and avoiding moving where they will hit you, or plotting movement and not shooting where you would hit a teammate.
- Intel managemant - if all your bots have a radar, then ideally each should lock a separate target, and share information. That way, you can maintain perfect scan data on every enemy. However, if you are not shooting at all the enemies, perhaps having at least one radar equipped bot per enemy you intend shooting at once, one scanning radar, and the rest droids. It may even be possible to scan with less by efficiently dividing scan areas between all your radar equipped bots.
- The leader has 200 energy, but causes a 30 energy drop to every teammate if it dies. Keeping it alive seems quite important, and the extra energy could make it more suitable to long range shooting. It might even be better to go all the way and make the leader a droid, for the extra 20 energy.
- Target priorities - from my observations, having 2 or more bots shooting at a single enemy, from different angles, makes it MUCH harder for the enemy to avoid being hit, as it considerably reduces the enemy's maximum lateral velocity against at least one shooter.
- Energy management - rather than each bot managing its own energy, might it be more efficient for the team as a whole to manage its energy - for example, if 2 bots could each shoot a SittingDuck, perhaps the one with least energy should take the shot?
That's all I've come up with for now, but I hope the community can come up with better. That's why we have a wiki, after all! -- CharlieN