Skip to content

Faction Action Turn and World Response

Overview

Faction action turns formalize what happens between sessions. Instead of static lore, each active faction takes one concrete action, absorbs one risk or cost, and leaves one visible sign in the world.

World response then turns those moves into playable pressure for the next session.

Core Pattern

Each cycle has two linked phases:

  1. faction action resolution
  2. world response publication

The first changes hidden state. The second makes those changes visible through rumors, prices, patrols, security posture, or mission offers.

Standard Procedure

  1. Select active factions for this cycle.
  2. For each faction, define objective, posture, and action.
  3. Resolve action outcome and cost.
  4. Advance one relevant pressure clock.
  5. Record one visible sign and one hidden implication.
  6. Publish at least one change into rumor, location, or service availability.

Run once per session cycle or once per major in-world time unit.

Why It Works at the Table

  • Keeps campaign worlds moving when players are elsewhere.
  • Makes faction conflict produce concrete play hooks.
  • Prevents prep paralysis by bounding world updates to one action per faction.
  • Aligns macro politics with table-facing evidence.

Faction Action Frame

For each faction, fill five fields:

  • objective this cycle
  • posture: cooperate, pressure, isolate, escalate
  • chosen action
  • cost or backlash risk
  • public signal

If two factions choose incompatible actions, generate a conflict incident and escalate heat.

World Response Rule

Every resolved faction action should change at least one of:

  • rumor stream
  • district baseline danger
  • settlement access or scarcity
  • patrol patterns
  • mission availability
  • contact graph tension

If none of these changed, the action was not translated into play.

Clock Integration

Use domain clocks as consequence memory:

  • governance
  • security
  • infrastructure
  • belief

Advance based on faction actions, not random drift. At threshold events, trigger visible crisis states.

Referee Procedure

  1. Keep active faction count intentionally small.
  2. Resolve one action per faction, no exceptions.
  3. Publish consequences before explaining causes.
  4. Seed two to three hooks from resulting instability.
  5. Update NPC/contact edges touched by faction moves.

Design Guidance

  • Choose actions that can fail and carry backlash.
  • Treat rumors as delivery channels for faction state.
  • Keep hidden implications for delayed reveals.
  • Let player intervention alter next cycle objectives directly.

Practical Comparison Rule

Use faction action turns when campaign politics should have persistent momentum and visible consequences. Use ad hoc faction updates when world drift is intentionally loose and low-stakes.

See Also