anchor

Use when

The design wants players to leave with stories, not scores; you need a director that authors drama over a deep sim.

RimWorld

What it is. A colony sim whose real product is stories. You keep a handful of flawed characters alive on a hostile map, but the game’s genius is the AI storyteller — a director that watches your state and paces raids, disasters, and lulls to build tension and release like a screenwriter, not a random-event table. You don’t win RimWorld; you tell someone about your RimWorld.

Player fantasy. The anecdote you can’t wait to share: the pyromaniac who saved the colony, the winter you ate your own dead. The pull is that every crisis lands on characters you know, and the director times them so the disaster arrives exactly when it’ll hurt — and mean — the most.

Design DNA

Fun here is emergent narrative — story as the output of interacting systems, not authored scenes. Two engines make it work. First, a deep, legible sim of needs and traits (mood, injuries, relationships, resources) so consequences chain into stories. Second, an AI director (system-emergent-systems, system-difficulty-and-dda) that reads your current state and schedules events for dramatic effect — hit you when you’re strong, breathe when you’re reeling — turning a difficulty curve into a plot. The characters are the stakes; the director is the author; the sim is the ink.

Load-bearing structures

StructureWhy it works
AI storyteller / directorPaces events against live state (wealth, health, morale) for tension→release, not flat randomness. The heart. → system-difficulty-and-dda.
Characters with traits & relationshipsNamed pawns with quirks and bonds make every consequence personal — the stakes that turn events into stories. → system-emergent-systems.
Deep need/mood simHunger, sleep, mood, breaks; needs interact and cascade (a bad meal → a tantrum → a fire). Consequence chains = plot.
Interacting subsystemsMedicine, temperature, food, defence, social — each affects the others; second-order events emerge nobody scripted. → pattern-emergence.
No win stateOpen-ended survival; the “goal” is the story you generate, which removes the “solved, done” cliff. → system-session-structure.
Legible cause-and-effectYou can always trace why it went wrong — the story is coherent, so it’s tellable. → pattern-readability.

What to steal

What’s just theme (drop it)

Composes into

Twist seams

See also

This module rendersthe repo's markdowndirectly — edit it there, it changes here.