Back to Home
Banished
game
•7/23/2026

Banished

byShining Rock Software LLC
Steam
8.3
The Verdict
"Banished is a landmark, and landmarks are allowed to show their age. Its refusal to give you money, tech trees, or victory conditions looked like austerity in 2014; in hindsight it was clarity. Every survival builder since has borrowed its central insight — that people, not resources, are the real economy — and few have executed the generational math this cleanly. The missing endgame is a real flaw, the UI is thinner than the simulation deserves, and the game's finished status means neither will ever change. But as a machine for generating hard-won, self-authored stories of towns that almost didn't make it, Banished still has no equal at its price. Buy it, install Colonial Charter when the base game goes quiet, and lose a winter to it."

Gallery

Screenshot 1
View

Key Features

Population as the only resource: No gold, no research points. Citizens are your economy, your military-grade logistics, and your failure state all at once. An aging population is a slow-motion catastrophe you can see coming five years out — and often can't stop.
Twenty interlocking occupations: Farmers, foresters, hunters, blacksmiths, tailors, teachers, and more, all drawing from one shared labor pool. Reassigning workers is your primary verb, and the tension between "food now" and "tools later" never fully resolves.
Barter-only trade: Visiting merchants are your sole pipeline for livestock, seeds, and goods you can't produce. Stockpiling firewood or ale as trade currency becomes a strategy in itself.
Procedural maps with tunable scarcity: Terrain, climate severity, and starting conditions are adjustable, letting you dial the game from "pastoral" to "actuarial nightmare."
Deep mod support: Community expansions like Colonial Charter effectively double or triple the content, adding production chains the base game never attempted.

The Good

Population-as-resource design still feels radical and creates genuine generational strategy
Systems interlock with rare elegance; failures are traceable and earned
Workshop mods (Colonial Charter, MegaMod) add years of content
Runs beautifully on modest hardware; frequently discounted

The Bad

No endgame — challenge evaporates once your town stabilizes
Sparse UI makes diagnosing problems harder than it should be
Windows-only, development long finished, no official expansions ever
Disasters feel random rather than escalating

In-Depth Review

Bottom Line: A decade on, Banished remains the purest expression of the survival city-builder — a cold, elegant machine where every citizen is a resource and every winter is a referendum on your planning. It runs dry once you've mastered it, but getting there is unforgettable.

The Loop

Banished's core loop is deceptively quiet. You place a building, assign workers, and watch tiny figures haul logs through the snow. Nothing explodes. Nothing attacks you. The drama is entirely demographic, and that's the game's masterstroke.

Here's how it actually kills you. Early on, you build houses to grow your population. New houses mean new families, which means a baby boom. Babies don't work — they consume food and firewood for a decade before contributing anything. So you over-expand food production to compensate, pulling workers from tool production. Tools degrade. Untooled workers produce at a fraction of capacity. Yields collapse right as the boom generation hits working age with nothing to do — and then that entire cohort ages out simultaneously, twenty years later, gutting your workforce in the span of two harvests. Banished doesn't punish mistakes immediately. It punishes them a generation later, when the cause is barely a memory. No other city builder of its era had the nerve to do this.

The occupation system is where minute-to-minute play lives. Every worker pulled from the fields is a worker added to the quarry, and the interface makes this zero-sum arithmetic constantly visible. There's real texture in the second-order effects, too: foresters and hunters compete for the same woodland, orchards take years to mature, and a schoolhouse — which makes citizens dramatically more productive — also delays their entry into the workforce. Education is a long bond with a brutal coupon schedule, and deciding when your fragile settlement can afford it is one of the best decisions in the genre.

Where It Runs Out

The honest critique, and the one the Steam reviews consistently land on: Banished has no third act. Once your town crests roughly 200-300 citizens with redundant food sources and a healthy trade surplus, the systems that once threatened you become bookkeeping. Disasters — fires, tornadoes, infestations — read as random taxation rather than escalating challenge. There are no goals, no scenarios, no late-game pressure. The game simply stops pushing back.

You can read this as purity — Hodorowicz built a simulation, not a campaign — but it's also a real ceiling on the experience. Frostpunk later demonstrated that survival builders can have narrative arcs and climactic stress tests without sacrificing systemic depth. Banished, by comparison, is all rising action. The modding scene patches this admirably (Colonial Charter alone adds enough production complexity to restart the learning curve), but leaning on mods to supply an endgame is a workaround, not a design.

Interface

The UI is functional and largely honest — production tallies, inventory limits, and per-building worker counts are all one click away. But it's austere to a fault. Diagnosing why food dipped requires cross-referencing three panels and your own memory; the game logs almost nothing. A town graph or event history would have transformed the mid-game. Priority controls for laborers are similarly blunt — you can nudge, but never truly queue. For a game about cause and effect across decades, the tools for investigating cause and effect are strangely thin.

Editorial Disclaimer

The reviews and scores on this site are based on our editorial team's independent analysis and personal opinions. While we strive for objectivity, gaming experiences can be subjective. We are not compensated by developers for these scores.