TTRPG Living World: What the Colony Does When You’re Not Playing

Most TTRPGs treat the end of a session like a save point. You dealt with the bad guys. Everyone gets XP. “You rest. We pick up next week.” The world holds its breath until the players come back.

Sol Fracta doesn’t do that. We drew inspiration from the faction clocks in Blades in the Dark

Building a TTRPG living world means accepting that the fiction doesn’t stop when the players log off.

The colony doesn’t wait for the players. It breathes, bleeds, and makes decisions on its own. And the system that makes that feel real isn’t a random event table — it’s a structured five-step procedure that turns the end of every cycle into the beginning of the next one.

Five steps. Twenty-five minutes. One loaded gun pointed at next week’s table.

---

The Problem I Was Actually Solving

I spent a lot of time building Sol Fracta’s resource system: dice that represent scarcity, consumption modifiers, faction influence as a zero-sum game. All of it mechanically interesting. None of it automatically creating the thing I actually wanted — the sense that time passing means something. That we feel entropy.

The first few test cycles exposed it fast. Players would finish a mission, we’d do some bookkeeping, and then the session would just… stop. The world felt like a museum. Static. Waiting for the PCs to breathe life into it again.

The fix wasn’t more mechanics. It was a sequence. A structure.

The insight was simple: resolution and consequence have to be causally connected and happen in real-time, at the table, in front of the players. Not as narration. As procedure. Steps that visibly flow into each other, so players watch the dominos fall before they leave or right before starting it.

---

The Five Steps

Step 1 — Resolution & Rewards (5 min)

Start with what just happened. PCs get their rewards. Then comes the decision layer: where do the recovered resources go? Who controls that building now? Which factions were visibly impacted by what the players did?

This isn’t just narration. It produces concrete mechanical outputs through negociation — changes to Control, changes to Influence, changes to resource dice. Write them down. They are the inputs for everything that follows.

The step matters because player agency has to register mechanically before the world responds. If exposing a conspiracy costs Horizon and MercoPrime influence, that loss has to be logged here, now, before Step 2 runs. Causality first.

Step 2 — Resource Rolls (3 min)

The colony lived while you were out there. Roll the dice.

Each resource rolls against its threshold (die max minus Consumption Modifier). Beat the threshold, you’re in shortage — dice downgrade, and something bad happens. Stay under, the colony holds.

The key: Step 1 modifies these rolls before they happen. If PCs brought back +1 ND on Vitals, apply it now. If they torched a farm in the process, that MC penalty hits now. Players watch their decisions echo forward into the colony’s health. That’s not bookkeeping. That’s consequence.

Step 3 — Faction Reactions (3–5 min)

Pick 1–2 factions. Give them a Move. But here’s the constraint that makes this work: factions don’t react arbitrarily. They react mechanically to the state of the world after Steps 1 and 2.

Vitals just downgraded? Ordo Crucis opens their reserves — not out of charity, but because they need to recover influence, and hungry colonists are a political opportunity. MercoPrime sees the same weakness and moves on the farms, coercively, because they can. Both decisions are logical reactions to a resource state, not GM fiat.

This is the step that transforms factions from characters to systems. They have interests. They read the board. They act.

Step 4 — The Narrative Event (10 min)

The GM takes everything from Steps 1–3 and weaves it into one event. Not a summary. A hook.

Four components: Trigger (what caused it), Protagonists (who’s involved), Stakes (what’s on the line), Hook (what decision do the players face next session).

The event doesn’t come from nowhere. It falls from the dominos. Which means it always feels inevitable in retrospect, and surprising in the moment. That’s the design goal.

Step 5 — Preparing the Next Cycle (5 min)

Three questions, decided collectively: Where does the recovered EV get invested? Which faction do we need to negotiate with? What urgency can’t wait?

This step exists because downtime needs direction. Players who leave the table with a clear intention play the next session faster, sharper, with less “what do we do?” paralysis.

---

Cycle 30: The Full Run

Here’s what all five steps look like in practice.

Step 1: The PCs expose a Horizon-MercoPrime conspiracy. Both factions lose 1 Influence. Horizon drops to 2 (minority), MercoPrime drops to 3 (influential but wounded). The PCs decide the exposed conspirators go to forced labor — a pragmatic choice that keeps production running but creates visible resentment.

Outputs: Horizon −1 Inf, MercoPrime −1 Inf, labor pool +2, political tension elevated.

Step 2: Resource rolls. Vitals are at D10, MC −3, threshold 7. Roll: 8. Shortage. RV downgrade D8→D6. Food reserve are smaller. Energetics hold. Industrials hold. One domino falls.

Output: Vitals are now fragile. The colony is hungry.

Step 3: Two factions move.

Ordo Crucis reads the food shortage and opens their reserves — free soup distribution in the habitat zones. Cost: some Industrials stock. Gain: +1 Control in residential sectors, goodwill with unaffiliated colonists. They’re buying influence with bread.

MercoPrime, wounded politically and calculating, sees the Farms (currently Ordo-controlled) as their path back to relevance. They move coercively. The farms change hands. Ordo gains colonists. MercoPrime gains infrastructure. The balance shifts in a way that serves both — and threatens everyone else.

Outputs: Ordo +1 MC Habitability Control, MercoPrime gains Farm control, Ordo loses Farm control.

Step 4: The Independent factions — the unaffiliated colonists, the people with no corporate banner — watch MercoPrime take the farms and connect the dots. Ordo is feeding them, but with MercoPrime controlling production, that generosity has a shelf life. They start organizing. A march toward the granaries.

The hook: The Siege of the Granaries. Morning. Three hundred colonists moving toward the food stores. MercoPrime security in position. Ordo standing between them with no legal authority.

Three choices for the players:

1. Stand with the Independents — escalate the confrontation, risk violence, rebuild political capital outside the corporate structure.
2. Negotiate between Ordo and MercoPrime — preserve order, accept a compromise that probably disadvantages the colonists.
3. Disappear into the crowd — gather intelligence, stay mobile, let this play out and respond to whatever comes next.

No right answer. All three have downstream consequences that will matter in Cycle 31.

Step 5: The Mine project needs 4 EV more. Ordo wants a conversation about the forced labor decision. The granary situation is urgent and visible. Choose your morning.

---

The Colonial Register Gets One Entry

One design note worth calling out: the Colonial Register — the in-fiction chronicle of the colony — doesn’t log the cascade. It logs the result.

After Cycle 30, one entry, chosen for what changed most: “Cycle 30. The Granaries stand but the line is drawn. MercoPrime holds the farms. Ordo holds the people. The Independents held the street.”

The cascade is GM information. The Register is history. They’re different documents for different purposes.

---

The Principle in One Sentence

The end of a cycle isn’t a pause. It’s a trampoline. The resolution of the past becomes the trigger for the future.

That’s it. That’s the whole system. Five steps that take twenty-five minutes and make every session feel like it happened in a world that was already moving.

The world doesn’t wait for the PCs. It moves. They wake up inside a colony that already made decisions without them. And their job, every cycle, is to figure out how to live inside the consequences.

---

When you run downtime in your games, do you run it as narration (“while you were resting…”) or do you make players present for the mechanical consequences? What made you choose that approach, and has it ever backfired?

How do you run a TTRPG living world at your table — what keeps it moving between sessions?