Flux Space: Megadungeon Structure Without Megadungeon Effort

Abstract

Flux Space separates a dungeon into two types of content:

Locations — fully keyed map sections that fit on a single sheet of graph paper; no direct connection to other Locations
Flux Space — abstracted corridor networks connecting Locations; no specific map; defined only by description, size, and an encounter table

The overall dungeon is depicted as a flow-chart showing how Locations and Fluxes connect. The approach delivers megadungeon feel (huge, interconnected, dense) without megadungeon prep (exhaustive room notes across stacked graph paper).

Structure

Locations

Standard keyed dungeon content: map + room notes
Fit on a single page
Do not directly connect to other Locations — all inter-Location travel requires passing through Flux
Exception: secret shortcuts and vertical connections may directly link Locations (used sparingly)

Flux Space

Each Flux section has three elements:

Element	Purpose
Description	Vague consistent appearance: "Worked stone," "Oozing walls," "Piled garbage" — gives each Flux personality for improvised specifics
Size	A number: how many encounter rolls players must make to pass through to the next Location
Encounter table	Wandering monsters, events, entries from adjacent Locations' inhabitants

Flux is not literally empty — it contains bedrooms, storerooms, gymnasiums — but nothing is valuable, dangerous (outside the encounter table), or requiring investigation. It's connective tissue, not content.

The Dungeon Map

A spider-web flowchart showing Locations as nodes and Flux sections as labeled edges. Reference codes on each node and edge keep the referee oriented.

Play Procedure

Party enters Flux Space from a Location
Make encounter checks equal to the Flux's Size number; resolve results as they occur
After rolling the required number of checks, randomly determine which connected Location they emerge into (usually excludes origin Location; may allow "lost" result returning them there)
Mapped Flux: once all encounter table entries have been encountered, that Flux is considered mapped — players can move through with a single check and choose their destination

Mapping Flux is a player-facing achievement: it transforms uncertain transit into controlled navigation. The dungeon shrinks experientially as players learn it.

Design Rationale

The problem it solves: megadungeon scope requires interconnection and scale, but exhaustive corridor notes produce referee paralysis and mapping collapse. A quarter-inch stack of graph paper with cross-referenced alphanumeric codes is a real prep trap.

Pointcrawl logic applied to dungeon interiors handles this: the corridors exist and are real in the fiction, but the referee only tracks meaningful nodes (Locations) and passage risk (Flux). Everything else is improvised from the Flux description when players ask.

Referee Implications

Flux descriptions drive improvisation: "oozing walls" is all you need to answer "what does this hallway look like?" without notes
Adjacent Location creatures bleed into Flux tables: gnomes from the Hall of Gnomes wander the connecting Flux; this gives Flux ecological coherence
Secret shortcuts provide player agency: once found, they allow bypassing a Flux entirely
Scale is felt, not mapped: players experience the dungeon as vast because Flux passages are uncertain and costly, not because you drew 200 rooms

Comparison to Other Approaches

Approach	Scale	Prep Cost	Player Experience
Full megadungeon map	High	Very High	Navigable, but prep often collapses
Linear dungeon	Low	Low	No spatial depth
Room-and-pillar grid	Medium	Medium	Functional but uniform
Flux Space	High	Low–Medium	Megadungeon feel; progressive map mastery

Sources

https://www.paperspencils.com/flux-space-in-dungeons/