Skip to content

Stronghold Lifecycle and Upkeep Cadence

Overview

Strongholds are most useful when treated as living campaign systems, not one-time level rewards. This cadence tracks how strongholds are founded, stabilized, stressed, and adapted over time.

Core Pattern

Run the lifecycle in five phases:

  1. establish and claim
  2. staff and secure
  3. maintain and provision
  4. absorb pressure events
  5. expand, repair, or retrench

Each cycle should produce at least one tangible change in capability or vulnerability.

Standard Procedure

  1. Define stronghold type, territory, and immediate strategic purpose.
  2. Assign baseline staffing: retainers, specialists, and command roles.
  3. Set upkeep obligations (coin, supplies, labor, political obligations).
  4. Resolve one pressure event per cycle (raid, shortage, legal claim, internal dispute, infrastructure failure).
  5. Choose one response mode: invest, negotiate, militarize, decentralize, or withdraw.
  6. Update local recruitment quality, service reliability, and faction posture.

Why It Works at the Table

  • Keeps high-level play tied to practical expedition decisions.
  • Converts treasure and alliances into durable but fragile advantages.
  • Produces mission hooks directly from upkeep stress.
  • Preserves campaign momentum between major dungeon arcs.

Upkeep Rule

Upkeep should be modeled as recurring obligations, not a flat tax.

  • material upkeep: repairs, supplies, payroll
  • political upkeep: tribute, legal recognition, obligations
  • social upkeep: loyalty, legitimacy, and settlement confidence

Neglect in any lane creates distinct failure modes.

Pressure Rule

Every cycle, advance one external and one internal pressure:

  • external: rivals, raiders, border disputes, authority intervention
  • internal: morale drift, corruption, maintenance backlog, leadership conflict

Dual pressure keeps stronghold play from becoming passive accounting.

Renewal Rule

After each pressure resolution, apply one trajectory outcome:

  • consolidation (stability up)
  • overextension (risk up)
  • adaptation (function shifts)
  • attrition (capability down)

This tracks whether the stronghold is maturing or decaying.

Referee Procedure

  1. Keep a one-page stronghold ledger with obligations and current pressure tracks.
  2. Resolve one upkeep pulse and one pressure pulse each session cycle.
  3. Convert at least one unresolved pressure into a mission offer.
  4. Let player policy choices alter next-cycle pressure composition.
  5. Surface visible local effects before abstract reports.

Design Guidance

  • Strongholds should create options, not only costs.
  • Avoid all-or-nothing collapse; partial failures produce better play.
  • Tie staffing quality to treatment, pay reliability, and reputation.
  • Keep regional politics close enough to matter operationally.

Practical Comparison Rule

Use this loop when campaigns include name-level holdings, regional influence, or recurring base operations. Use one-time stronghold assumptions when domain management is outside campaign scope.

See Also