Game Mower dev wiki · Game Mower wiki

A cozy, low-poly lawn-care game for 1 to 4 siblings. Dad cuts you off, you move into grandma's house, and you build a garden company from her garage: mowing, trimming, pools, pressure washing, one client at a time. Unity 6000.2 with URP, FishNet co-op, macOS and Windows.

This wiki is the team's memory: how the game works, how the code is laid out, and how to work on it without breaking things. It's written for whoever picks up the project next, human or Claude session.

Where to start

New to the code? Read Architecture, then the README "Where things live" and "Key systems".
About to touch Unity? Read Tools & MCP first: several sessions can share one editor.
About to play-test? Read Testing. Back up the save before anything else.
Picking up a build step? The MVP plan says what's next. Every feature answers the golden-rule checklist in Co-op: the siblings together (Tech).

What's in here

Section	What it covers
Game	One spec per feature: story and cast, the mower and the grass, jobs and work, money, the day and the weather, co-op, menus and UI.
Dev	Architecture, code map, co-op, content pipeline, how to add things, testing, tools, gotchas.
Plan	The Roadmap (what goes in which version, and how far it is), the idea inbox.

The old plans (DESIGN.md, EARLY_GAME.md) are retired. What no spec holds yet waits in Leftovers from the old plans.

Writing pages

Feature specs follow one format and one set of rules: read Writing specs first. Every idea has a code, its version and status live in the roadmap, and drawings are figures inside the Markdown.
Other pages are free Markdown in docs/. The folder is the sidebar section (docs/game/, docs/dev/, docs/plan/). The first # Title line is the page title.
Update the page in the same commit as the change. A wiki that lags the code is worse than none.
Link pages with relative .md links ([Testing](dev/testing.md)) or [[testing]]; codes like GR1 link themselves.

Run the wiki (first time: npm --prefix tools/wiki install), then open http://localhost:4321:

npm --prefix tools/wiki run dev

Check the docs and the roadmap before committing:

npm --prefix tools/wiki run check

npm --prefix tools/wiki run build writes the static site to docs/site/ (generated, not committed).