
Running the City
A Trebuchet Games GM Tool for Urban Play
Practical tools for making cities feel different at the table.
Introduction
Cities are one of the most loved adventure settings. The bustle of a crowd, the danger of pickpockets, the corrupt city official, and questionable strangers all around.
But players and GMs alike can run into problems when the adventure moves into a city. Do any of the following sound familiar?
- The city feels just like the village.
- It’s just a list of shops, like a menu.
- There’s too much to keep track of.
- I need 400 NPCs to make this area realistic.
Trebuchet Games uses our tools to narrow the focus for the GM while broadening the world for the players.
You don’t need to build an entire city to make your players feel like they’re standing in one.
The goal of this tool isn’t to create a complete city for you. It’s to give you practical ways to make city play feel different at the table: more people, more movement, more interruptions, more encounters, more distance, and more things happening that have nothing to do with the characters.
1. The People
Cities are filled with people. A GM who wants the world to feel alive around the players can feel pressure to create hundreds of individual NPCs. That’s work the GM doesn’t need.
In Meaningful Connections, Trebuchet Games uses NPC Groups as a single entity to describe NPCs who share a similar feature, purpose, or activity.
- 8 kids playing ball in the street? 1 NPC Group.
- 20 people shopping in the market? 1 NPC Group.
- 6 clerks leaving a government office? 1 NPC Group.
- 12 dockworkers unloading a barge? 1 NPC Group.
Describing the Groups lets the party know how many people are around, while the GM only has one entity to handle. Five NPC Groups of 20 people give you 100 people without creating 100 NPC sheets.
Detached NPCs
Most city NPCs are strangers to the characters. They have jobs, appointments, families, errands, and problems of their own. Unless the characters give them a reason to care, casual NPC interactions can be more detached than they would be in a village.
- The shopkeeper has other customers.
- The clerk has a line.
- The guard has somewhere else to be.
- The server is carrying three other tables.
- The passerby may answer a question, but may not stop for a conversation.
Detached doesn’t mean hostile. It means the characters aren’t automatically the most important people in the room.
2. Description Is Your Key
Read-aloud text does double duty in city settings. It tells the party not only what is around them, but who.
A group of civic sewer workers, clerks heading to the office, and specialists discussing their trade immediately give the location a city feeling. Noise, smells, people, work, and movement are your aim.
Show the City Working
Don’t only describe buildings. Show the systems that keep thousands of people alive and organized.
- Sewer workers lift a grate and lower someone underground.
- Guards change shifts at a gate.
- A delivery wagon unloads flour at a bakery.
- Couriers run sealed documents between public offices.
- Labourers repair a damaged street.
- Market workers erect stalls before the crowds arrive.
- Porters move crates from a warehouse to waiting carts.
These details can distinguish districts without requiring paragraphs of exposition. The docks, the administrative district, a wealthy residential street, and a crowded market should not sound, smell, or move the same way.
3. Distance
Cities are big. Walking from one shop to another in a small village is often negligible, but travelling from the inn to the castle in a city can be almost an adventure in itself.
City movement should take time. Crowds, carts, crossings, gates, narrow roads, construction, markets, bridges, and public events can all slow movement. The characters may be able to choose a faster route, a quieter route, or a longer route that avoids the worst congestion.
When distance costs time, movement becomes a player choice rather than a teleport button. The time spent crossing the city can also matter to events happening elsewhere.
Know the Routes
The GM should have a general understanding of the major routes through the city before play. You don’t need to plan every street, but you should know the main ways characters are likely to travel between important Locations and anything that will affect those routes.
Some obstacles and Events should already be there before the characters choose their route. A parade may be scheduled along Main Street. A bridge may be under repair. A market may fill a particular square every morning. A gate may close at sunset.
If the characters choose that route, the obstacle is already there. The parade didn’t suddenly appear because they picked Main Street. Route Conditions are things the GM knows ahead of time; Random Encounters are the things that may happen while the characters travel.
A few route notes may be all you need:
- Main Street: Normally Busy. Packed during the scheduled parade from noon to 2:00 p.m.
- River Road: Crowded in the morning while cargo is unloaded.
- Temple Lane: Quiet most of the day.
- East Bridge: One lane closed for repairs; travel time increased.
Working City Movement Procedure
1. Choose the destination and route.
2. Estimate the base travel time or distance.
3. Determine the Street Condition for the route and time of day.
4. Adjust travel time for congestion or obstacles.
5. Check for Trebuchet Random Encounters at the appropriate frequency.
Living World If you are using a Living World, advance the city clock and update any Events, NPCs, Locations, or other circumstances that change while the characters travel.
Street Conditions and Travel Time
Street Condition changes how long it takes to move through the city. Apply the multiplier to the normal travel time for that part of the route.
| Street Condition | Travel Time |
| Quiet | ×1 |
| Busy | ×1.25 |
| Crowded | ×1.5 |
| Packed | ×2 |
| Crush | Travel resolved as a crowd hazard |
For example, a trip that normally takes 20 minutes takes 25 minutes through Busy streets, 30 minutes through Crowded streets, and 40 minutes through Packed streets.
Mixed Conditions
If a route passes through more than one Street Condition, apply the multiplier to each part separately. For quick play, use whichever condition covers most of the route.
4. The City Keeps Moving
The city does not stop when the characters stop.
When the party stands on a street discussing what to do next, interrupt them occasionally with the city around them. A mother and child walk between two characters. A distant whistle sounds. Two men approach menacingly, then walk straight past. A wagon driver shouts for the party to move. Three clerks hurry by carrying stacks of papers.
Most of these interruptions don’t need to lead anywhere. They aren’t automatically plot hooks or encounters. They remind the players that thousands of other people are living their lives around them.
City Activity
If you know the location ahead of time, write some ordinary activity into the adventure. A baker has a delivery. Guards change shifts. Sewer workers have part of the road blocked. These details don’t need to become Encounters; they’re simply part of the place.
If you need something on the fly, roll on the table below. None of these are automatically Encounters. If the players decide to get involved, then it can become one.
| d20 | City Activity | d20 | City Activity |
| 1 | Workers unload a cart. | 11 | A wagon driver argues with a pedestrian. |
| 2 | Two people argue over a delivery. | 12 | A group of workers heads home at the end of a shift. |
| 3 | A child runs through the crowd chasing an animal. | 13 | An animal gets loose. |
| 4 | A merchant loudly advertises their goods. | 14 | A public notice is being posted. |
| 5 | Guards change posts. | 15 | Two people stop in the street to gossip. |
| 6 | A courier pushes through the street. | 16 | A delivery is carried into a nearby business. |
| 7 | Someone drops and breaks something. | 17 | Someone stops a passerby to ask for directions. |
| 8 | Labourers block part of the road while working. | 18 | A shopkeeper sweeps rubbish into the street. |
| 9 | A street performer gathers a small crowd. | 19 | A patrol passes through. |
| 10 | Someone leans from an upper window and shouts to the street below. | 20 | Roll twice; both things are happening nearby. |
The Irrelevant Is Important
Not everything the GM describes needs to be about the characters. Once players learn that ordinary city life is constantly happening around them, described people and Events stop feeling like glowing quest markers. If the characters decide something matters, they can choose to make it matter.
5. Encounters
Cities have more encounters than wilderness. Not combat encounters – encounters.
A thief steals from a shopper. A child chases a puppy through the street. An escaped pet owlbear runs loose. A cart breaks an axle. Workers argue over who is responsible for moving it. A public official arrives with an escort. A street performer attracts a crowd.
Encounters are happening all over the city all the time. A crowded urban area should give the party more chances to run into something than an empty road through the wilderness.
Encounter Checks
For every 30 minutes or part thereof of city travel, make one Encounter Check. An Encounter occurs if the die result falls within the range shown below.
| Street Condition | d6 | d8 | d10 | d12 | d20 |
| Quiet | 1 | 1 | 1-2 | 1-2 | 1-3 |
| Busy | 1-2 | 1-3 | 1-3 | 1-4 | 1-7 |
| Crowded | 1-3 | 1-4 | 1-5 | 1-6 | 1-10 |
| Packed | 1-4 | 1-5 | 1-7 | 1-8 | 1-13 |
| Crush | No roll | No roll | No roll | No roll | No roll |
Pick whichever die you like and stick with it for the journey or scene. In a Crush, don’t roll; the crowd is already the Event or hazard.
Mixed Conditions
If the route changes Street Condition, use the condition the characters are in when you make the check. For quick play, use whichever condition covers most of the route.
Trebuchet Random Encounters
Use the established Trebuchet Random Encounter structure:
| Description | Event | Outcome |
| What the characters notice. | What is happening. | What changes, persists, or can result from interaction. |
The Encounter doesn’t have to stop travel for a fight. It can simply be one more piece of the city in motion.
6. Density
Denser parts of the city have more people, more encounters, slower movement, and potentially more danger. Density can change by district, time of day, and circumstance.
A dock road may be Packed at dawn and Quiet after midnight. A government district may be Busy during office hours and nearly empty late at night. A market can shift from Crowded to Packed when a festival begins.
| Street Condition | Travel | Encounters | What It Feels Like |
| Quiet | ×1 | Low chance | Side streets, early morning, quiet residential areas |
| Busy | ×1.25 | Increased chance | Working streets, shops, regular daytime traffic |
| Crowded | ×1.5 | High chance | Markets, docks, festivals, shift changes |
| Packed | ×2 | Very high chance | Processions, major Events, gate openings, bottlenecks |
| Crush | Crowd hazard | No Encounter roll | Riot, evacuation, panic, disaster, fleeing crowd |
7. Crowd-Related Checks
Do not make characters roll just to walk down a busy street. A check should exist because the crowd makes an action uncertain and failure has a meaningful consequence.
The travel multiplier already represents ordinary difficulty moving through the city. Crowd-related checks become useful when characters are trying to do something against the flow, pressure, noise, or confusion of the people around them.
Default Crowd DCs
| Street Condition | Default Crowd DC |
| Quiet | No check normally required |
| Busy | No check normally required |
| Crowded | DC 10 |
| Packed | DC 12 |
| Crush | DC 15 |
Use the Crowd DC only when the crowd is what makes the action difficult. If someone is actively hiding, fleeing, grappling, or opposing the character, use the normal rules for that action instead.
Crowd Check Examples
| Situation | Possible Check | Possible Consequence |
| Force through a Packed crowd quickly | Strength (Athletics) DC 12 check | Lose time, attract attention, or fail to make progress |
| Weave quickly through a Packed crowd without shoving people | Dexterity (Acrobatics) DC 12 check | Lose time, collide with someone, or draw attention |
| Keep sight of someone through a Crowded market | Wisdom (Perception) DC 10 check | Lose sight of the target |
| Keep the party together in a surging Packed crowd | Wisdom (Perception) DC 12 check | One or more characters become separated |
| Move safely through a dangerous Crush | Appropriate DC 15 check or saving throw | Fall, become separated, be carried in an unwanted direction, or suffer another crowd consequence |
If circumstances make the crowd meaningfully easier or harder to deal with, lower or raise the DC by 2.
Dangerous Crowds
Use an ability check when the character chooses to push against the crowd. Use a saving throw when the crowd suddenly does something to the character.
- The character tries to force a path through the crowd: use an ability check.
- The crowd suddenly surges, panics, or crushes inward: use a saving throw.
When a crowd suddenly surges or becomes dangerous, affected characters make an appropriate DC 15 saving throw. Strength can hold position. Dexterity can keep a character on their feet or out of an obstacle.
On a failure, choose what makes sense for the situation:
- Knocked Prone.
- Carried 10 to 30 feet with the crowd.
- Separated from companions.
- Pinned or Restrained against an obstacle.
- Dropped or lost unsecured equipment.
- Minor bludgeoning damage where actual crushing, trampling, or collision occurs.
Don’t deal damage just because the density reached Crush. A festival crowd surging toward a performer and a panicked mob fleeing a burning building can both be a Crush, but only one is likely to hurt somebody.
8. Setting the Scene: City Battle Maps
Groups that use theatre of the mind can run these rules without a map. For groups that enjoy visual positioning, city scene battle maps let the GM zoom in when an urban interaction becomes spatially important.
The GM does not need a battle map for the entire city. The city can remain abstract at the large scale, while important moments use reusable scene maps.
Suggested Reusable Urban Scenes
- Busy Market Street or Square: Crowds, stalls, pickpockets, public performances, arguments, runaway animals, pursuit, separation.
- Alley Network or Back Street: Chases, surveillance, hidden meetings, service entrances, criminal activity, shortcuts.
- Gate, Bridge, or Chokepoint: Inspections, tolls, bottlenecks, lines, protests, accidents, crowd pressure.
- Dockside or Warehouse Edge: Loading cargo, labour, smugglers, ropes, carts, cranes, slippery surfaces, water access.
- Courtyard, Tenement, or Shared Yard: Residents, gossip, domestic activity, children, neighbourhood tensions, witnesses at windows.
- Public Office, Guild Reception, or Waiting Area: Bureaucracy, petitions, appointments, clerks, guards, overheard conversations, waiting crowds.
These are just ideas for reusable city scenes. This article includes one: Dockside / Warehouse Edge.
Dockside / Warehouse Edge Example
The dockside map shows how much play you can get out of one city scene without mapping the entire city.
A dockside battle map gives you water, dark alleys, spaces beneath the docks, ships, crowded warehouses, shady businesses, cargo, ropes, carts, cranes, and narrow routes. It also gives you sailors, dockworkers, warehouse workers, guards, smugglers, merchants, pirates, and whatever may be living in the water.

What Makes a City Scene Map Useful
- People and NPC Groups already using the space.
- Visible city systems: deliveries, workers, guards, drains, carts, queues, repairs, or administration.
- Movement constraints and chokepoints.
- Clutter and objects the characters can interact with.
- More than one route through the scene when appropriate.
- Signs of the district and its normal activity.
- Space for Trebuchet Random Encounters to become spatial if the players engage.
Putting It Together
You don’t need to simulate the whole city. You only need enough information to make the part around the characters feel like one.
| Route | Street Condition | Travel Time | Encounter | Scene |
| Choose destination and route | Determine how busy the streets are | Apply the multiplier and any Route Conditions | Make the Encounter Check | Zoom in with a scene map if needed |
Free Download: City Travel Tracker Use the printable City Travel Tracker to record routes, base travel time, Street Conditions, planned Route Conditions, Encounter Checks, and final travel time. Download it from the Trebuchet Games Library.
Use what works for your table. Throw away the rest.
Narrow the focus for the GM. Broaden the world for the players.

Leave a Reply