Guide

Colony sim game design explained

Your cook collapses from heatstroke because the kitchen has no cooler. The doctor rushes over — but she is also your only farmer, and the rice crop is two days from rotting. While you reprioritize jobs, a raid alarm sounds from the north wall you never finished. That cascade is not a bug; it is the colony simulation doing its job. Games like RimWorld, Dwarf Fortress, and Oxygen Not Included sell the fantasy of building a settlement from nothing, but the design contract is sharper: autonomous settlers, scarce labor, and systems that collide so every base tells a story the designer never scripted. This guide covers colony-sim subgenres, the expand-assign-respond loop, colonist needs and mood, job prioritization, room quality and layout, threat clocks, research pacing, a Harbor Haven frontier worked example, a subgenre decision table, common pitfalls, and a production checklist. For broader systems framing, see simulation game design; for hunger, temperature, and resource scarcity, see survival mechanics.

What colony sims are — and how they differ from city builders

A colony simulation game puts the player in charge of a small group of settlers who perform tasks autonomously according to priorities the player sets. You design the base, assign work, and respond to crises — you rarely micromanage every swing of a pickaxe. The drama comes from emergent interaction between needs, jobs, environment, and threats.

This is distinct from a city builder, which models thousands of abstract citizens at a distance with zoning and budgets. City builders optimize throughput; colony sims optimize individuals with names, traits, and breakdowns. It is also distinct from a farming sim, where the player avatar performs most labor directly. In colony sims, labor is a scheduling and priority problem, not a stamina bar on one hero.

Major subgenres

