Skip to content

Settlement Service Volatility and Scarcity Pulse Loop

Overview

Settlement services should not be static menus. This loop treats access, pricing, reliability, and safety as dynamic outputs of local pressure, creating strategic movement between towns and meaningful timing decisions.

Core Pattern

Run five pulses each settlement turn:

  1. economy pulse
  2. authority pulse
  3. street pulse
  4. opportunity pulse
  5. instability pulse

Each pulse must change one visible service condition and one hidden trajectory.

Standard Procedure

  1. Identify current scarce resource and controlling actors.
  2. Resolve authority posture and enforcement friction.
  3. Advance street sentiment (fear, rumor, confidence, panic).
  4. Generate one new offer, contract, or access deal.
  5. Advance one instability vector likely to break into play.
  6. Publish the results as service availability, delays, surcharges, rationing, closures, or black-market openings.

Why It Works at the Table

  • Makes settlement choice and travel timing matter.
  • Converts rumor flow into concrete logistical effects.
  • Couples faction conflict to player-visible consequences.
  • Produces hooks from normal maintenance instead of bespoke plotting.

Service State Rule

Track services by short states:

  • open and stable
  • open but constrained
  • delayed or rationed
  • captured by a faction gatekeeper
  • collapsed or inaccessible

State changes are the primary campaign signal; prices are secondary.

Scarcity Rule

A scarcity pulse should alter at least one of:

  • equipment access
  • transport reliability
  • medical or repair throughput
  • information brokerage quality
  • safe lodging and storage options

If scarcity does not touch services, players cannot act on it.

Rumor-to-Service Rule

For each town turn, convert at least one rumor into a practical service update. This links narrative noise to operational reality.

Examples:

  • militia rumor becomes checkpoint delays
  • plague rumor becomes healer overload and price spikes
  • guild feud rumor becomes tool access denial

Referee Procedure

  1. Keep one index card per settlement with five pulse tracks.
  2. Apply one step of change per pulse, not full overhauls.
  3. Publish visible effects first, underlying causes later.
  4. Rotate which service category gets hardest pressure.
  5. Carry unresolved pulses into next session until addressed.

Design Guidance

  • Volatility should create decisions, not random inconvenience.
  • Alternate pain and opportunity so towns remain playable.
  • Use different pulse signatures per settlement identity.
  • Keep at least one reliable baseline service per town for planning stability.

Practical Comparison Rule

Use this loop when settlement logistics and faction pressure should shape campaign routing. Use static service lists when towns are brief stopovers and macro-economy is out of scope.

See Also