Strategic Review Solo Dungeon Adventures Tables

Overview

This source documents the earliest known procedural dungeon-generation algorithm, published in Strategic Review (1975). It provides a complete traversal-driven chain of seven linked tables for solo or emergent dungeon mapping.

The 7-Table Algorithm

Every room and passage is generated by moving through the dungeon and triggering checks — the dungeon grows from exploration, not pre-placement.

Table	Triggers When	Die
1: Periodic Checks	Every 60' of passage (30' after door or side passage)	d20
2: Doors	Table 1 rolls 4-7	sub-tables
3: Side Passages	Table 1 rolls 8-10	sub-tables (type + width)
4: Turns	Passage direction needed	sub-tables
5: Chambers & Rooms	Table 1 rolls 14-16, or door leads to one	shape + exits + contents sub-tables
6: Stairs	Table 1 rolls 17	d20
7: Traps	Table 1 rolls 19, or Chamber Contents roll	sub-tables

Table 1 full results (d20): - 1-3: Continue straight; check again in 60'. - 4-7: Door → Table 2. - 8-10: Side passage → Table 3; check again in 30'. - 14-16: Chamber → Table 5. - 17: Stairs → Table 6. - 18: Dead end (check walls for secret exits per Table 5 footnote). - 19: Trap → Table 7; passage continues, check again in 60'. - 20: Wandering Monster; roll for spawn direction.

Table 6 Stair Types (d20): 1-5 Down one level · 6 Down two · 7 Down three · 8 Up dead-end · 9 Down dead-end · 10-11 Chimney up one · 12-13 Chimney down one · 14-18 Trapdoor down one · 19-20 Trapdoor down two.

Important Expansion Tables in the Source

The raw text includes additional details often omitted in short summaries.

Table 5.6 Treasure Scaling

Treasure scales per level with structured coin bands.
"With monster" treasure routes to OD&D outdoor treasure logic with proportional adjustments.
High rolls add gems, jewelry, or magic.

This makes the generator not only spatially procedural but also reward-procedural.

Stair and Trap Clauses

Source stair entries include extra logic such as one-day closure doors and collapsing chute risks. Trap tables include gas subtype effects (blindness, fear, sleep, strength boost, sickness, poison).

These clauses are valuable because they inject stateful consequences into traversal, not just map geometry.

Table 8 Caves and Caverns (Optional Lower Floors)

The source includes an optional lower-floor cave/cavern complex with:

cavern size generation,
pool and lake sub-tables,
magic pool effects (stat shifts, wish logic, transport effects),
optional 1-in-6 monster presence framework.

This is effectively a mode switch from corridor architecture to large natural spaces.

Baseline Rules

Three hard constraints from the original text:

The upper dungeon level must be fully pre-planned (not random) and must include outdoor encounters and a central staircase into the dungeon proper.
The first randomized level begins generation from the center of graph paper; expansion radiates outward.
Rooms must not extend beyond graph paper edges; any boundary-violating roll is rerolled — "common sense is crucial."

Secret door search: for every 10' of wall, roll a d12 — a 1 finds a secret door, a 12 triggers a wandering monster.

Why It Holds Up

The algorithm never generates features in isolation. Every element — door, room, stair, trap — is triggered by the act of traversal (passage → check → result). This means the dungeon grows organically from exploration rather than from a pre-laid-out map.

It produces irregular, non-repeating layouts with genuine surprise even for the referee, because the referee is also exploring. Compare against modern "room template" approaches, where layouts are set before play. The Strategic Review method makes the referee a fellow explorer.

Useful as a benchmark when designing any procedural dungeon tool: does your system produce emergent geometry, or does it just dress up a fixed architecture?

Referee Implementation Pattern

For current solo and one-on-one use, run the algorithm as a strict loop:

Traverse 30-60 feet.
Trigger periodic check.
Resolve generated feature.
Apply secret-door and trap side rules when prompted.
Record spatial and state changes before next move.

The crucial extraction from the source is "common sense plus reroll boundaries": keep the algorithm moving, but block nonsensical outputs.

Design Implications for Tooling

This source remains useful for MCP and software tooling because it is already a deterministic table chain:

clear trigger points,
explicit dice inputs,
unambiguous state transitions,
straightforward auditability for referee-facing assistants.