Frontier survival colonies — rimworlds, crash sites, harsh biomes with raids and winters (RimWorld, Frostpunk's survival layer).
Underground / facility sims — enclosed environments with atmosphere, plumbing, and power as first-class resources (Oxygen Not Included, Factorio's early base phase).
Historical settlement sims — feudal hamlets, pioneer towns, or space stations with lighter combat (Going Medieval, Surviving Mars).
Autonomous-dwarf classics — deep simulation with minimal direct control and maximal emergent narrative (Dwarf Fortress).
Cozy colony hybrids — low-threat base decorating with light needs systems for a gentler audience.

The core loop: expand, assign, respond, survive

Most colony sims cycle through four phases that repeat at increasing scale:

Expand — claim space, mine resources, build shelter and production chains.
Assign — set job priorities, zones, and schedules so colonists convert raw materials into food, medicine, and defenses.
Respond — fires, disease, mental breaks, equipment failures, and raids force reactive triage.
Survive — weather seasons, sieges, or win conditions before the next expansion wave unlocks harder problems.

The loop works when expansion creates new vulnerabilities. A bigger farm feeds more mouths but attracts raiders; a deeper mine yields steel but risks cave-ins. If growth only adds power without new failure modes, the mid-game becomes a solved idle state. Tie every upgrade to a new dependency: solar panels need batteries; batteries need rare minerals; rare minerals need a distant outpost.

Time scales

Colony sims usually run on accelerated simulation time with pause-and-plan. Micro time covers individual tasks (cook meal: 400 ticks). Meso time covers days and seasons. Macro time covers colony years and legacy goals. Let players pause to issue orders, then watch consequences unfold — the tension between planning and real-time pressure is the genre's signature.

Colonist needs, mood, and social dynamics

Settlers are not interchangeable workers; they are need machines with opinions. Classic need bars include food, rest, recreation, comfort, and safety. When needs drop, mood falls; when mood falls, mental breaks, fights, and work refusal follow. This converts spreadsheet logistics into character drama.

Designing needs that matter

Visible thresholds — players should see "hungry" before "starving," with escalating penalties, not a sudden death at zero.
Quality tiers — fine meal vs nutrient paste, private bedroom vs barracks. Quality differences reward investment without hard gates.
Trait modifiers — pyromaniacs near fire, ascetics in bare rooms. Traits create asymmetric solutions across playthroughs.
Social relationships — friendships, rivalries, and romance change mood independently of physical needs. A well-fed colonist still breaks if their spouse dies.

Avoid need sprawl: more than six tracked needs dilutes comprehension. Group related comforts (beauty, space, temperature) into a single room quality score where possible, as RimWorld does with bedroom impressiveness.

Job prioritization and labor scarcity

Labor is the colony sim's true currency. Every colonist has limited hours; every task competes. The player's primary interface is usually a priority matrix (numbered 1–4 per job type) or work-zone assignment, not direct unit commands.

Job categories that every colony needs

Category	Examples	Failure mode if neglected
Survival	Cook, grow, hunt	Starvation cascade
Infrastructure	Build, repair, haul	Base decay, stockpile jams
Health	Doctor, tend, clean	Infection outbreaks
Defense	Soldier, turret crew, hunter	Raid wipes
Production	Smith, tailor, chemist	Gear stagnation
Research	Scientist at bench	Tech plateau

Hauling is the silent killer. If haulers are deprioritized, workshops starve for inputs and dining rooms fill with rotten meals. Either automate hauling late-game (conveyor belts, drones) or give it a dedicated low-skill role new colonists can fill immediately.

Skill progression adds depth: a level-15 miner outproduces three novices, making veteran preservation a strategic choice. Pair skills with passion markers (double XP in loved jobs) so colonists feel suited to roles without rigid classes.

Base layout, rooms, and production chains

Colony bases are spatial puzzles. Distance costs time — a kitchen far from the freezer wastes hauler hours. Pathfinding bottlenecks (single doorways, narrow mineshafts) create fun failures until players learn to widen corridors and decentralize storage.

Room design principles

Functional adjacency — kitchen next to freezer and dining; hospital near pharmacy; workshop near raw stockpile.
Room roles and bonuses — workshops in clean, dedicated rooms gain speed bonuses; bedrooms need doors for privacy.
Zoning — growing zones, mining designations, and forbidden areas let players paint intent without placing every tile.
Verticality — multi-floor bases save surface area but complicate pathfinding; communicate floor transitions clearly.

Production chains should be legible: iron ore to steel to components to turret. Hide complexity behind machines, not menus. When players understand the chain, they can diagnose bottlenecks ("we are steel-limited, not power-limited"). For sink and source balance across chains, see game economy design.

Threat clocks, seasons, and difficulty curves

Colony sims need external pressure or bases become self-sufficient sculptures. Common threat clocks:

Raids and sieges — scale with wealth, population, or narrative storyteller intensity.
Seasons — winter kills crops; summer drains water; toxic fall spreads disease.
Environmental hazards — solar flares, earthquakes, oxygen depletion, plague.
Internal decay — equipment breakdown, food spoilage, mental breaks during long peace.

The best difficulty systems telegraph threats. A raid warning gives 24 hours to reposition turrets; a cold snap forecast lets players harvest early. Surprise total wipes feel unfair; recoverable setbacks feel like stories. Scale raid size to colony wealth so success breeds harder challenges — the "rich get raided" feedback loop prevents runaway snowballing.

Research trees and progression pacing

Technology unlocks convert survival into specialization. Early research solves immediate crises (electricity, medicine); mid-game unlocks automation; late-game unlocks win conditions or luxury. Research usually costs scientist labor time, creating opportunity cost: every hour at the bench is an hour not spent building defenses.

Branch trees beat linear lists. Let players choose between geothermal power vs solar, melee vs ranged doctrines, or trade vs self-sufficiency. Mutually exclusive branches encourage replay without requiring new biomes. Gate late tech behind rare materials or quest events so progression spans in-game years, not hours.

Worked example: Harbor Haven (frontier crash site)

Harbor Haven is a mid-scope colony sim slice: three crash survivors, temperate forest biome, quarterly raids, mild winters. Design goals: teach priorities in 15 minutes, create a first crisis by day 8, and reward base planning by day 30.

Starting state

Colonists: engineer (build + research passion), medic (doctor + grow), scout (hunt + fight).
Resources: 40 packaged meals, 200 wood, 80 steel scrap, one solar panel (damaged, 50% output).
Immediate threats: no roof (rain mood penalty), no freezer (meals spoil in 4 days), raid forecast day 8.

Days 1–7: survival triage

Players must assign the engineer to walls and sleeping spots, the medic to a growing zone and sickbay, the scout to hunt and set traps. Hauling competes with building — if the engineer is set to "build 1, haul 4," stockpiles jam and construction stalls. The tutorial nudge: "Meals spoiling in 3 days — build a powered cooler before researching turrets."

Day 8 raid: first crisis

Three raiders attack from the north. Sandbags (unlocked day 1) and the scout's bolt rifle should hold if players walled a choke point. Failure state: one downed colonist, recoverable with medic tending. Success teaches defense before expansion.

Days 9–30: specialization fork

Research branch A unlocks hydroponics (food independence); branch B unlocks turret automation (defense independence). Choosing both delays either by two weeks — a real opportunity cost. Winter on day 25 stops outdoor crops, testing whether players invested in greenhouse or stockpile. By day 30, a stable colony has 6–8 colonists (one recruit event mid-month), private bedrooms, and a resolved bottleneck (food OR defense, not both neglected).

Subgenre decision table

Player fantasy	Subgenre	Core tension	Avoid if
Stories from chaos	Frontier survival (RimWorld-like)	Raids, mood breaks, triage	Audience wants zero combat stress
Engineering puzzles	Facility / atmosphere sim	Gas, power, plumbing balance	Team lacks simulation depth budget
Watch dwarves live	Deep autonomous sim	Emergent narrative, minimal UI	You need accessible onboarding
Decorate a settlement	Cozy colony hybrid	Light needs, aesthetic goals	You want hardcore failure states
Historical authenticity	Settlement period sim	Seasonal agriculture, trade	Scope cannot support era research

Common pitfalls

Hauler starvation — every workshop backs up because hauling is deprioritized; dedicate haul role or automate early.
Need bar overload — tracking 12 separate meters overwhelms new players; consolidate into room quality and mood summaries.
Unfair surprise wipes — instant-kill events without warning end campaigns without teaching; telegraph and scale threats.
Single optimal layout — if one base template solves all biomes, replay dies; biome-specific constraints (heat, toxins, elevation) force adaptation.
Colonist fungibility — identical stats make deaths painless; traits, relationships, and skills make loss hurt.
Peace plateau — after raids stop, nothing pressures growth; wealth scaling, maintenance decay, or win-clock keeps tension.
Micro-management creep — if players must click every meal, you have built a farming sim by accident; trust priorities and zones.

Practical checklist

Playtest days 1–3 without guides — can a new player secure food and shelter?
Verify hauling does not block critical chains when all colonists are busy.
Document mood thresholds and mental-break outcomes in an in-game codex.
Simulate raid scaling at population 3, 8, and 15 — are wipes recoverable?
Map every production chain on one page; no orphan resources.
Winter (or equivalent downtime) forces prep by day 20 in a 30-day arc.
Research branches offer meaningfully different playstyles, not +5% stats.
Pathfinding stress test: 20 colonists crossing one doorway during a raid.
Save file records colonist stories (events log) for player sharing.
Accessibility: pause-anytime, color-blind need indicators, scalable UI text.

Key takeaways

Colony sims generate stories by colliding autonomous settlers, scarce labor, and environmental pressure — not scripted cutscenes.
Job prioritization is the primary player skill; hauling and doctor roles are common bottlenecks.
Room quality and needs convert logistics into character drama when traits and relationships amplify mood.
Threat clocks must scale with success and telegraph danger so failures teach rather than frustrate.
Expansion should introduce new dependencies, not just bigger numbers — every upgrade needs a new thing that can go wrong.