City Builder

City Builder is a genre in which the player places infrastructure and zones land, and the game's central labor is keeping several interdependent systems — traffic, power, water, tax revenue, land value, pollution — within tolerance at once. There is usually no scoreboard opponent. The city itself is the adversary, in the sense that it will find the load-bearing mistake in your grid faster than you will.

SimCity set the template with its demand-and-zone model: residential, commercial, and industrial zones each track their own demand curve, and the player's job is to read those curves and correct imbalance before it compounds. Cities: Skylines pushed the simulation further into traffic specifically, modeling individual vehicle pathing rather than an aggregate flow number, which turned "my city is failing" into a legible, diagnosable traffic-engineering problem rather than a vague malaise.

The genre is easy to confuse with Colony Sim, and the distinction is worth holding onto: a colony sim tracks named individuals with needs and moods, while a city builder abstracts its population into statistics — average happiness, not Greg's happiness. That abstraction is a design choice, not a limitation; it's what lets a city builder scale to tens of thousands of residents without the interface collapsing.

The genre's real tension is between simulation depth and legibility. A model detailed enough to be true is often too opaque to be readable — a city can fail for reasons buried three systems deep, and a player who can't trace the cause learns nothing from the failure, the same legibility problem that Soulslike design solves for combat. The best city builders expose enough of their internal graph (overlays, per-building tooltips, historical charts) that a bad decision remains diagnosable years after it was made.