We Don’t Play Dungeons Like They Used To

Short summary

• Modern 5e play often treats dungeons as static funnels that end in one big “nova” boss fight. That design encourages extreme caution or skipping exploration.
• Proposed fix: bring back dungeon turns — 10-minute time increments called “stretches” (an OSR mechanic older than D&D) — to make time a tracked resource, increase tension, and restore meaningful exploration and resource management.

History and context

• Dungeon turns (10-minute segments) appear in pre-D&D rules and early D&D drafts.
• The Old School Renaissance (OSR) preserved and extended these time-tracking practices.
• The video creator (Davi of Mystic Arts) draws on modern OSR games and fanzines that keep the idea alive.

What a “stretch” (10-minute dungeon turn) does

• Converts exploration into discrete, repeatable time units so the dungeon “moves” even while players deliberate.
• Lets the DM run wandering monsters, hauntings, random events, timed hazards, and shifting objectives to create gradual tension rather than one-off slugfests.
• Makes actions meaningfully concurrent: while one player performs a long task, others can keep watch, search, scout, or otherwise contribute.

Concrete mechanics and design dials

Wandering-monster / event dials (three knobs)

• Frequency: decide how often to roll (every 10 / 30 / 60 minutes).
• Probability: set encounter chance per roll (examples: ~16%, 33%, 50%).
• Difficulty: choose encounter outcome severity (easy / medium / hard).

Example uses:

• Roll for hauntings every 10 minutes in a haunted house.
• Make a vent crawl take 10 minutes while an elemental wanders the vents.
• Use repeated rolls to create escalating stakes across stretches.

Start / stop tracking:

• Begin when exploration/crawl starts (lighting a torch, entering, or the first 10-minute activity).
• Stop when the crawl ends or the party exits the area.

When to use stretches:

• Use whenever a dungeon has more than a couple of combats (multi-room floors, mega-dungeons, or sessions where time/resource tracking enhances play).

Player activities (one activity per stretch)

Ask each player “what are you doing for this 10 minutes?” — they pick one activity, mark it, and resolve it at the end of the stretch.

Typical activity list:

• Cast a spell (ritual/long action)
• Help / assist another character
• Interact (talk / manipulate)
• Keep watch (prevent surprise; very valuable)
• Loot everything (search thoroughly)
• Move quietly / scout
• Search area (takes the stretch)
• Take your time (general cautious activity)

Implementation: mark activity boxes on a tracking sheet, resolve checks and tasks, then roll for wandering monsters/random events at the end of the stretch.

Search and skill resolution

• Prevent skill dog-piling by making searches take time and by limiting what a single roll covers (example: one check per 5-ft square or one check per discrete item/area).
• Make activities worth it: keeping watch should reliably prevent surprise; searching thoroughly takes time but yields greater finds.

Combat flow improvements

• For many small fights, use a default dungeon-wide initiative (or no initiative / clockwise turn order) to avoid spending 10–15 minutes rolling initiative for each minor skirmish.
• Reserve full initiative for major fights; use streamlined mechanics for resource-draining minor encounters.

When to use dungeon turns (practical guidance)

• Use them when they make running the game easier or when you want time to matter: wandering monsters, timed hazards, long exploration, resource attrition.
• If the system is more prep work than it’s worth for a short or two-encounter dungeon, wing it instead.
• Rule of thumb: if a dungeon takes longer than about 10 minutes to clear or has multiple rooms/levels, dungeon turns add value.

Design / DMing tips and benefits

• Time as a resource encourages player engagement: players split tasks and keep everyone involved.
• Creates tension as resource consumption grows and the chance of an encounter increases.
• Stops players “going nova” every combat because fights and resources are spread across multiple encounters.
• Makes short rests in-dungeon a risky but mechanical choice rather than DM fiat.
• Speeds prep: you can prepare a usable dungeon in an afternoon that supports multiple sessions.
• Communicate the structure to players so they understand the rules and can plan.

Quick step-by-step to run a stretch

1. Declare the crawl has started (torch lit / entry).
2. Ask each player what they do for the next 10 minutes (pick an activity).
3. Mark activities on a tracking sheet (one box per stretch).
4. Resolve actions (checks, tasks, progress).
5. At end of stretch, roll wandering monsters/random event table and resolve.
6. Repeat.

Examples of non-standard uses

• 10-minute beats to escalate tension on a train ride.
• Hauntings every stretch in a haunted house (repeated rolls escalate to violent phenomena).
• Timed heist tasks (vent crawling while a vent elemental roams).
• A random event table that alternates combat and flavor events to shape the dungeon’s vibe.

Practical caveats

• Don’t force it if it over-complicates play for your table.
• Try a quick implementation with a single index card and a d6 to test the idea.
• Make the activities and rules easy to reference so players can use the structure to argue and plan (better than secret DM rules).

Where to get more material

• Mystic Arts / The Broadsheet (digital magazine on Patreon) — play-ready dungeon engineering rules, random tables, magic items, and a City of Brass mega-dungeon generator.
• The video creator sells separate “dungeon engineering” rules and runs a community (links in the video description/shop).

Gamers and sources featured / mentioned

• Davi (video creator, Mystic Arts)
• OSR creators and products: Taran Pound (Vagabond), Free League (Dragonbane), Gavin Norman (Old-School Essentials / OSE), Kelsey Dion (Shadowdark)
• Justin Alexander (referenced for “player unknown structure” concept)
• Historical figures: Gary Gygax and Dave Arneson
• The Broadsheet and the broader OSR / grognard community