A city builder gives you an empty map, a modest budget and a set of levers that all feed into one another. Nothing you place stays local: a decision about housing becomes a decision about jobs, then about traffic, then about the budget, and it arrives back at you as a complaint. There is rarely a win screen, and the genre is better for it.
Place, connect, balance, respond. Every solution is a new load on some other system, which is why a city builder never resolves and never quite fails either. Bankruptcy and gridlock are soft, recoverable failures; scenario modes bolt on hard goals, but the open-ended default is the honest one.
SimCity's central trick still defines the form: you do not place every building, you place intent. Homes here, industry there, and the simulation decides what actually gets built, when, and whether anyone wants it. That single decision is why the genre feels closer to gardening than to construction, and why watching is as much a verb here as building.
Not every branch took that route. The Impressions city builders — Caesar III in 1998 and its Egyptian and Greek successors — ran services on walkers: a market trader or a doctor leaves their building, walks the streets, and serves only the houses they happen to pass. Coverage is not a radius, it is a route, so layout becomes logistics and a badly shaped block starves next to a full granary.
The survival branch shrank the city to a village and made winter the antagonist. Banished (2014) is its clearest statement — no villain, no enemy, only how many people the cold leaves you. Cities: Skylines followed in 2015 and took the mainstream mantle by making traffic the thing players argue about. Frostpunk arrived in 2018 and fused the village with society management: one generator, a book of laws, and a city that keeps score of what you were willing to do.
A city builder is a diagnosis game. Something is always slightly wrong and the pleasure is working out why, so the good ones spend enormous effort on telling you: overlays for land value and pollution, heat maps for service coverage, and best of all a single named citizen you can follow from their door to their job and back.
Trace a complaint to its cause and the simulation is teaching you; fail to, and it may as well be a random number generator. There is a real difference between a game that simulates commuters and one that rolls dice and paints cars onto the road, and an hour is long enough to feel it. An honest simulation produces problems that are your fault, and that ownership is what makes fixing them satisfying.
The same instinct points three ways. Zoom in until the population is individuals with names and moods and you have a colony sim. Zoom out until the city is one counter on a continental map and you are in 4X and grand strategy. Keep the layout but give it something to survive and the exercise becomes tower defense.
The pressure in a city builder is the budget, and the endgame problem is that you eventually beat it. The scramble — the under-funded, half-wired early city where every choice costs something — is where the design lives. Once the machine runs at a comfortable surplus, most city builders have nothing left to want from you, and the finished city is a screensaver you feel fond of.
Games answer this differently. Disasters restore the pressure by force. Scenarios replace the sandbox with a brief. Frostpunk simply ends, which is the cleanest answer anyone has found. If you are building one, decide early what the second act asks for, because a growth curve on its own will not carry it.
A brief for this genre lives or dies on its first line, because that line decides what the player actually places:
Type: City builder (you zone intent; a colony sim gives you named people)
Core loop: Draw roads, zone land, fund services, read the complaints, redraw
Perspective: Free or isometric camera above the map, zoomable down to a street
Win / lose: Open-ended; bankruptcy and gridlock are the soft failures, scenarios add hard ones
Session: Hours, in a pause-fix-unpause rhythm
Progression: The city is the progression; policy and tech unlock as it scales
Fill that in and the cascade decides most of the rest for you. Leave it vague and an AI will hand you a map where buildings drop into place fully staffed — which looks like a city builder in a screenshot, and answers none of the six questions above.