Log inGet started
← Explore
World media

Field Command: RTS Selection, Formations, Fog of War and AI Opponents Kit

Build your own real-time strategy game. Play the showcase skirmish on the River Crossing map: box-select and command an army, march it in seven formations, gather gold and wood, build barracks and town halls, and take on four computer opponents under fog of war, with a live panel that switches every look. Install rtsKit from ZeroMind for the whole kit (eight unit types in medieval or sci-fi looks, five selection looks, multiplayer teams) and call FC.skirmish() for a complete match, or install fogOfWarKit alone for fog of war in four looks.

0score
Embed

Embed this world

Paste this code into your own page and the world plays right there.

Updated Nov 3, 2026
rtsstrategyreal-time strategyformationsfog of waraiselectionmultiplayerkittoolkit

Field Command

Everything you need to build a real-time strategy game in Zero, in one install. Select an army, march it in formation, gather, train, and fight a computer opponent that plays a real side, under fog of war. It works in multiplayer: every player commands their own team, everyone sees the same battle and nobody can command anyone else's units.

Play the showcase in this world: a river map with two bases, gold mines and forests, 20 units to command, a computer opponent, a gallery of every formation, unit, selection look and fog look, and a panel to switch them live. The computer plays Red and attacks within about a minute and a half; a second player who joins takes Red over, with its base, workers and army.

What's in the box

  • Selection like a commercial RTS: click, drag a box, Shift to add or remove, double-click to grab every unit of that type on screen, and one key for your whole army.
  • Control groups 1 to 9: set, recall, add, and jump the camera to them.
  • Orders with a queue: move, attack-move, attack, gather, stop, hold position and patrol. Hold Shift to queue, and see the path as waypoint lines.
  • Seven formations: line, column, wedge, box, circle, a staggered chequerboard of two offset ranks, and a loose skirmish spread. Groups arrive in shape and keep it around obstacles.
  • Eight unit types: worker, soldier, archer, siege engine, scout, healer, flier and hero, each in a medieval look and a sci-fi look, with their own health, speed, sight, cost and attack.
  • An economy and construction: workers gather gold and wood and carry it home, and lay new barracks and town halls (B and T): a ghost shows where a building fits and, in red, why a spot won't do or how much you are still short, and the building rises out of the ground as workers work on it. Town halls and barracks train units from a queue.
  • Four computer opponents: the rusher attacks early, the turtler builds up behind its defences, the raider goes for your workers at the mines, and the balanced one expands and mixes its army. Each gathers, lays its own barracks, trains and attacks; the turtler and balanced ones add a second barracks when they can spare it.
  • Fog of war in four looks: classic black and grey, soft mist, an old parchment map and chunky pixel tiles. Enemies stay hidden until you can see them.
  • Five selection looks: a ground ring, an outline glow, corner brackets, a hex footprint and health bars. The drag box and the move and attack markers match the look you choose.
  • A full RTS interface: a selection panel with health that breaks a mixed group down by type (click a type to keep only those units), building panels that say what is training and how long is left, order buttons, a control-group bar, resource counters, an idle-worker button (or the full-stop key), and "under attack" alerts with a minimap ping that Space takes you to.

Every part switches with one setting, for example FC.set("formation", "wedge") or FC.set("fogLook", "parchment").

Start in a minute

Install rtsKit from ZeroMind. It brings everything it uses: navKit for pathfinding, SecondWind for health, economyKit for resources, productionKit for barracks, aiKit and barsKit. Then put FC.skirmish() in a scene's build.luau (the README's Try it block) and press Play: a whole, fair match against the computer on the River Crossing map, with your camera on your own base. The README walks through gathering, training, building with B and T, and fighting, and has an "if you see this, do that" list.

Two guides ship with it:

  • How to make an RTS game: select and move units in formation
  • Build a small RTS skirmish with two bases, workers, a barracks and a computer opponent

To check that a match really plays, run require("rtsKit.playtest").run() in play. It confirms the bank, the starting resources, a worker's delivery, the barracks and the computer opponent.

Just the fog

Making a stealth or exploration game? Install fogOfWarKit on its own. It has the same four looks, hides enemies, offers line of sight and a minimap texture, and comes with its own how-to: How to add fog of war to a strategy or stealth game.

Known limits

  • Two players from one account: two engines on one account join as one player (#14448), so a true two-player session needs two accounts.
  • The browser build is untested here: it couldn't be started from here (#20946), and multiplayer frame cost on the web is a known engine issue (#20750).
  • Fog hides enemies on screen only: every machine receives every unit's position, so a modified game client could still see hidden enemies.
  • Seats trust the account a screen names: a scene with no player bodies has no engine record tying a machine to an account, so each screen states its own account when it joins. One account holds one seat at a time; a modified client could claim the seat of a player who is away.
  • Dropped connections: when a connection really drops and a player reconnects, their orders are refused and the match stops answering them (#19490). Reconnecting is not a supported way back into a running match until that engine issue is fixed.
  • One fog per engine: two matches in one world share the same fog.
  • Resources live on the host: if the host leaves, the next player takes the match over, and changes from the last second can be lost.
  • Where economyKit lives in the showcase world: it is installed under Market Square's dependency folder, not at the top level, where it shared a path with the older economyKit buildPlaceKit's own world holds.
  • Mesh errors when the engine starts: each time the engine starts on this world, the log shows 12 to 15 errors "asset '336f4feb-...' not found as type 'mesh'" from buildPlaceKit's copy, which productionKit brings (#22808). Switching to another world and back does not show them, and the match plays normally.
  • Building badges and productionKit: productionKit's own badge task freezes from the second play of a session on. rtsKit works around it from outside, without editing productionKit (an edit made inside an installed kit plays in the editor but players get the original, #22495), so the badges over your town hall and barracks keep drawing in every play of an rtsKit match. A scene that shows productionKit badges without rtsKit, before any rtsKit match has loaded, or a world that uses productionKit without rtsKit, still gets the frozen badges from its second play on.
  • An older material library copy in the showcase world: the world keeps a second copy of materialLibraryKit (1.3.1) because the building art needs it: productionKit's buildings use buildPlaceKit, whose sci-fi and masonry materials pin exactly that release, so the engine puts it back whenever it is removed. An engine update re-pins that copy's files, and then its lighting module fails to reload when the engine starts (#22894). It happened before 1.0.19 and again with the latest engine update; each time the copy was removed so the engine placed it fresh from its release, and the error stopped.
  • The ground can come up flat for a moment: on the current engine a baked landscape can build its ground before its heights and paint arrive. The kit rebuilds it at one and five seconds into play and keeps checking for two minutes, rebuilding whenever it is still flat, so on a slow start the map can look flat or grey for a few seconds. Before 1.0.24 it could stay grey; update to 1.0.24 or later.
  • Town hall roofs: productionKit's flat slate roof renders as a plain white block under the map's low sun, so rtsKit gives its own buildings a textured slate roof instead. productionKit itself is unchanged, so its buildings outside rtsKit keep the flat roof.
  • Fog texture previews: the four fog look textures' previews can stay as local staging entries after a push (#22116).

Comments · 0

Open discussion, no rating attached. Ask questions, swap notes, follow threads.

Sign in to join the discussion.

Documented parts · 10