How do I run exploration in a huge ruined city?

Why a street-by-street map stalls the table

The temptation with a ruined capital, abandoned megacity or fallen port is to draw every street and treat the whole place as one enormous dungeon with fog of war. That approach creates two problems at once. If you reveal the full map, the city loses its sense of scale and mystery in a single session. If you hide it behind corridor-by-corridor exploration, a location meant to sustain ten or twenty sessions turns into slow, low-choice grid crawling where every junction costs the same amount of attention.

A city that size is not really one location. It is a region that happens to have roofs and walls. Wilderness exploration already solved this using pointcrawls and hexcrawls, and urban ruins benefit from the same shift: important places and the routes between them matter more than mapping every block. Give players meaningful choices about where to go, what to risk to get there, and what they learn once they arrive, rather than asking them to account for every turning.

Treat the city as a layered pointcrawl

For a first playable slice, five-ish districts are often enough; add more when the campaign needs them. Each district is a node with the same depth you would give to a village or small valley:

• Districts as nodes with identity Name each district by what it once was and what now defines it: the Flooded Dockyards, the Glassmakers' Quarter, the Cathedral Precinct. For each, note its current character, its dominant danger or inhabitant, an orientation cue, and an active discovery such as a vault, archive, shrine or survivor enclave that makes a visit worthwhile.
• Pointcrawl routes, not street grids Link districts with a small set of named routes: a half-collapsed boulevard, a canal, a rooftop run, a service tunnel, or a cleared patrol road. Give each route an approximate travel time, hazard and cost such as noise, exposure, supplies or toll. Keep the network looped where it makes sense, with trade-offs players can weigh before they commit.
• Orientation cues that set goals Give players ways to orient themselves: a leaning tower above the roofs, bells audible through the streets, smoke, a beacon, a familiar smell or a signal on the radio. Some cues are visible from afar; others become clear only from a rooftop, in certain weather, or once a route reaches higher ground. They give direction without requiring you to reveal every intervening street.
• Information follows the fiction Reveal information when the fiction gives characters a reason to learn it. Skyline features may be obvious; residents may know common routes; a high vantage can reveal geography; an archive can show historical access; scouting can expose patrols; rumours can suggest uncertain possibilities; and helping a faction may open access to protected knowledge. Do not hide information just because the party has not completed a prerequisite.
• Routes as the best reward The most satisfying treasure in a huge city is often not coin but mobility. A cleared alley that avoids the main patrol, a rowboat that crosses the flooded ward, a secured stair through a collapsed arcade, or a repaired cableway changes future journeys. Track each route qualitatively as unknown, known, dangerous, secured, blocked or contested; its state can change when a faction moves, weather shifts, infrastructure fails, the party clears it, or enemies learn how it travels.
• Nested adventure sites inside districts Inside a district, zoom in only when players commit to a specific ruin: a single tower, vault, sewer nexus, temple or stronghold. Run that building as a conventional dungeon or compact pointcrawl of rooms and chambers. When they leave that building, return to the district and route scale. The city frames the dungeon; it does not replace it.
• Factions and territory that move Assign each district a current holder or pressure: a militia remnant, scavenger guild, cult, occupying company, nesting creature, or simply hazard and emptiness. Note what that holder wants, what it patrols, and what happens if the party helps, robs or displaces it. The city need not wait for the party: between expeditions, patrols may shift, scavengers strip a site, weather floods a route, a faction fortifies a district, or rumours about the party spread. The map stays mostly the same; its routes and occupants change.
• Environmental pressure on travel Let choices during movement matter. Darkness that demands light, unstable floors, hostile patrols, cursed wind, rain that floods low streets, dwindling clean water or daylight hours that force a camp all turn travel time into a budget. Keep pressure visible so players can prepare or accept risk rather than being punished after the fact.

Run each journey as a short loop

When the players say, “We want to get from Gate Ward to the Cathedral”, let them choose a destination and route. Tell them the known travel time, cost and risk before they commit, including what they can prepare for. Once they set out, advance relevant time, light, supplies or exposure. Resolve a travel event only if there is meaningful uncertainty or pressure; not every trip needs a random encounter. Then arrive, reveal what the journey or a new vantage makes knowable, and update the route's state on the shared map.

Resolve uncertain travel; summarise mastered travel. Once a route is mapped, its main hazard cleared or passage secured, repeated safe journeys can be compressed unless something meaningful has changed. A secured thirty-minute stair should feel different from the two-hour exposed boulevard it replaced. Between expeditions, update route states and occupants when time, faction moves or hazards give you a reason to do so.

Obstacles are pressures, not progression locks

An obstacle should follow from the city's history and be legible before the party commits. Treat it as a visible pressure that makes a route costly, dangerous or uncertain until the situation changes, rather than as a reason the party simply cannot go. Where the fiction allows, they can push through at high risk, improvise protection, take a costly detour, negotiate passage, find another route, change the environment, or decide the destination is not worth it yet. Some things really are impassable, but let that follow from the fiction rather than a progression plan.

Prepare why the obstacle exists, what would logically change it, and one or two known opportunities. Accept other solutions that fit the fiction. For the flooded lower wards, boats may be known and sluice controls rumoured; players might instead build a raft, climb the roofs, drain a cellar route, bargain with ferrymen or use a fitting ability. The obstacle invites planning without demanding the GM's intended unlock.

City pressures and possible responses

Progress means better choices, not just more map

The Metroidvania comparison helps when progress means growing competence and local knowledge rather than collecting keys. A changed situation may give the party better choices: a safer path, a vantage that reveals new orientation cues, introductions to a faction that trades maps for favours, or control of a district that becomes a forward base with supplies and rest.

Start with enough information for players to make meaningful choices, then add detail as they explore. Some rumours become located sites; hard journeys become known routes. Over time, the party moves through the same city faster, quieter and with more options about who to deal with or avoid. Revisiting an early district can produce new play because its holder, patrol or hazard may have shifted.

Prepare a city you can run next session

Use this as a starting pass before you place the city on the table:

• Sketch a few districts as named nodes, each with one or more orientation cues and notes on when characters can sense them.
• Connect them with routes and note approximate travel time, hazards and costs; offer useful trade-offs where the city supports them.
• Give the party enough visible or otherwise knowable destinations to make a meaningful choice; the right number depends on the table and campaign.
• Seed a handful of leads and note how characters might learn each one, without hiding obvious information behind prerequisites.
• For each significant obstacle, note why it exists, what could logically change it and one or two known opportunities; leave room for other fitting solutions.
• Prepare nested sites in districts the party is likely to visit first as small dungeons or compact locations you can zoom into when players commit.
• Assign a holder, patrol pattern or environmental pressure to each district and note how it might change if the party displaces, bargains with or ignores them.
• Track route states such as unknown, dangerous, secured, blocked or contested, and update them when the fiction changes.