Skip to content

Downtime Consequences and Complication Procedures

Overview

Downtime consequences turn the gap between expeditions into active play pressure. Instead of treating town time as bookkeeping, the procedure uses spending, indulgence, or social overreach to generate new obligations, enemies, rumors, and opportunities.

The key value is persistence: a downtime event should not vanish after a single joke scene. It should alter the campaign state.

Core Pattern

The procedure works when it answers four questions in order:

  1. What did the character do or spend?
  2. Did that push them past a clear risk threshold?
  3. What consequence now exists in the world?
  4. What must the table remember next session?

Good downtime complications create campaign continuity, not just comic color.

Common Consequence Families

Family Typical Result What it adds to play
Contact Friend, fixer, patron, lover, rival New social leverage or obligation
Debt Money owed, favor owed, public oath Ongoing pressure and deadlines
Injury Hangover, wound, humiliation, curse Temporary penalties or altered approach
Scandal Broken landmark, public insult, gatecrash, feud Reputation movement and faction response
Discovery Rumor, map, hidden location, political secret New lead or mission seed
Property shift Item lost, windfall gained, stash found, relic moved Resource volatility and follow-up scenes

Threshold Models

Different games can trigger downtime complications in different ways.

Spending threshold

The character spends enough to justify risk. Higher spending increases XP, status, or visibility, but also makes a consequence roll more likely.

Debt threshold

If the character overspends or borrows, a consequence happens automatically. Debt is the cleanest trigger because it guarantees persistence.

Exposure threshold

A party that takes repeated public actions, flaunts treasure, or mixes with volatile factions triggers consequences even without formal spending rules.

Referee Procedure

  1. Establish the downtime action clearly: carousing, gambling, ritual excess, political networking, or reckless celebration.
  2. Set the risk threshold: spending roll, debt line, visibility check, or faction heat.
  3. Roll or choose one consequence family.
  4. Attach one concrete world element: NPC, place, item, rumor, or deadline.
  5. Record it in campaign state before the next expedition begins.

Recording Rule

Every downtime consequence should leave at least one durable note in one of these places:

  • contact list
  • debt ledger
  • faction clock
  • rumor sheet
  • location status

If it leaves no durable note, it was color, not consequence.

Escalation Logic

Downtime procedures are strongest when ignored consequences worsen.

  • A debt becomes collection pressure.
  • A contact becomes an obligation.
  • A scandal becomes faction hostility.
  • A discovery becomes a race with rivals.

This lets one table roll feed several future sessions.

Design Guidance

  • Favor mixed outcomes over pure punishment. A consequence that gives both trouble and opportunity is better than simple loss.
  • Let consequence type reflect settlement tone. Frontier towns produce brawls and debt; capitals produce scandal and patronage; weird cities produce curses and impossible contacts.
  • Use downtime to change the social map. If nothing about the town changes, the procedure is underperforming.

Practical Comparison Rule

Use downtime consequence procedures when you want town play to generate hooks, contacts, and pressure without prepping a separate town adventure. Use them especially after profitable expeditions, because success should destabilize the campaign world.

See Also