Skip to content

Infrastructure Economy and Maintenance Failure Loop

Overview

Infrastructure is not static backdrop. This loop models utilities, transport, and civic systems as contested economic networks that degrade, fail, and recover through player and faction action.

The goal is to make infrastructure reliability a visible strategic layer.

Core Pattern

Cycle through six stages:

  1. baseline utility state
  2. maintenance load and debt
  3. disruption trigger
  4. failure propagation
  5. market and faction response
  6. repair or adaptation outcome

Each cycle should alter at least one practical service condition.

Standard Procedure

  1. Define critical chains (power, water, transit, data, medicine, food).
  2. Assign each chain a maintenance state (stable, strained, brittle, failing).
  3. Advance one disruption source (sabotage, weather, corruption, overload, neglect).
  4. Resolve which district or node fails first.
  5. Apply economic effects: shortages, price spikes, rationing, black-market growth, protection rackets.
  6. Offer repair or exploitation missions tied to faction posture.
  7. Update chain state after mission outcomes.

Why It Works at the Table

  • Makes cities and waypoints feel materially alive.
  • Connects faction politics to concrete daily consequences.
  • Produces recurring mission hooks from systemic stress.
  • Supports both urban campaigns and post-collapse salvage play.

Maintenance Debt Rule

Unresolved upkeep creates debt that compounds risk:

  • first stage: slower service and minor outages
  • second stage: reliability collapse and access gating
  • third stage: cascading failure into adjacent chains

Debt should accumulate from both neglect and conflict damage.

Failure Propagation Rule

One chain failure should pressure others where dependencies exist:

  • power outage degrades data and medical throughput
  • transit breakdown constrains repair logistics and food delivery
  • water contamination escalates public order and labor unrest

Propagation is what turns incidents into campaign events.

Response Economy Rule

When failures occur, factions and markets react in recognizable patterns:

  • emergency procurement and hoarding
  • coercive access control by gatekeepers
  • opportunistic black-market expansion
  • legitimacy gains or losses for authorities

These reactions should generate mission offers and political repositioning.

Referee Procedure

  1. Track two to three high-impact chains, not every utility.
  2. Advance one maintenance or disruption step per settlement cycle.
  3. Publish one visible civic sign before revealing full causality.
  4. Tie at least one active mission to current chain stress.
  5. Let successful repairs create temporary stability, not permanent immunity.

Design Guidance

  • Reliability should be uneven across districts and factions.
  • Use scarcity changes to force route and alliance decisions.
  • Preserve player agency by offering fix, exploit, or bypass options.
  • Avoid pure doom spirals; include recovery windows and contested solutions.

Practical Comparison Rule

Use this loop when campaign identity depends on urban fragility, weird-tech upkeep, or post-collapse utility politics. Use static infrastructure assumptions when logistics are outside desired play focus.

See Also