A city builder browser game is a planning puzzle that runs locally in your browser: you place five disclosed permits on a fixed 5-by-5 grid, audit every orthogonal neighbor, and finish on an exact 1,000-point score. The City Builder Game defines one original board with four reserved corners, a starting budget of 19, three permit types (Residential at cost 3, Commercial at cost 4, Civic service at cost 5), and a fixed five-step route. Every accepted permit pays 100 base points and adds a disclosed cardinal bonus only for occupied orthogonal neighbors; diagonal cells never count. The disclosed sequence — Residential at row 2 column 2, Civic service at row 1 column 2, Commercial at row 2 column 3, Residential at row 1 column 3, and Commercial at row 2 column 1 — produces independent awards of 100, 250, 200, 250, and 200 points and drains the budget from 19 to exactly 0. Because the route, costs, bonuses, and reserved corners are all visible on the page, the result is reproducible without any hidden simulation or random element.
What this city builder browser game actually is
This game uses the word "city" as a theme for a small disclosed rule system, not as a model of real urban planning. The board is an original 5-by-5 grid that does not correspond to a real location, a zoning code, a property price, a population model, or a changing map. There is no account, no upload, no model call, and no network-based opponent; every interaction runs locally in your browser. The entertainment value comes from executing a tight, fully visible five-step sequence and from auditing the asymmetry between Residential, Commercial, and Civic service adjacency bonuses. Real decisions about zoning, infrastructure, finance, accessibility, environment, and community constraints are deliberately outside its scope, and the puzzle is labeled as fictional entertainment rather than guidance.
Grid layout, reserved corners, and the starting budget
The board has 25 cells indexed by zero-based row and column coordinates, so the top-left cell is row 0 column 0 and the bottom-right cell is row 4 column 4. Four corner cells — (0,0), (0,4), (4,0), and (4,4) — are reserved and cannot host a permit. The remaining 21 cells hold the five-step route, and only five of them are ever occupied in the canonical run.
You start with a budget of 19 and three permit types in your ledger. Residential costs 3, Commercial costs 4, and Civic service costs 5. The selected permit type, the target cell, the remaining budget, the occupied count, the current mistakes, and the last award all remain visible on the page throughout the run. Keyboard players can move the lot cursor with the Arrow keys, choose the next type with the 1, 2, or 3 keys, and press Enter or Space to approve. Pointer and touch players can use the visible permit buttons and grid cells instead and then select Approve selected permit.
How to play the city builder browser game to 1,000 points
Follow the disclosed permit ledger in order. Each step names one permit type and one exact cell. Match both, approve, and watch the disclosed award update before the next ledger item appears.
- Open the City Builder Game and read the first ledger item: Residential at row 2 column 2. Select Residential (key 1 or the R button) and move the lot cursor to (2,2) with the Arrow keys, then approve with Enter or Space.
- Read the next ledger item: Civic service at row 1 column 2. Select Civic service (key 3 or the Civic button) and move the cursor to (1,2), then approve. The disclosed award updates to reflect the 100 base plus 150 for the adjacent Residential below.
- Read the next ledger item: Commercial at row 2 column 3. Select Commercial (key 2 or the Commercial button) and move the cursor to (2,3), then approve. The disclosed award reflects 100 base plus 100 for the adjacent Residential to the left at (2,2); the Civic service above at (1,2) does not count because it is diagonal from (2,3).
- Read the next ledger item: Residential at row 1 column 3. Select Residential and move to (1,3), then approve. The disclosed award reflects 100 base plus 100 for the adjacent Civic service to the left at (1,2) plus 50 for the adjacent Commercial below at (2,3).
- Read the next ledger item: Commercial at row 2 column 1. Select Commercial and move to (2,1), then approve. The disclosed award reflects 100 base plus 100 for the adjacent Residential to the right at (2,2). The run closes on an exact 1,000-point score with a budget of 0.
Permit costs, base points, and the three adjacency rules
Every accepted permit pays exactly 100 base points. After that, only the selected type's disclosed bonus counts, and only for occupied orthogonal neighbors — up, down, left, and right. Diagonal cells never add a bonus. The three permit types apply three different rules, which is what creates the asymmetry you audit on every step.
| Permit type | Fixed cost | Base points | Adjacency bonus (orthogonal only) |
|---|---|---|---|
| Residential | 3 | 100 | +100 per adjacent Civic service, +50 per adjacent Commercial |
| Commercial | 4 | 100 | +100 per adjacent Residential |
| Civic service | 5 | 100 | +150 per adjacent Residential |
One concrete audit: when Civic service is placed at (1,2), its only occupied orthogonal neighbor is Residential at (2,2). The award is therefore 100 base + 150 = 250, which matches the disclosed value on the page. That same rule explains why Residential at (1,3) reads 250 as well — 100 base plus 100 for the adjacent Civic at (1,2) plus 50 for the adjacent Commercial at (2,3).
What counts as a mistake, and what the game ignores
The game distinguishes a recoverable planning mismatch from an impossible action. A valid affordable permit placed on the wrong cell or with the wrong type for the current ledger item creates one mismatch. Repeating the exact same step, type, and cell signature is deduplicated and adds no further penalty. A second distinct mismatch — a different wrong type or a different wrong cell on a still-affordable step — closes the permit file and ends the run.
By contrast, several attempts change no buildings, no budget, no score, and no mistake count. Trying a reserved corner, a cell outside the 5-by-5 grid, an already occupied cell, or a permit whose cost exceeds the remaining budget is treated as impossible and ignored. The disclosed losing route starts by attempting Commercial at (2,2), repeats that exact attempt without a second penalty, and then attempts Residential at (0,1) — a reserved corner — which is simply ignored. Completion and deadlock freeze building, selection, and cursor transitions so extra actions cannot alter the audited result.
How the 1,000-point finish is independently audited
Verification does not ask the product reducer for its own expected values. An independent literal grid oracle restates the costs, base points, asymmetric placement-time bonuses, permit route, reserved corners, and starting budget from scratch. It then recomputes each Manhattan-distance-one neighbor award one step at a time, checks the five cumulative board states, exercises the occupied, blocked, outside, unaffordable, repeated-error, and terminal paths, and finally requires the exact 1,000-point total.
Because the route is fixed and the rule system is fully disclosed, the run is reproducible without luck, hidden simulation, or model dependency. Restart restores the exact initial board and budget, so a second attempt behaves identically to the first. The shared Boss Key remains available through the standard game shell, and no step uploads data or contacts a server. This makes the City Builder Game a clean example of a city builder browser game whose scoring can be reasoned about rather than guessed, which is what distinguishes it from the larger open-ended simulations that share the keyword.
If you're weighing options, Clock Practice Game: Master Five Analog Clocks to 1,000 covers this in detail.