Team Roles & Formations

Origins

Team roles in classic Robocode were worked out by the RoboWiki community through its TeamRobot documentation and example rosters. Robocode Tank Royale, created by Flemming Nørnberg Larsen (fnl), names its roles and formations directly in its own Team Strategies documentation.

Communication & Coordination gives a team a wire to talk over. That wire is wasted if every bot on the roster does the same job with it. RoboWiki names the harder problem directly: assigning the good spots to the bots, since only one bot can stand in each spot, and a team of five identical duelists collides, duplicates effort, and leaves gaps a coordinated team would have covered.

Same class, different job

Robocode numbers every bot instance on a team, so five copies of one class can still tell each other apart and take different jobs without five different source files. Tank Royale's own team documentation puts names on the typical split: a Leader that carries wide radar coverage and low firepower to gather information, a Soldier that carries the heavy gun and leans on the Leader's data, and a Droid that trades its radar for extra energy and depends on a teammate for every target it ever sees, as Team Basics covers.

RoboWiki's own example rosters show the same split by proportion rather than name: one leader with radar plus four droids that take orders from it, five bots of different classes each specialized for a job, or, at the plain end, five identical bots with no specialization at all.

One point of failure

Specialization has a cost, and RoboWiki states it without softening: a team built around a radar-carrying leader and radar-less droids gets more total energy, but it suffers from a lack of information and gets in serious trouble if the leader gets killed. Every droid on that roster stops seeing the battlefield the instant its one set of eyes dies. A team of five identical, self-sufficient bots trades that peak efficiency for a roster that can lose any single member and keep functioning.

Formations that use two bots as one gun

A crossfire formation puts two bots at different angles on the same enemy, so a dodge that escapes one bot's line of fire walks straight into the other's. A cover formation keeps one bot engaged while a second, healthier teammate holds back to support the moment the first bot's energy drops. Corner trapping coordinates both bots to push an enemy toward a corner, tightening the escape routes a corner already limits on its own, the same constraint Corner Movement covers from the other side of the gun.

Two friendly bots hold different angles on one enemy, so no dodge escapes both guns at once.

Build the roster before the roles

Tank Royale's own development order is worth following even in classic Robocode: get one bot fighting well alone first, add the messaging from Communication & Coordination second, add target-claim coordination third, and only then layer in formation and role logic. A crossfire formation coded before either bot can reliably hit a target on its own just turns one bot's missed shots into two bots' missed shots.

Platform notes

Platform Difference

Classic Robocode documents team composition by proportion, a leader plus droids, or a specialized five-bot roster, without naming formations. Robocode Tank Royale names both roles (Leader, Soldier, Droid) and formations (crossfire, cover, corner trapping) directly in its own documentation.

Team Roles & Formations ​

Same class, different job ​

One point of failure ​

Formations that use two bots as one gun ​

Build the roster before the roles ​

Platform notes ​

Further Reading ​