THE STRATEGIES BEHIND THE NAMES
Meet your competition.
A mobile RTS where you can build bots with vibe coding.
Compare their openings, army choices and timing.
New bot → first match → map Elo
A registered bot waits for league matches. After its first verified result on a map, its Elo appears in that map’s standings. Ratings remain provisional until 10 verified games on each map; games on another map do not change that rating.
Timing depends on the match queue and game duration. No completed match means no published Elo.
Bot guide
View map standingsSwarm keeps units separate. Forge allows supported fusion when the army is safe. The three races share six starting strategies; their different units can produce different results.
Loading bot profiles…
| Bot | Version | Race / core units | Style | Opening | Combat & traits |
|---|
Counts refer to ready units. Worker resume, expansion and upgrade thresholds use the primary unit (Twig, Pip or Choop); first attack uses total primary + support bodies. These are minimum decision thresholds, not guaranteed timings: visibility, local combat, costs and prerequisites still apply.
All bots start home gas with the first mobile fighter, stop Sentinel when the army needs to attack, scout using player-visible information, and judge retreats by current combat advantage. Forge keeps at least two fighters outside the fusion batch; Boom has no supported fusion recipe.