Start with a road.
Make room for a city.

Your first neighbourhood.

1. Start a new city and lay a short road.
2. Add residential zoning, then supply power and water.
3. Run the simulation and watch population, funds and monthly income—not just the buildings.
4. Use Settings → Save, then check Continue when returning.

Progress stays in this browser on this site. Clearing site data, storage limits or changing browsers can lose local saves. Keep an exported copy somewhere you control.

A city export is not the game’s source.

A SMALL RECIPE. A DIFFERENT START.

Same riverbank.
A different budget.

Open the separate v2 Scenario Workshop to start a fresh 40×40 city with $25,000, $50,000 or $100,000. Pick an optional self-set goal, or simply build. A tiny recipe lets another person reproduce that initial map and budget—not your progress or the game’s source.

Separate saves: v2 saves are isolated from v1 and are not automatically migrated. Use one game tab at a time. Keep an exported city backup outside browser storage.

1. In v2, open Settings → Scenario Workshop and choose your budget and optional goal.
2. Select Review scenario, inspect the fixed base and budget, then explicitly Start reviewed scenario as a separate city. The current v2 city is backed up before switching; storage can still fail or be cleared.
3. Use Download reviewed recipe or Download this city’s recipe to keep the small JSON recipe.
4. Import a recipe file or paste its JSON, review it and explicitly start. Opening or reviewing a recipe alone does not start a city.

Goals are self-set, not enforced. The recipe fixes the initial layout and budget; later simulation is nondeterministic. Export/import stays local. You can separately send a recipe for private curator review—not cross-game mixing or automatic publishing.

Return a v2 recipe for private review →

Two-part v2 source: download the unchanged v1 base archive and the small v2 changes kit. The kit alone is not the complete game. Its reviewed offline Python assembler verifies both the base and every output file, then creates a complete, self-contained v2 city source directory. Follow the kit README; no game code is executed and nothing is downloaded during assembly.

The source travels with the city.

Exact source/runtime hashes & release evidence · Credits & licence notices

Original source: amilich/isometric-city at b774dd791310. Game Commons adaptation: local English, offline solo scope, bounded imports and hosting integration. Analytics, remote fonts and the protected themed pack are excluded.

Code and artwork are not the same claim.

MIT; retain original and dependency notices.

Pinned upstream WebP art under the repository-level MIT declaration. AI-generation workflow documented upstream; no independent per-image provenance guarantee. Protected themed pack excluded. Root-level MIT permission is not a trademark clearance or a guarantee of authorship for every image.

What was actually tested?

Bounded desktop check on 31 October 2026 of the prefixed static release: two full 70×70 imports, each followed by explicit Save → reload → Continue. Simulation advanced from 66 to 88 residents and monthly income from −174 to −154; the saved 88-resident city restored. The second import restored the baseline of 66 residents, $95,456 and monthly −174. Malformed input was rejected without changing the city. No Chromium Error 9 was observed during this bounded run; no cause or general stability claim is established. Mobile and long-session acceptance remain unverified.

Source tests and a successful build are not independent-player acceptance or a promise that every city, browser and long session will work. Read the exact release record before relying on a particular result.

Bring the next version back.

Share public links to your complete source and playable build, the pinned parents, what changed, the reuse terms and what you actually tested. Review is private and manual; submitting is not publication or approval.