Skip to content

Dungeon Revisit and Restocking Pressure Loop

Overview

Revisit play is strongest when dungeons do not remain frozen after first contact. This loop updates explored sites with new occupancy, changed rewards, and altered route safety, making repeated delves meaningful rather than repetitive.

Core Pattern

The loop has five passes:

  1. mark elapsed time since last visit
  2. restock touched and adjacent spaces
  3. regenerate unstable traversal edges
  4. publish visible signs of change
  5. convert new state into choices for the next delve

Standard Procedure

  1. Determine return interval (same day, days, weeks, or longer).
  2. For each previously entered room, roll restocking state (monster, treasure, both, or empty).
  3. In volatile zones or long absences, increase instability by rolling twice and keeping the riskier result.
  4. For partially mapped perimeters, run traversal-triggered generation checks to grow or reroute the site.
  5. Add one visible clue per changed sector (tracks, barricades, smoke, silence, scavenger signs).
  6. Start the next session with updated route and risk information.

Why It Works at the Table

  • Prevents solved dungeons from becoming dead content.
  • Rewards reconnaissance and route memory.
  • Produces emergent factions and claims inside old sites.
  • Makes delay and recovery time a strategic choice.

Restocking Rule

Use bounded room-level outcomes that can be resolved quickly:

  • hostile occupancy
  • opportunistic scavenging
  • newly exposed or moved treasure
  • temporary emptiness with signs of approach

The point is to shift site state, not fully redesign the dungeon every return.

Volatility Rule

Escalate restocking intensity when any of the following is true:

  • long interval since last visit
  • heavy prior disturbance by the party
  • known nearby faction competition
  • active hazard or collapse pressure

Volatility should create altered routes and changed risk assumptions.

Traverse-and-Grow Rule

Unexplored or unstable edges can continue to generate by movement-triggered checks. This keeps old sites expandable without prebuilding complete maps.

Use this only where uncertainty remains; avoid rewriting already stable, high-detail sectors.

Referee Procedure

  1. Keep a short revisit log per site (date, disturbance, unresolved threats).
  2. Restock only affected sectors plus one adjacent ring.
  3. Add one new route problem and one new opportunity each return.
  4. Telegraph changes before punishment through evidence in approach zones.
  5. Preserve continuity by keeping some old landmarks unchanged.

Design Guidance

  • Revisit loops should produce both danger and leverage.
  • Total random overwrite kills player mapping value.
  • Visible signs matter more than hidden state for fair play.
  • Use limited updates often rather than massive rewrites rarely.

Practical Comparison Rule

Use this loop when campaigns revisit megadungeons, ruins, or persistent underworld sites. Use one-and-done stocking when locations are intended for single-session resolution only.

See Also