Log inGet started
Package

rtsSkirmishKit.package

This package holds more than this page lists. See all of its files in its world.

README.md

rtsSkirmishKit: real-time strategy skirmish kit

A complete real-time strategy skirmish against the computer, or against a friend, for any Zero world (the showcase world calls it Warfront). Install rtsSkirmishKit, add one line to a scene, press Play.

What you get:

  • A whole game around the match: title screen, skirmish setup (map, your side, opponent, difficulty, victory, start, army look, selection look, time of day, fog), a ready check when two people play, a 3-2-1 countdown, an in-match menu that pauses the battle (Resume, Restart, Quit to title), and victory and defeat screens with match stats that count what you would count, Rematch, Change setup and Main menu.
  • The match: two bases; workers start gathering at once and carry gold from mines and wood from trees back home; build a town hall, barracks, farm (supply), guard tower and walls; train workers, soldiers and archers (plus the rest of rtsKit's roster); move, attack, attack-move and gather orders; click and box select; fog of war per side that starts fresh every match; a computer opponent that gathers, builds, trains and attacks in waves with reinforcements.
  • Every way to play, each one setting: six victories, four opponents at four difficulties, four start modes, seven maps (forest, desert, island, snow pass, a forest you cut your way through, an arctic bay, an Alpine valley) plus your own through Maps.register, seven looks (medieval, sci-fi, cartoon, painted, comic, sketch, anime), five selection looks, six times of day, four fog styles, and either side to play.
  • Every device: keyboard and mouse, gamepad and touch (phones too, portrait and landscape) for selection, every order, the build menu, the camera and all menus.
  • Always multiplayer: a second player takes the other side and sees the same battle through their own fog; the host checks every command, so nobody can order the other side's units.
  • Feel: sparks, clashes, dust and explosions on hits, deaths and fallen buildings, a fanfare for finished buildings, and battle music that swells with the fighting.

Five minutes to a playable skirmish

  1. Install rtsSkirmishKit from ZeroMind (it brings rtsKit and the kits it needs). In a large world this takes a minute or two.
  2. Open a scene's build.luau. A brand-new world has no scene yet: make one with zero scene create --startup skirmish menu in the engine shell (or New scene in the editor, template Menu, set as startup), then open scenes/skirmish.scene/build.luau and replace its contents with:
local Skirmish = require("rtsSkirmishKit.api")

function content()
	Skirmish.skirmish()
end
  1. Press Play. The title screen appears; choose Skirmish, pick your options, Start match.

That's it. Other defaults in one table:

Skirmish.skirmish({ map = "frostpass", victory = "regicide", difficulty = "hard", look = "cartoon", timeOfDay = "dusk" })
Skirmish.skirmish({ side = "red", selection = "brackets" })   -- play Red, corner-bracket selection
Skirmish.skirmish({ startPhase = "countdown" })                -- skip the menus, straight into a match

Controls

Keyboard + mouseGamepadTouch (phones too)
Selectclick a unit or building, drag a box, Shift adds, double-click selects the typesteer the cursor with the right stick, A selects, hold A and move to drag a box, d-pad up selects the armytap; Box button then drag; Army and Clear buttons
Ordersright-click: move, attack or gather by what is under the cursor; A then click = attack-move; S = stopB = smart order at the cursor (move, attack, or gather on a mine or tree); X then A = attack-movetap ground, enemy or resource after selecting; Attack button then tap = attack-move
Build and trainselect a worker (or a town hall or barracks), click a button on the command card, click to place, right-click cancelsY focuses the command card, d-pad picks, A confirms, then A places on the map; B backs outtap a card button, tap to place
Cameraarrow keys or the screen edges pan, the mouse wheel zooms, middle-drag turnsleft stick pans, RT and LT zoom (the right stick moves the cursor)one-finger drag pans, pinch zooms
Menusclick, or arrow keys and Enterd-pad and A / B, bumpers switch setup tabs on small screenstap
Pause menuEsc (once nothing is selected; the first Esc clears a selection) or F10Startthe menu button, top left

Button prompts follow the device you touched last. On a phone the HUD fits the screen (minimap and command card size themselves to the width, buttons never smaller than 44 points, and the hint along the bottom wraps over several lines inside its panel) and stays clear of the engine's own Menu button. Checked at 357 points wide (a phone in portrait); on a screen narrower than about 300 points, such as a squeezed editor Scene panel, the resource chips at the top and the objective banner run past the edges. On a desktop or tablet screen nothing in the HUD covers anything else at the normal UI size or at 2x: the objective line sits on the top row only when it clears the whole chip row (Rank pill, gold, wood, army and the idle chip) and otherwise moves to a line under it, and the keyboard hints wrap inside the selection panel instead of running under the command card.

Balance

A normal player can beat the easy computer in well under ten minutes. Warfront sets the pace on top of rtsKit while a skirmish runs:

  • Supply: a town hall supports 20 units and each farm 10 more (rtsKit alone: 10 and 8), and a farm costs 40 wood (rtsKit: 60). require("rtsSkirmishKit.startModes").SUPPLY and .FARM_WOOD change it.
  • Farm spots: every map offers at least five spare build spots per base that take a farm or a barracks (the play check proves it for every map).
  • Easy computer: slower income, smaller and later waves, one barracks and no guard towers or walls. Hard and brutal gather faster, start richer, attack early and keep sending reinforcements.

Feel: hits, explosions and music

rtsSkirmishKit.feedback makes the battle feel alive, for every player: juiceKit sparks and sword clashes on hits, dust when a unit falls, a big explosion when a building is destroyed, a burst and a fanfare when a building is finished, and soundstage battle music that plays the menu theme around matches, the explore track during a match and swells into the action track as the fighting heats up (the music set follows the look: fantasy, cartoon or sci-fi). Effects are throttled so a big brawl stays smooth. require("rtsSkirmishKit.feedback").enabled = false turns it off, .LEVEL (0..1) scales the effects, .MUSIC maps looks to music sets.

Settings

Every value is one setting: Skirmish.set(key, value) while the game runs (host, before a match), Skirmish.skirmish({ key = value }) for the defaults, or the setup screen. Keys and values: require("rtsSkirmishKit.settings").OPTIONS.

keyvalues (default first)
mapriverCrossing (River Crossing, forest), dunes (Sunscorch Dunes, desert), isles (Twin Isles, island), frostpass (Frost Pass, snow), deepwood (Deepwood, a forest you cut your way through), glacierBay (Glacier Bay, arctic), highlandFord (Highland Ford, an Alpine valley, the guide's worked example), or your own (Maps.register)
sideblue, red: the side you play; the computer or a second player takes the other
opponentbalanced, rusher, turtler, raider
difficultynormal, easy, hard, brutal
victoryconquest, annihilation, regicide, kingOfTheHill, treasury, survival
startModenormal, fastStart, rich, nomad (workers only, no base)
lookmedieval, scifi, cartoon (toonBlocks), painted (watercolorBlocks)
selectionring, outline, brackets, hex, healthbar
timeOfDayday, dawn, dusk, night
fogLookclassic, mist, parchment, pixel
fogtrue, false
redhuman (a second player takes the other side when one joins), computer

Numeric tuning that passes through: treasuryGoal (3000), hillSeconds (90), survivalSeconds (480), seed.

Each map has one name everywhere (setup screen, Maps.list(), docs); maps.module is the only place it is written.

Two players

A second person who opens the world while you are in setup is seated on the other side (red = "human"). Their setup screen shows your choices live and a Ready button; your Start match says "Waiting for player" until they press it. Both machines then build the same match: the host runs the simulation and checks every order, each player commands only their own units and sees through their own fog. A player who joins mid-match takes over the computer's side; when they leave, the computer plays it again. Anyone beyond two watches. Every building, the town halls and barracks drawn by productionKit included, appears on both screens (fixed in rtsKit 1.1.3: before it, a guest saw units but no buildings).

Big battles

Measured on 2026-11-12 in the desktop app (Linux, an engine client running the match as host, vsync on): Sunscorch Dunes, 80 soldiers and archers against 80 plus both starting armies, about 180 units in one brawl in the middle of the map, frame times sampled every frame for 12 seconds of fighting (734 frames):

frame time
typical (median)16.1 ms (vsync-paced 60 fps)
95th percentile18.4 ms
99th percentile25.5 ms
worst single frame97.9 ms (one hitch)

The simulation and every script together cost about 5 ms of each frame; the rest is waiting for vsync. The simulation runs on the host only, and every other screen draws from compact snapshots, so a guest's machine does less work than the host's.

Measured again for 1.0.20 (same map and armies, 178 units, an engine sub-client as host, three engine clients on one machine): the first big fight after the app started ran at a median 17.4 ms with a 95th percentile of 43.6 ms, a 99th of 111 ms and a worst frame of 271 ms, because unit and effect art is prepared the first time it appears; a second fight in the same session ran at 17.7 / 29.4 / 42 / 59 ms. The largest steady script cost in a fight is rtsKit's Commander at about 2.5 ms a frame; nothing else reaches 0.5 ms.

In the browser a playtester measured about 17 ms a frame in a full match (reported by the world's owner, 2026-11-12; not repeated by the kit's own tests, which run in the desktop app and cannot open the browser version of the game: engine issue #20946). Measure on your own target devices before relying on 150+ units on a slow phone.

Scripting

local Session = require("rtsSkirmishKit.session")
Session.phase()                  -- "title" | "setup" | "countdown" | "playing" | "results"
Session.on("phase", function(p) print("now", p) end)
Session.results()                -- winner, reason, duration, per-team stats, won
Session.match()                  -- the running rtsKit match, for anything rtsKit can do
Session.setReady(true)           -- this player is ready (two-player setup)

require("rtsSkirmishKit.playtest").run({ map = "deepwood" }) plays a whole match in about 30 seconds and checks it (start, countdown, both bases, farm spots, objective, victory, stats, rematch).

Your own map

local Maps = require("rtsSkirmishKit.maps")
Maps.register(MyMap.INFO, MyMap)   -- adds it to the setup screen and Skirmish.set("map", id); call on every peer (the scene build)
Maps.build("myMap")                -- in edit mode: a temporary preview, never recorded into the scene
Maps.clear()                       -- removes the preview

A map is a module whose build hands a SPEC (ground, bases and build spots, mines, woods, rocks, water, navigation blockers, scenery) to require("skirmishMapBuilder.builder").build; its ground is baked with require("skirmishMapBuilder.terrainBake"). Both come from the skirmishMapBuilder package, and the rules of victory from skirmishVictory (require("skirmishVictory.rules")); installing rtsSkirmishKit brings both. The old names rtsSkirmishKit.maps.common, rtsSkirmishKit.maps.terrainBake and rtsSkirmishKit.victory still work. The guide Example: build a second skirmish map builds one step by step, including how to wall a river so armies use its fords, which water to use, and how far in from the edge hills to keep build spots. In Play, a running session keeps the map code it loaded and Rematch keeps the built map, so leave Play and press Play again after editing a map module.

What's inside

api (front door), settings, session and the Session component (the synced state machine), victory, difficulty, startModes (openings and supply), looks, feedback, maps with seven map modules and their baked grounds, screens and the Screens component, playtest, a test suite, and two guides:

  • How to make a real-time strategy game (rtsSkirmishKit.package/guides/how-to-make-a-real-time-strategy-game)
  • Example: build a second skirmish map (rtsSkirmishKit.package/guides/example-build-a-second-skirmish-map)

Built on rtsKit (Field Command) and through it navKit, SecondWind, economyKit, productionKit, saveKit, fogOfWarKit, aiKit, barsKit and controlsKit; menus from menusKit and MatchFlow; looks from styleKit with toonBlocks and watercolorBlocks; scenery from alpineProps, desertProps, tropicalProps, forestProps and arcticProps; effects from juiceKit; sound and music from soundstage.

Tests

zero tests run rtsSkirmishKit (edit mode) runs the kit's suite; it passes in a fresh world. zero tests run rtsKit checks the toolkit underneath.

Changes

  • 1.0.26: release for everyone: the package descriptions of rtsSkirmishKit, skirmishVictory (1.0.1) and skirmishMapBuilder (1.0.1) now say what each gives you and how to use it. No change to the game.
  • 1.0.25: a polish round from playing and from watching someone build with the kit. Built on rtsKit 1.1.13 (Field Command pull requests #14 and #15).
    • An in-match menu: Esc (once nothing is selected; the first Esc still clears a selection), F10, the pad's Start or the menu button at the top left opens it. Resume, Restart and Quit to title for the host, whose menu holds the battle for everyone (no simulation, no computer turns, no building or training, the match clock stops); a guest's menu says the host is in charge, and the guest's screen shows "Paused" while the host has it open. The match pauses through rtsKit's new paused field.
    • A rematch starts clean: the last match's result, stats and clock are cleared the moment a new match (or a restart, or the title) begins.
    • End-of-match numbers count what you would count: "Buildings lost" reads against everything a side had (its opening base and what it raised), for example "5 of 5", with the kinds underneath ("Town hall, 2 barracks, farm, tower"), so the number adds up even for buildings hidden in the fog; "Buildings raised" counts what went up during the match; wall segments have a line of their own instead of each counting as a building.
    • The command card shows the pad's buttons on a gamepad: the button that opens the card, and on the focused button the one that presses it (rtsKit 1.1.12).
    • Tidier on screen: the minimap takes the map's ground colour (sand, snow, ice, sea, Alpine meadow) instead of grass green on every map (rtsKit 1.1.13); the first match out of the box is against the easy Balanced computer on River Crossing.
    • More variety: three more looks (Comic, Sketch, Anime) and two more times of day (Overcast, Storm), each one setting like the rest.
    • Two parts of the kit are installable on their own: the six ways to win are the package skirmishVictory (skirmishVictory.rules), and the map builder, the terrain baker and the open-water material are the package skirmishMapBuilder (skirmishMapBuilder.builder, .terrainBake, .openWater). Installing rtsSkirmishKit brings both; rtsSkirmishKit.victory, rtsSkirmishKit.maps.common and rtsSkirmishKit.maps.terrainBake still work and forward to them. A single water sheet now defaults to open water too (Sunscorch Dunes and Twin Isles name the River Crossing water they always used), and discBlockers covers a disc with a real unrotated octagon.
    • The second-map guide reads in order for a newcomer: twelve numbered steps, each ending in a check, with the water options, watertight rivers, how far the edge hills reach into the field and previewing the map in the step where you need them.
  • 1.0.24: the release of pull request #2 (the 1.0.23 and 1.0.22 entries below) from this world; its contributor had already published 1.0.22 and 1.0.23 from their own world, and a version can be published once. Reviewed here on the kit's own maps: Highland Ford's stream is walled along each reach and a soldier ordered straight across it walks round by the ford without entering the water; the playtest passes 15/15 on all seven built-in maps; a map previewed in edit mode leaves 0 pending scene edits while built and after Maps.clear(); the open-water material draws as water away from River Crossing. Corrected on top: Sunscorch Dunes and Frost Pass build their ridges with segmentBlockers too, so their ridges now block along their whole length (the 1.0.22 entry said no built-in map changed); the second-map guide names 1.0.24 as the first version whose previews stay out of the scene, and describes the blocker boxes as reaching halfWidth either side of the line. A new test checks that segmentBlockers gives unrotated boxes with no gap along a line at any angle.
  • 1.0.23 (contributed in the same pull request as 1.0.22): previewing a map in edit mode no longer writes it into the scene. Maps.build outside Play recorded every tree, rock and mine into the open scene as authored edits, and Maps.clear() afterwards left edits naming entities that were gone, so the scene refused to build ("missing-parent" conflicts) until they were cleaned out by hand; the guide never said so. The map root is now made temporary when built outside Play (by the shared builder before any child is spawned, and by Maps.build for a map with a builder of its own, such as River Crossing), so a preview is drawn but never recorded; in Play nothing changes. The second-map guide has a new step 6, "Look at it while you build it" (play-testing is now step 7). Checked in edit mode: building Silverrun Vale (84 trees) and River Crossing left 0 recorded scene operations and 0 scene changes, both while built and after Maps.clear(), and the preview renders; zero tests run rtsSkirmishKit 38/38.
  • 1.0.22 (contributed from a world that built its own map with the second-map guide): rivers built with C.segmentBlockers no longer leak. It returned one long rotated box per segment, but Common.build registers nav blockers as axis-aligned boxes and drops the rotation, so a north-south stream got short east-west bars across it with open water between them (on Highland Ford the stream between z -54 and -46 was walkable and a route from bank to bank walked straight through it at z -53). It now steps square boxes half across along the line no more than half apart; on Highland Ford the whole stream line is blocked and the same route goes round by a ford. Water on a map of your own draws as water: a spec's waters sheets took rtsKit's River Crossing water, which samples River Crossing's own depth map over River Crossing's rectangle and drew a checkerboard on another map. The kit ships maps/openWater.material (the same tuning, no depth map) as C.OPEN_WATER, the default for waters sheets; no built-in map's water changes (Glacier Bay names its own material, Twin Isles uses water). Sunscorch Dunes and Frost Pass build their ridges with the same segmentBlockers, so their ridges now block along their whole length too. The second-map guide's step 4 now says how blockers, water sheets and the frame hills' reach work. Checked: zero tests run rtsSkirmishKit 38/38, the playtest 15/15 on the new map, and pathing on Highland Ford before and after.
  • 1.0.21: no more empty "Idle" circle over every building. productionKit's default badge is a dial with the product's icon inside, and a town hall or barracks that is not training showed an empty dark circle labelled Idle. The kit now sets productionKit's slim "minimal" badge on every screen before a match starts: a small status dot and a thin bar that fills while the building trains, over your own buildings only (enemy buildings still show nothing). The Session component's badgeStyle field picks another style per screen: minimal, ring, badge, float or none. Checked: your town hall and barracks draw the minimal badge, enemy ones none, no errors.
  • 1.0.20: polish from playing and from the fresh-install report. The match countdown no longer leaves errors in the log, and its sounds always have a live source: MatchFlow's audio puts its sound source on whatever camera is active the first time and keeps it, and a skirmish swaps cameras every match, so from the second countdown on each 3, 2, 1 and GO played into a removed camera and logged "parent ... never materialized" (four per match). The kit now plays MatchFlow's own countdown clips, at MatchFlow's pitches, through an audio source it creates on the menus and keeps; the fix for MatchFlow itself is filed on its world. Checked: a match start logs no orphaned entities and no errors. "Big battles" carries a new measurement with 178 units, from a cold first fight and a warm second one.
  • 1.0.19: the release of pull request #1 below, from this world. Its contributor had already published the same change as 1.0.18 from their own world, and a version can be published once.
  • 1.0.18 (contributed as pull request #1 by someone who installed the kit in a fresh world; 1.0.17 was an earlier push of that request): fixes from installing the kit in a fresh world and playing every map, start mode and victory. The setup screen's map cards show their whole description: at 1920 x 1080 the cards are 83 points tall (two columns of four rows) and the art band left too little room, so the description was cut off mid-line on River Crossing, Frost Pass, Deepwood, Glacier Bay and Highland Ford. A short card now gives up the art band (and the gap it kept) before it cuts any text, and steps an extra-long description down a size (Deepwood). The playtest no longer fails Fast start matches: the opening lays two farms on build spots 1 and 2, and setting them aside did not clear their footprints from the navigation grid, so those spots read as "blocked"; a spot a building already stands on (the opening's, or one the computer laid there) now counts as taken. The playtest can finish an Annihilation match: it only knocked the buildings down, which never wins Annihilation; it now removes the enemy units too. The test suite passes in a world that adds its own map: the settings test counted every listed map as built in, so registering a map the way the second-map guide shows made zero tests run rtsSkirmishKit fail ("Expected 8 to be 7"); it now counts the seven built-in maps by id. A world made with the five-minute recipe can be published: the menu and strategy cameras are made at runtime, so a scene holding only Skirmish.skirmish() had player intent "none" and no saved camera, and zm push refused it ("player_scene.none_without_camera"). Warfront.skirmish() in a build now also saves a low-priority WarfrontSceneCamera over the map centre (priority 0, under the menu camera's 5 and the strategy camera's 10, so it never takes the screen from them); pass camera = false to leave it out.
  • 1.0.16: built on rtsKit 1.1.11 (Field Command pull request #13), which takes the last em dash out of the toolkit's text; the showcase world's own files (plan, scene and world entry files, world settings) have none either. Played again from the title to a win and a loss.
  • 1.0.15: built on rtsKit 1.1.10, which this world could now take in through its install: the shared economy test passes whoever is in the room. Of the two loose copies of rtsKit files, the update retired the test-suite copy, but the commit that took the update wrote it back; both stay, byte-identical to the 1.1.10 release (see Known limits).
  • 1.0.14: text only: the four file-header comments that still held em dashes now use colons, so no text in the kit has one.
  • 1.0.13: no error in the log when a match starts. The menu camera used to be removed in the same frame the strategy camera was created, which left a frame or two with no camera drawing at all; productionKit's building visuals ask for the drawing camera every frame and logged "entity() requires a string entity ID" in that gap. The screen's old camera now stays until the new one is actually drawing (match start, rematch and back to the title), so there is no blank frame and no error. Maps added with Maps.register stay in the list when the maps code reloads (they are kept in engine-held module state). A won or lost match always reaches its end screen: once the judge decided, the results were published two frames later, but in between the host's "take over a running match" step made a new judge, which at a fast match speed (or after one slow frame) decided again and pushed the results back every frame, so the match never ended. The host now waits for the results while a match is being finished, and a test guards it. rtsKit's shared economy test no longer depends on who is in the room: fixed upstream as rtsKit 1.1.10 (Field Command pull request #12), which this showcase world could not take in yet (see Known limits).
  • 1.0.12: corrects the 1.0.11 entry. The showcase world still keeps two of rtsKit's files, the production module and the test suite, as files of its own beside the installed kit, byte-identical to the rtsKit 1.1.9 release. The engine writes them back at every commit even when the commit stages their removal, so they could not be cleared yet (reported to ZeroMind). This is about the Warfront world only: installing rtsSkirmishKit in another world brings rtsKit in as an ordinary install.
  • 1.0.11: built on rtsKit 1.1.9. Nothing in the desktop HUD covers anything else at either UI size: the objective banner reserved too little room for rtsKit's top-right chips, so once the "idle" chip showed it ran into the Rank pill (and at 2x covered its first letter); it now stays on the top row only when it clears the whole row and otherwise sits on a line under it. In rtsKit 1.1.9 the keyboard hint line wraps inside the selection panel, which no longer runs under the Formation part of the command card. Two of the last four loose copies of rtsKit's files (the Commander and the sim) are gone; see 1.0.12 for the other two.
  • 1.0.10: built on rtsKit 1.1.8. The end screen shows the real totals and freezes them when the match ends: the deciding building fell before rtsKit announced it, so the screen counted one building lost too few (2 buildings shown as 1), and it showed the live counters, so units finishing training after the end kept adding to them; the session now waits for the match's last events, checks buildings lost against the simulation, copies the stats and stops counting. Checked with a defeat against a hard rusher (Blue lost 2 buildings, Red trained 25, unchanged 15 s later) and a victory (Red lost 4 buildings, trained 6). The title screen shows the published version (it still said 1.0.6; a test now keeps it in step with package.yaml). The phone hint line wraps instead of running off the right edge (rtsKit 1.1.8); the 1.0.9 entry's "nothing on screen covers anything else" missed that the hint was cut off.
  • 1.0.9: built on rtsKit 1.1.7, after playing whole matches with a gamepad and on a phone-sized touch screen (2x density) in the editor's own window. Phone and pad controls keep working from the second match on (before, every rematch left them dead); taps reach the map everywhere on a phone screen, pinch zooms out as well as in, and minimap taps land where they point. Checked on the phone: box select, tap orders, Stop, Attack-move, Patrol, Hold and Move after Hold, the build menu with its placement ghost and refusal reasons, training, rally points, the Army button, camera drag, pinch and minimap, and a whole match won by taps alone; nothing on screen covers anything else in the HUD, the build card, the setup screen or the victory screen. Checked on the pad: stick pan, LT/RT zoom, cursor, hold A to box, B order, X then A, d-pad army / stop / hold, Y command card.
  • 1.0.8: built against rtsKit 1.1.6 (the selection panel's key hint names the new army key); the reuse review rates every installed part. No change to how the kit plays.
  • 1.0.7: fixes from playing the showcase on every device. Every starting worker goes to work, on every map and start mode and on the very first match after a world loads: units are put down before the navigation bake finishes, so a worker placed on a building, a guard tower or a mine stayed inside it; rtsKit 1.1.4 walks them out once the bake is done, and a nomad side (no base) now has all its workers found a town hall at the base spot and then gather. The defeat screen speaks from your side: the line under the title said "The enemy base was destroyed." when your own base fell; each screen now phrases the result for its own side ("Your base was destroyed.", "You held the centre…", a watcher's "Blue's base was destroyed."), and Victory.describe(code, outcome) does it for your own screens. Real stats: workers trained at a town hall were not counted as trained (rtsKit 1.1.4). Seven maps everywhere: Highland Ford, the map the guide builds, ships with the kit as its seventh map, so the setup screen, the README, the guides and the package description all say seven. Army hotkey: backquote or Ctrl+A (F2 is the editor's pause key; rtsKit 1.1.5 and 1.1.6, which also fixes the selection panel's key hint).
  • 1.0.6: renamed from warfrontKit; guests see buildings; arrow keys and wheel; phone taps on command-card buttons.

Known limits

Engine problems that are already tracked carry their engine issue number. The rest are the kit's own and say so.

  • Device checks use the engine's input simulator, not a person at a keyboard, a pad or a physical phone. 1.0.9 was played in the editor's own window because a separate test client points its screen-to-map step at the wrong camera (the menu camera), so clicks and taps checked there cannot be trusted (engine issue #25239). A farm laid by taps alone was not seen: every spot tapped on the crowded test base was correctly refused ("too close to another building", "too close to gold or trees"); the same build order sent directly lays one.
  • Phone layouts were checked on a stand-in, not a real phone screen. The editor has no real phone-sized screen preview (engine issue #22607), so phone checks resized the game view to 780 × 1688 and set a 2x display density, which is what a real phone reports. Taps on command-card buttons (button first, then the target on the map) and the Menu-button clearance were verified that way with the input simulator, not on a physical phone.
  • The ten-minute win was checked by a scripted player, not by hand. It used real clicks on Skirmish and Start match, then a script that gathers, builds farms on the map's spots, trains soldiers and archers and attacks with 16 or more units: it beat the easy Balanced computer on River Crossing in 6 min 18 s of match time. A person plays differently; harder levels take longer by design.
  • Two players across the network were played by the world's owner and a friend (units, fog and orders agreed; buildings were missing on the guest, which 1.0.6 with rtsKit 1.1.3 fixes). The building fix itself was checked with two engine clients on one machine, not again across two computers.
  • The browser frame time is someone else's measurement. The kit's own checks cannot open the browser version of the game (engine issue #20946), so the browser figure under "Big battles" is the world owner's playtest, not a measurement the kit repeated.
  • One shared economy test used to depend on who was connected (the toolkit's own test, not the engine). rtsKit's check "economyKit runs its bank on the machine the match names" read its default bank machine while a running match had already chosen one, so it failed when an extra editor was in the room. Fixed in rtsKit 1.1.10 (Field Command pull request #12); this world now runs rtsKit 1.1.11, and the check passes with other machines in the room.
  • Two loose copies of rtsKit files in the showcase world (engine issue #25242). The Warfront world keeps rtsKit's production module and test suite as files of its own beside the installed toolkit, byte-identical to the rtsKit 1.1.11 release. Updating the toolkit through its install (to 1.1.10, then 1.1.11) retired the test-suite copy each time, but the commit that took the update wrote it back with the new bytes, and the production copy, which neither release changes, stayed throughout. This is about the Warfront world only: installing rtsSkirmishKit in another world brings rtsKit in as an ordinary install.
  • Reconnecting after a dropped connection seats a player again by account, but a player who drops mid-match loses any orders in flight (the kit's own limit).
  • Deepwood is heavy: about 1600 entities, about 2.2 s to build; the other maps take 0.4 to 1.5 s (the kit's own limit).
  • Renamed in 1.0.6: the package was published as warfrontKit up to 1.0.5. Code that required warfrontKit.* now requires rtsSkirmishKit.*; nothing else changed.