Players entering a dungeon usually ask:
“Where should we go?”
Players entering a city, however, will often say:
“We go to the blacksmith.”
The difference seems small, but it reveals one of the fundamental problems of urban adventures.
In a dungeon, travel is part of the game. As you move through corridors, doors, and rooms, you do not know what you will encounter.
In a city, movement usually works like a menu.
Inn.
Palace.
Blacksmith.
Guild.
“We go there.”
The scene changes.
Justin Alexander’s Urbancrawl approach addresses exactly this problem: turning the city from a backdrop where adventures happen into an explorable game space.
Rolling on Every Street Is Not an Urbancrawl
The first mistake is translating city travel directly into a dungeoncrawl.
While the players are walking to the inn, saying:
“You move one street forward. Let’s roll for an encounter.”
does not make the city explorable.
It only slows the journey down.
Cities are not dungeons.
Cities are designed for people to live in. Under normal conditions, people can get from home to the market. Guards know the roads. Streets have signs. Traveling from one place to another is usually not an adventure.
Alexander therefore distinguishes between Moving and Crawling.
Moving is when the players travel normally to a place they know.
Crawling is when they actively engage with the city: they are looking for something, being followed, escaping someone, moving through dangerous districts at night, or navigating a city that no longer functions normally.
This distinction is extremely useful.
It means you do not need to play out every movement.
You play out only the movement that matters.
Divide the City Into Districts
The most exhausting way to run a city is to prepare every building.
Hundreds of shops.
Dozens of inns.
The NPCs living in every house.
Most of that material will never be used.
A more useful scale for an Urbancrawl is the district: a neighborhood or region.
For example:
Old Town.
The Harbor.
Nobles’ Hill.
The Smiths’ Quarter.
The Temple District.
The players know where these areas are.
Each district also has a few memorable features. The great shipyard dominates the Harbor. A ruined clock tower stands in the center of Old Town. Iron gates close Nobles’ Hill at night.
But you do not prepare the interior of every building.
What you prepare is the content the players can discover in that district.
More Than One World Exists in a City at the Same Time
Layers are one of the strongest parts of an Urbancrawl.
Two different groups walking down the same street can discover completely different cities.
First layer:
Gangs.
Second layer:
The forbidden magic trade.
Third layer:
Missing people.
Fourth layer:
Heist targets.
Each layer distributes nodes across different districts of the city.
The Harbor District, for example, might contain both a gang warehouse and a dealer in smuggled magic items.
If the players are investigating “What is in the Harbor?”, they may encounter one of these layers.
But if they say:
“We are investigating the trail of the missing people in the Harbor.”
you look directly at the layer connected to that subject.
Alexander describes this distinction as generic investigation and specific investigation. The fundamental action of an Urbancrawl is not geographic movement, but the player choosing a district and investigating it.
This is where the city stops being a menu.
The players decide not only where to go, but what to look for when they get there.
Hidden Nodes Give the City Depth
Not all content needs to be discoverable from the beginning.
Suppose there are three vampire dens in the city.
The players discover one of them.
Inside, they find a letter.
The letter mentions Count Ormu.
A new node has now opened.
Or perhaps the players eliminate several vampire cells in the city. The network has taken enough damage that higher-level actors are forced to move.
They become visible as a result.
This structure lets an organization behave like an explorable network instead of simply being “the big villain and their henchmen.”
Resolving lower-level nodes can reveal the deeper connections beneath them.
Ask the Player, “What Are You Doing in the City?”
You do not need a highly complicated system for an Urbancrawl.
The basic procedure can be surprisingly simple.
The player chooses a district.
“We investigate Old Town.”
The GM asks:
“What are you looking for?”
If the players have no specific goal, they make a generic investigation. An appropriate discovery emerges from one of the active layers in that district.
If they have a specific goal, you look at the relevant layer.
“We are looking for somewhere the alchemists sell contraband.”
There is no point in drawing a random encounter from the vampire table now. The players receive an answer from the world about the thing they are investigating.
You can use an appropriate check for your system if needed. But failure should not always mean:
“You find nothing.”
Perhaps they reach the information, but the wrong person notices their investigation.
Perhaps they find the informant, but the informant wants money.
Perhaps they learn where the place is, but they must go there at night.
The investigation advances, and the city reacts.
Turn the Die Result Into a Scene
The player makes an Investigation check.
They succeed.
“You learn where the vampires are.”
Technically, that is enough.
But it wastes the strength of the Urbancrawl.
Instead, you can open the result as a scene:
“You are in the back room of a narrow tavern. After finishing his third drink, the informant leans over the table. ‘Look at the warehouses north of the Harbor,’ he says. ‘But not after sunset.’”
The same information.
But now a moment has happened in the city.
Let the City Grow Behind the Players
The purpose of an Urbancrawl is not for the GM to prepare an enormous city encyclopedia in advance.
It is the opposite.
At the beginning, there are a few districts.
A few layers.
A few nodes in each layer.
New connections emerge as the players investigate.
New NPCs become important.
Some nodes disappear.
Some become other nodes.
If the players burn down a criminal organization’s warehouse, it is no longer the same node next week.
Perhaps it has become the guard’s investigation headquarters.
Perhaps a rival gang has taken over the area.
Perhaps the only survivor of the fire has become a new enemy.
You do not “prepare” the city this way.
You allow it to grow during play.
Turn the City From a Menu Into a Map
There is nothing wrong with the players saying:
“We go to the blacksmith.”
Playing every scene as an Urbancrawl would be unnecessary.
But when the players are truly looking for something in the city, questions begin to appear:
“Which district are we investigating?”
“What are we looking for?”
“Which of our contacts are we asking for help?”
“What is the cost of uncovering this information?”
When those questions arise, the city is no longer merely a menu of shops.
The players learn its structure.
They recognize its districts.
They notice who holds power where.
They see that something they did in one district has consequences in another.
After a while, the GM’s map and the city in the players’ minds begin to become the same thing.
That is the real achievement of an Urbancrawl:
turning the city from a place to visit into a system to explore.