# Undercooked A cooperative, **in-browser**, Overcooked-style kitchen game: 1–4 players share one kitchen over WebSockets, cook orders against the clock, and climb a campaign of levels that get progressively harder. Lobbies are **anonymous** — no accounts, no email, no password: you create a room, share the 5-character code, play. > Working title. "Overcooked" is a trademark of Ghost Town Games/Studio MDG; this > project is an independent homage with its own art, code, and content. ## Status Phases **01** (runnable service scaffold), **02** (level content, schema and validation), and **03** (the deterministic simulation kernel: fixed-step tick, movement and collision, the action button, the hands, the replay goldens) are **complete**; the next pending phase is `04_kitchen_pipeline_and_scoring`. What runs today: - **The service.** The Python toolchain is locked (`uv.lock`), configuration is a single typed, validated `Settings` object (`DEBUGPY` support included), and `uv run undercooked` starts a FastAPI server that serves the client shell at `/`, the browser assets from `app/static/`, and `GET /healthz` — which answers `{"status":"ok","version":"0.1.0","rooms":0}` (`rooms` stays `0` until phase 05 owns a supervisor) — with the security headers (CSP `default-src 'self'`) on every response. - **The content.** The recipe book and the first two campaign levels live in `levels/`; `sim/level.py` parses them into typed models, `sim/validation.py` runs PLAN §8's named rules, and `create_app` loads + validates that bundle at startup and **refuses to boot** broken content — the named-rule report goes to stderr and `undercooked` exits `2` instead of serving a half-working kitchen. `GET /api/levels`, `GET /api/levels/{id}` and `GET /api/config` answer from it, and `undercooked-levels` gives authors the same gate from the command line (`docs/LEVELS.md` is the schema reference). - **The tick.** `sim/state_build.py` builds a round from level + seats + seed and `sim/step.py` advances it in whole `0.05` s substeps (20 Hz, A4) with a splitmix64 RNG seeded from the round seed — pure (no clock, no `random`, nothing mutated), replayable from a seed plus an input script, and 100 % covered. The clock, the input contract and the round's end condition are real. `docs/SIMULATION.md` is the contract, `tests/sim/test_rng.py` locks the generator's published vectors. - **Walking the kitchen.** `sim/movement.py` + `sim/collision.py` are stage 3 of the tick: intent is clamped server-side (`move=(50,0)` walks at 3.5 tiles/s, not 175), accelerated at 30 tiles/s² and integrated one axis at a time against an axis-aligned sweep, so a cook stops flush against a wall instead of inside it, slides along it for free, cannot tunnel a 1-tile wall even at the coarsest legal `dt`, and cannot clip a diagonal corner. Walls, counters, void, off-map and the solid fixtures (`spawn_shelf`, `chop_board`, `stove`, `prep`) block; `serve`, `sink` and `trash` do not. Cooks soft-push each other apart symmetrically and positionally — a bump never injects velocity — and only a genuine terrain deadlock drops an input, the later-received one, exactly like the kernel's arbitration. Stun (`0.6` s) pins velocity and position and reports one `stunned` event on entry; facing follows the last non-zero intent, so an action press while standing still does not spin the cook. Proven by hand-computed geometry in `tests/sim/test_movement.py`, by a 2000-substep four-cook random walk from the sim's own RNG that re-checks containment, non-overlap and hash equality after *every* substep (`tests/sim/test_movement_stress.py`), and by the same walk on the shipped levels through the whole `step()` (`tests/sim/test_movement_kernel.py`). - **The action button.** `sim/interact.py` is the second half of stage 2 of the tick: the one `action` flag per frame becomes one press per rising edge, so however long the button is held there is one effect — and one named refusal when there is nothing to do (`DENIED` with `out_of_reach`, `hands_full`, `station_busy`, `contested_lost`, … in the payload, which the client turns into a nudge; a silent no-op is the failure mode PLAN §5 bans by name). A press resolves a reach zone — the tile in front, then the two diagonal-front tiles (a 0.6-tile forgiveness beyond the 1-tile reach), then the tile underfoot — and a ladder picks the verb: a full hand sets its item down on the fixture (the spawn shelf is the escape hatch), a free hand picks from a ready fixture or shelf stock, a stunned cook is refused before the target is even read, and a fixture owns what is on it (an onion on a chop board is *to be chopped*, not grabbable). Two cooks pressing the same item in the same substep are arbitrated by arrival, `seq`, then seat index — the loser is told `contested_lost`, never left wondering. The work verbs (chop, cook, plate, serve, wash) are named by the ladder but no-ops until phase 04's pipeline spends them (the long-press trash is real — see "The hands" below); `docs/SIMULATION.md` §"The action button" is the contract. Proven by `tests/sim/test_targeting.py` (hand-computed reach geometry, the press edge through the whole `step()`) and `tests/sim/test_verbs.py` (a table that covers every `Verb` and every `DeniedReason`, plus the gate's contested arbitration). - **The hands.** `sim/carry.py` is what the verbs *do*: one carried item per cook (a second pick is `hands_full`), no floor drops in v1 (a press at open floor is the named `nothing_here`), and a set-down is a *placed object* — `RELEASE` / `PLACE_ON_STATION` / `PLATE_DISH` put the item on the fixture and stamp it with a mark, so a teammate's pick of a set-down within 20 ticks is a `HANDED_OFF` with both ids (the sanctioned pass) and an unmarked pipeline input stays the work press's. The trash is long-press and always available: holding the button over the can for 8 substeps destroys the carried item (`TRASHED`, the raw `−2` score nudge in the payload for phase 04's clamped scoring, `counters["trashed"]` up by one); a short press and a walk-away do nothing. A 100-tick fuzz of random simultaneous presses re-checks the conservation law (`hands + stations + trashed == initial`) after every tick, and a scripted two-player pass-and-contest reaches its committed golden hash. `docs/SIMULATION.md` §"The hand" is the contract (phase 09's co-op E2E asserts exactly this tie-break). Proven by `tests/sim/test_carry.py` and `tests/sim/test_replay_carry.py`. - **The rules are tests, not promises.** The no-external-asset rule is `tests/unit/test_no_external_assets.py`, "no level or recipe id in Python" is `tests/unit/test_content_not_hardcoded.py`, the documentation set is guarded by `tests/unit/test_docs_index.py`, and `bash .agents/validate.sh` is the gate the phase pipeline runs after every task. What does not exist yet: the rest of the simulation (the cooking pipeline, order spawning and scoring in phase 04), rooms and the WebSocket protocol (05-06 — the lobby buttons answer "Not implemented until phase 05.") and the playable Canvas renderer (07). Execute phases with the `phased-execution` skill (`auto-phase.sh`); it always takes the lowest-numbered directory still in `.agents/phases/todo/`. ## How to play The intended loop, once the room flow ships: open the site, **Create lobby**, read out the 5-character code, everyone else **Joins** with it, the host picks a level, the room readies up, and the kitchen starts. Each cook has one movement control and **one action button** that picks up, uses and puts down whatever is in reach — one carried item at a time. Orders appear in the HUD with a shrinking deadline; assemble the dish and serve it at the window before the timer runs out. Levels escalate: more recipes, fewer stations, hostile floors. Nothing is saved between rounds and nothing identifies you: the browser keeps only a random per-tab token and the last code you typed, both in `sessionStorage`. What actually works today is the shell of that: the page loads, normalises a typed code to five uppercase alphanumerics (codes themselves are Crockford base32, and only get issued once phase 05 runs the room supervisor), and answers "Not implemented until phase 05." Movement keys and touch controls are defined by the phase-07/08 client and documented in `docs/CLIENT.md` once that phase writes it. ## Quickstart (development) Requires [`uv`](https://docs.astral.sh/uv/), Python ≥ 3.12, and `podman`/`docker` for container builds. **There is no database** — all live game state is in memory. ```bash uv sync --extra dev uv run undercooked # http://127.0.0.1:8000 (shell page + /healthz) uv run undercooked --host 0.0.0.0 --port 8000 # e.g. to reach it from a phone uv run undercooked --reload # dev reload uv run undercooked --levels-dir levels # point at another content dir curl -fsS http://127.0.0.1:8000/api/levels # the campaign cards the lobby will show curl -fsS http://127.0.0.1:8000/api/config # client-safe settings + protocol version ``` `python -m undercooked` is the same command (the container uses it). A flag always beats the environment, which beats the built-in default. There is no `/docs` or `/openapi.json`: FastAPI renders those pages from a public CDN, which this project forbids. The validation the server runs at startup (every level file loads, and no rule of PLAN §8 is broken) is a command too — `undercooked-levels`, see **Authoring content** below. Debug the server with a real debugger attached (dev only - the listener binds `0.0.0.0`, so never enable it on a public host): ```bash DEBUGPY=1 uv run undercooked # opens a debugpy listener on :5678, then serves as usual ``` Authoring content: ```bash uv run undercooked-levels list # the campaign, in campaign order uv run undercooked-levels show 01_first_kitchen --grid # resolved level + reachability overlay uv run undercooked-levels validate # the content gate; --json for scripts uv run undercooked-levels new 03_riverboat # scaffold a level from the recipe book uv run undercooked-levels axes # escalation-axis table (phase 11's curve) ``` `undercooked-levels` is a thin shell over the loader and the PLAN §8 rules `create_app` runs at startup, so a green `validate` is a server that boots. It finds content through the settings (`--dir` > `UNDERCOOKED_LEVELS_DIR` > `levels`, plus `--recipes` > `UNDERCOOKED_RECIPES_PATH` > `