# screens.match
BATTLEBOX's match flow as a module: `toTitle`, `toGarage(keep)` / `garage` (BUILD YOUR BOT from the title, GARAGE after a result), `testDrive` / `endTest` / `testing`, `startMatch`, `confirm` (FIGHT from the title, REMATCH from a result screen), `tick(dt)` and `countingBot` for the HUD's 10-count.
- **title** restores the last-used build once per session (`screens.garage.restore`) and poses both corners for the faceoff.
- **garage** opens `editor.session` on the player's build (`screens.garage.open`). With the 3D build view (`editor.view`) both corner bots are parked out of shot and the camera holds the `build` shot on the view's stand; without it a temporary turntable (`GarageTurntable`, materials `screens.turntable` / `screens.turntableRim`) stands the player's corner bot slowly turning under the `garage` shot. FIGHT closes the garage (the build goes to `Rules.setDesign("HAVOC")` and `last.json`) and starts the countdown; BACK returns to the title.
- **test drive** puts the build in the player's corner and runs phase `free` (bots drive, no clock) with the chase shot and the rival parked out of the way; `endTest` (Esc / pad B / ◀ GARAGE) returns to the garage with the session and its undo history intact.
- **countdown / fight / ko / decision**: 3-2-1, the 3:00 clock, KNOCKOUT on destroyed or a 10 s immobile count, the judges' decision at 0:00.
It sequences `game.rules` phases, `reset`, `decide` and camera shots and duplicates none of its numbers. A bot that cannot be posed in a frame (mid-rebuild) is logged once and does not stop the flow.
# game.rules
BATTLEBOX's constants, rules and live match state, shared by every part of the game. `require("game.rules")`.
- **Constants**: `TITLE`, `PLAYER` ("HAVOC"), `RIVAL` ("RIPTIDE"), `COLORS` palette, `MATCH_SECONDS` (180), `COUNTDOWN_SECONDS`, `KO_COUNT_SECONDS` (10), `IMMOBILE_SPEED`, `MAX_HEALTH` (100), `ARENA` (16 x 16 m box, wall height, camera inset), `STARTS` (start squares, yaw), `HAZARDS` (every floor saw, kill-saw slot, the screw pit and the four pulverizers, with damage footprints), `BOT_SPECS` (size, mass, drive, weapon RPM and damage).
- **Rules**: `weaponDamage(attacker, rpm)` = maxHitDamage x (rpm/maxRpm)^2, zero below 20% spin; `weaponKnockback`; `hazardAt(x, z)`; `decide()` for the judges (more damage dealt wins, then more health, then RIPTIDE).
- **State** (per peer, single-player vs the AI): `state()`, `bot(name)`, `opponent(name)`, `isLive()`; phases `free` / `title` / `countdown` / `fight` / `ko` / `decision`.
- **Mutations**: `registerBot`, `setPhase`, `applyDamage(victim, amount, cause, attacker?)`, `reset()`.
- **Events**: `on(event, fn)` returns an unsubscribe; `emit(event, payload)`. Events: phase, hit, hazard, damage, destroyed, ko, decision, reset, weapon, pulverize.
- **Camera**: `kickCamera(0..1)`, `setShot("chase" | "faceoff" | "orbit", focus?)`, read by `game.ArenaCam`.
- `formatClock(seconds)` -> "2:14".
State lives in `modules.state()`, so it survives hot reloads. Owned by the plan step; slices read it and may ask for additions in `design/spec.md`.
# screens.garage
The ROBOT MAKER's panel state and every action it takes (BUILD YOUR BOT), independent of drawing.
- **The bot being built lives in `editor.session`.** Every panel edit goes through the session (undo/redo, mirror twins, snapping, normalizing), and the module listens with `Session.on` to redraw. Multi-part edits are wrapped in `beginDrag`/`endDrag` so they are one undo step.
- **The 3D build view** (`editor.view`) is driven from here: palette cards call `View.beginPlace(type)`, the toolbar `setTool` / `setView` / `focus`, issue clicks `Session.select` + `View.focus`. `View()` hands the view `pointerBlocked(x, y)` (the panel rects the art reports, in window points) and the pad focus (`setPadEnabled`, pad Y). While the view is not up, the palette adds parts at a default spot and edits are pushed to the player's corner (~4/s) so the turntable bot shows them.
- **Zones and rows.** `rows(zone)` describes the toolbar, palette, right panel (PART inspector / BOT / OPPONENT), stats issues and the BUILDS menu as rows of items with action ids; `act(id, value)` runs them (taps, keys and pad all resolve to the same ids). The cursor (`move`, `select`, `cycleZone`, `setZone`, `togglePadView`, `back`) walks the same rows.
- **Inspector**: typed numeric fields for position (cm), rotation (°), size (by the type's `sizeRule`: diameter for round parts), every `params` entry (number / enum / bool / text), material picker with blurbs, paint override (role, custom colour, finish), mirror link (MIRROR / UNLINK), DUPLICATE / DELETE. Several parts selected: MOVE BY, and the size, material, params and paint they share. Fields take a typed value (Enter or leaving the field commits), ± steps (the snap step) and drag-scrub on the label.
- **Saves** (this machine only, written straight through at play): `/source/local/garage/builds/<slot>.json` as v2 `Design.encode` JSON, `last.json` (build, slot, opponent) restored once per session by `restore()`. A v1 save in `builds/` converts to v2 in place when first listed (original kept in `/source/local/garage/v1-backup/`); a v1 `last.json` converts on restore.
- `open(keep)` / `close()` / `flush()` / `tick(dt)` are called by `screens.match`; `setHooks{ fight, back, testDrive }` wires the flow. FIGHT is refused (with the first problem) unless `stats.legal`.
Drawn by `screens.garageArt`, routed by `screens.BroadcastScreens` (taps) and `screens.MatchDirector` (keys/pad via `screens.garageNav`).