Introduction
Maps in Twilight: 2000 are how the group turns a broad survival problem into a series of choices. A travel map asks where the party can go, what it must spend to get there, and what kind of ground it will cross. A battle map asks where everyone is standing when seconds, cover, range, and movement matter. A city map narrows travel to dense streets, blocks, and local obstacles.
The most useful habit is simple: do not ask a map to answer a question at the wrong scale. Plan the journey on the travel map. Resolve a confrontation on a battle map when positions matter. Return to the travel map after the immediate situation changes.
On the travel map, the game becomes an open-world hex crawl. The party decides where to go, what to spend, whom to trust, and which risks are worth taking. Rumors, needs, personal goals, weather, factions, and consequences turn geography into a story. This guide covers both halves: reading the maps, and running the campaign loop that moves across them.

Hot Take
The travel map is the campaign's decision board, not the Referee's secret puzzle. Players should be able to see enough terrain, routes, and uncertainty to make real tradeoffs. Hidden information can create tension; hidden choices only create frustration.
The same goes for the hex crawl. A good one is about making every chosen route mean something, more than about discovering every hex. If players always know why they are moving, what it may cost, and what could change their mind, the open world stays focused.
For the rules-facing travel pressures behind the map, see the survival and resources guide.
The three map scales
The game moves between three scales. Each has a different job.
| Map scale | What it represents | Main question | Use it when |
|---|---|---|---|
| Travel map | The campaign region and long journeys | Where do we go, and what will it cost? | Planning routes, crossing terrain, spending travel time, seeking resources |
| City map | A town or city at a tighter travel scale | Which district, street, or route can we use? | Moving through populated or dense urban areas |
| Battle map | The immediate scene of a conflict or tactical problem | Where are we, what can we reach, and what protects us? | Combat, tense standoffs, vehicle positions, hazards, close exploration |
Official travel maps use broad hexes to regulate movement across a region, while battle maps use a much smaller tactical hex. You do not need to recite those measurements during play. The important distinction is narrative: one travel hex covers a meaningful stretch of country; one battle hex covers a meaningful piece of immediate terrain.
If a group is choosing between a paved road, a forest track, and a river route, use the travel map. If it has reached a blocked bridge and needs to decide who can see the party, where a vehicle can turn, or which wall provides cover, switch to a battle map or a quick sketch.
Read a travel map as a resource plan
A travel route has at least five costs: time, food and water, fuel or endurance, exposure, and uncertainty. The map lets the party compare those costs before committing.
| Map feature | Likely advantage | Likely tradeoff |
|---|---|---|
| Major road | Faster and easier movement | More visible, more likely to be watched or controlled |
| Woods | Concealment, firewood, possible food | Slower movement, reduced visibility, difficult driving |
| Open ground | Clear navigation and long sightlines | Exposure to weather and observation |
| Hills or mountains | Observation, defensible routes, landmarks | Slow progress, fatigue, difficult vehicles |
| Swamp or broken ground | Concealment and a route others may avoid | High travel cost, risk of delay or getting stuck |
| Ruins | Salvage, shelter, clues, cover | Hazards, blocked movement, attention from others |
| River or lake | Water, fishing, a possible travel corridor | Crossing or boat requirements, weather, limited access points |
This is deliberately not a replacement for the terrain rules. The rules determine the exact mechanical effect. The table tells the group how to think about what it sees: every route solves one problem while creating another.
A major road may preserve fuel and daylight but make the party easy to spot. The forest route may conceal it but cost enough time that making camp becomes necessary. A river crossing may shorten the trip only if the group has a boat, a safe ford, a bridge, or a relationship with people who control one.
Give the party a route briefing
Before players choose a route, give them information in a consistent order. This avoids a common problem: the group makes a sensible plan, then discovers that all the relevant facts were withheld until after it committed.
- Destination: What is the party trying to reach or avoid?
- Known routes: Which roads, tracks, waterways, or trails are visible or rumored?
- Terrain: What kind of ground lies on each option?
- Time: How much daylight or how many shifts might each route take?
- Supplies: Which option is hardest on food, water, fuel, or maintenance?
- Known pressure: What danger, local rule, weather, or uncertainty is associated with it?
- Fallback: Where can the party stop, turn back, or change course?
The Referee does not need to reveal secrets. "The bridge may be controlled, according to a traveler from yesterday" is enough to support a decision. So is "the forest track is slower, but you can see signs that people use it." The players choose whether to investigate, take the risk, seek better information, or spend resources on a detour.
Running a Game This Week?
The GM Session Kit - a Session Zero template, a recap format, and a pricing cheat sheet. Free, and yours the moment you ask.
No spam, unsubscribe anytime.
Terrain should affect intent, not just speed
Travel terrain matters because it changes what the party can try. A woods hex may invite scouting, hunting, gathering fuel, or avoiding attention. A town may invite trade, repair, rumors, or trouble with local rules. A road may support a vehicle but put the group in view of anyone who uses the same corridor. Each terrain type should change at least one decision.
Ask these questions whenever the group enters new ground:
| Question | Useful answer at the table |
|---|---|
| What slows us down? | Dense growth, soft ground, steep terrain, wreckage, water, or poor roads. |
| What can we see from here? | Observation changes planning and risk. |
| What helps us survive here? | Firewood, food sources, shelter, salvage, water, contacts, or local routes. |
| What can move here? | The answer changes vehicle and pursuit choices. |
| What makes us visible? | Open ground, roads, water approaches, smoke, vehicle noise, or a known crossing. |
| Who is likely to use this place? | Farmers, traders, scouts, hunters, patrols, refugees, or people avoiding others. |
| What will this cost if we stay? | Time, exposure, supplies, and attention are all resources. |
| What could change our plan? | Weather, a blocked route, a damaged vehicle, a rumor, a sign of recent activity. |
That is enough to make a hex feel distinct and to make the map part of roleplay. A group that knows it must enter a settlement can decide how visibly to arrive. A group facing poor ground can choose to travel slower, look for an alternate route, leave a vehicle, or ask locals for help. You do not need to stop for a detailed scene every time the party enters woods. Summarize the ordinary progress, then pause when the terrain produces a choice: a fork in the track, fresh signs, a likely campsite, a vehicle problem, or a local person who knows the area.
Travel map to battle map: make a clean handoff
Switch to a battle map when the question becomes tactical. The travel map tells you that the party reached a forest road, ruined crossroads, lakeshore, or town edge. The battle map tells you where the road, trees, buildings, vehicles, people, and cover are in the immediate scene.
| Travel-map fact | Battle-map translation |
|---|---|
| Forest route | Trees, undergrowth, a narrow road, uneven sightlines, possible soft ground |
| Open farmland | Fields, ditches, fences, scattered buildings, long sightlines |
| Ruined settlement | Broken walls, blocked streets, interiors, rubble, uncertain cover |
| River crossing | Bank, bridge or ford, limited approaches, exposed waterline |
| Major road | Pavement, vehicles, roadside cover, open approaches, visible movement |
The translation should preserve the broad terrain but not become a rigid one-to-one copy. A travel hex is a large area. An "open" region can still contain a shed, ditch, hedgerow, or small stand of trees. A forest region can still contain a clearing. Pick the immediate details that make the scene interesting and fair.
That matters most in combat. The combat and weapons guide covers how cover, range, and tactics shape a fight. A good battle map gives players options: move, take cover, withdraw, flank, negotiate, use a vehicle, or avoid making the situation worse.
Battle maps do not have to mean combat
Use a tactical map whenever precise space matters, even if no one fires a shot. It can help with:
- approaching a guarded gate without looking hostile;
- searching a damaged building while keeping an exit open;
- moving a vehicle through a blocked route;
- rescuing someone from a flooded area;
- managing a tense negotiation where everyone is armed and wary;
- setting up a safe camp around a defensible location.
Conversely, do not force a full battle map for every conflict. The rules support theater of the mind in close quarters or at extreme range, where exact hex-by-hex movement may add little. Choose the map scale that gives the players the clearest meaningful options.
Make maps player-facing without spoiling the campaign
The party should not receive a complete intelligence map just because the Referee has one. It should receive what its characters can reasonably see, remember, ask, scout, or learn from a reliable source.
| Information type | Good way to present it |
|---|---|
| Visible terrain | Show it directly on the map or describe it plainly. |
| Known road or river | Mark it, including obvious damage or uncertainty. |
| Rumored danger | Add a note with the source and age of the rumor. |
| Hidden threat | Keep it hidden until the party has a fair way to discover it. |
| Faction boundary | Show signs, patrol activity, or local rules rather than a perfect border. |
| Possible destination | Mark a name, landmark, contact, or question - not necessarily a guaranteed reward. |
This preserves exploration without turning every turn into a blind guess. A map can have blank areas, question marks, partial routes, and crossed-out information. Those are useful because they tell players what they do not know.
City maps need a different mindset
City travel compresses distance but increases friction. Buildings, rubble, crowds, narrow streets, damaged utilities, local factions, and blocked routes mean that a short physical distance can take as much effort as a much longer rural stretch.
When the party enters a town or city, change the questions:
- Which district has the contact, market, shelter, or route we need?
- Which streets can a vehicle actually use?
- What local rules govern weapons, trade, entry, or curfew?
- Where are the exits if the situation changes?
- What can we learn before committing to a deeper approach?
Use a city map to make neighborhoods and movement matter, beyond serving as a larger battle map. A city is also a network of people, needs, and information.
A player map checklist
Before leaving a safe place, ask:
- What is our destination, and what would make us turn back?
- Which route best matches our supplies, vehicle, and time?
- What terrain will slow us, expose us, or offer useful resources?
- Who is responsible for navigation and keeping watch?
- Where can we stop if we do not arrive as planned?
- What rumor or unknown are we treating as a risk?
- What map change would make us reassess the plan?
The checklist is not about finding a perfect route. Twilight: 2000 is built on imperfect information. It is about making sure the party owns the risk it takes.
Running a Twilight: 2000 hex crawl
A Twilight: 2000 hex crawl gives the party its own reasons to move instead of functioning as a board-game march across empty terrain, and the group shouldn't have to wait for a plot to arrive. It should have reasons to move: reach a rumored market, find a missing person, avoid a hostile force, locate repair supplies, seek shelter, follow a radio message, return home, or help a community. The Referee's job is to give those reasons weight without deciding which one the party must choose.
The campaign loop
At its best, a hex crawl repeats a simple sequence:
| Step | Party question | What makes it dramatic |
|---|---|---|
| Get a lead | What matters next? | The lead connects to a need, hope, fear, or promise. |
| Choose a route | How do we get there? | Every option has visible benefits and costs. |
| Assign effort | What does each person do with this shift? | Moving competes with watching, gathering, resting, and other needs. |
| Meet a complication or opportunity | What has changed? | Terrain, weather, people, and consequences create a decision. |
| Make camp or reach a place | What can we safely do now? | Shelter, security, supplies, and relationships matter. |
| Reassess | What did we learn, spend, gain, or provoke? | The next choice reflects the world the party has changed. |
The loop is not rigid. A conversation can take the place of an encounter. A repair can consume a planned travel period. A rumor can send the party in another direction. The structure works because every interruption has a visible cost: time, attention, supplies, risk, or an opportunity left behind.
Start with two or three real leads
Open-world play can stall when a group has no reason to choose a direction. Do not solve that by giving it one mandatory quest. Give it a small set of practical possibilities.
| Lead type | Example player-facing information | Decision it creates |
|---|---|---|
| Shelter | "A settlement nearby sometimes takes in travelers who can work." | Do we risk local rules for a safer night? |
| Resource | "A workshop may still have the part our vehicle needs." | Is the detour worth fuel and exposure? |
| Person | "Someone matching that description was seen heading north." | Do we follow before the trail goes cold? |
| Threat | "A road has become dangerous, but no one agrees why." | Avoid it, investigate it, or prepare to cross it? |
| Rumor | "A radio operator has been asking for help." | How reliable is the source, and what might wait there? |
| Personal goal | "A character knows a possible route toward home." | Does the party support that hope now or later? |
The leads should be different enough that choosing one means delaying another. A safe camp may be in the opposite direction from a possible repair. A promising rumor may be less reliable than the road the party already knows. That tension is the heart of a hex crawl.
For a Referee, the useful preparation is not a script. It is a short note for each lead: what the party can learn, what pressure surrounds it, and what changes if the group arrives late, leaves, helps, or causes trouble.
Shift choices make time visible
The travel rules divide the day into shifts. That asks the party to choose how it spends limited time. Movement is important, but it competes with watching for danger, gathering, searching, foraging, hunting, fishing, resting, cooking, making camp, repairing, and exploring. Present this as a tradeoff rather than a list of chores.
| If the party chooses to... | It may gain... | It gives up or risks... |
|---|---|---|
| Move quickly | Distance, a chance to reach shelter or a lead | Time for food, repairs, information, or a safer camp |
| Keep watch | Early warning and better awareness | A person who cannot perform another full task |
| Search or scrounge | Useful material or clues | Travel time and exposure in one place |
| Forage, hunt, or fish | Food and local knowledge | Time, uncertainty, and possible separation |
| Rest | Recovery and a more capable group later | Progress and a chance to reach another destination |
| Make a proper camp | Better shelter and security | A shift spent staying put |
| Explore | Information, people, and opportunities | Route progress and supply consumption |
Players need to understand the opportunity cost of each shift more than they need to optimize it. If they choose to stop and help a settlement, that can be a good choice even if it delays the destination. The world should react to the delay, but it should also remember the help. The survival and resources guide covers the practical rules context for those pressures.
Rumors keep the sandbox moving
Rumors point the party toward possibility without guaranteeing a reward. A useful rumor has three parts:
- A subject: a person, place, resource, danger, or opportunity.
- A source: someone who may know, fear, want, or misunderstand something.
- A question: a detail the party can test through travel, observation, or conversation.
"There is a safe settlement east of here" is weak because it gives no decision. "A fisher says the eastern settlement will trade medicine for engine parts, but the road is watched" gives the party a reason to investigate and a reason to plan.
Do not punish the party simply because a rumor is incomplete. A rumor can be wrong, biased, out of date, or exaggerated, but it should still reveal something useful when the party investigates. Perhaps the settlement has no medicine but does have a mechanic. Perhaps the road is watched, but the watchers are asking for help. The party's choice should create information even when it does not produce the hoped-for reward.
Make encounters consequences, not interruptions
An encounter works when it connects to the party's movement, current needs, or past choices. It does not have to be a fight. It can be a traveler, a damaged vehicle, a disputed crossing, a weather problem, a signal, a resource opportunity, or evidence that another group has noticed the party.
| After the encounter, what changed? | Good result |
|---|---|
| Information | The party gains a lead, warning, map correction, or question. |
| Resources | It spends, earns, finds, trades, or damages something that matters. |
| Relationship | A group now trusts, fears, needs, remembers, or seeks the party. |
| Route | A path opens, closes, becomes safer, or becomes more dangerous. |
| Personal stake | A character's background, dream, or moral code now matters. |
If the answer is "nothing," the scene may not need table time. Describe the travel color, then move to the next meaningful choice. For ongoing local powers, use the factions section of the setting guide, and for running the meetings themselves, its encounters section. A group that meets the party should have a need and a memory instead of vanishing when the scene ends.
Camp is a decision point, not an automatic reset
Making camp asks where the party will spend one of its most vulnerable periods. A good camp scene can be brief but should establish the stakes:
- Why is this place better than the alternatives?
- Who prepares shelter, food, equipment, or watch?
- What signs suggest that someone else uses the area?
- What does the party do if it must leave quickly?
- What will be different in the morning if the camp succeeds?
The answer may be as simple as "we stop early near water because the vehicle needs attention." That is enough to create future material: the repair might work, a traveler might arrive, weather might change, or the party might learn it has chosen someone else's fishing spot.
Avoid treating every camp as an ambush roll. A secure night, a useful conversation, or a quiet recovery is a meaningful outcome. Tension comes from uncertainty and tradeoffs rather than from denying rest at every opportunity.
Use personal goals to guide the map
Twilight: 2000 characters have lives beyond the party's supply list. Their relationships, beliefs, dreams, and moral lines can turn a map location into something personal. A rumor of a refugee camp matters differently to a character searching for family. A working radio matters differently to someone who still hopes to contact home. A dangerous detour may test a character's promise never to abandon strangers.
| Player prompt | Campaign benefit |
|---|---|
| What place are you still hoping to reach? | Creates a personal destination. |
| What kind of person would you stop to help? | Defines a moral pressure. |
| What resource reminds you of your old life? | Gives trade and salvage emotional weight. |
| What rumor would you have trouble ignoring? | Creates an optional hook without railroading. |
| What would make you refuse the quickest route? | Establishes a meaningful boundary. |
The Referee does not need to force each answer into the next session. Keep them available. When the party meets a related choice, the open world becomes personal without becoming scripted.
A one-page hex-crawl session prep
For Referees, a compact prep sheet is enough:
- Note the party's current location, supplies, condition, and vehicle state.
- Prepare two or three nearby leads with clear player-facing information.
- Write one terrain consequence for likely routes.
- Write one local group or person who could react to the party.
- Note one changing condition: weather, route damage, scarcity, a rumor, or faction pressure.
- Review one player goal that could matter if the group chooses that direction.
That supports a responsive session without mapping out a plot. The players choose the route; the world supplies context and consequences.
Common map and hex-crawl mistakes
Treating the travel map as a board game with no fiction. Every move should connect to terrain, resources, people, or a goal. If a hex changes nothing, summarize it and move on.
Giving the party no reason to move. An open world needs information. Offer multiple leads, not a blank map and an expectation that players invent the campaign alone.
Withholding route information until it is too late. Players need visible facts and trustworthy uncertainty before they decide. Surprise them with consequences, not with information their characters should have had.
Turning every shift into an accounting exercise. Track what creates a decision. Summarize routine travel and linger when a task, resource, route, or relationship is at stake.
Turning every encounter into a fight or a full tactical map. Encounters should create information and choices, and precise maps belong where precision adds choices. Keep the scene in theater of the mind when it does not.
Making battle maps sterile arenas. Add exits, cover, civilians, vehicles, terrain, weather, and reasons not to shoot. Tactical choices get more interesting when the environment matters.
Invalidating careful planning. Let preparation earn benefits. A surprise can still occur, but it should not erase information the party reasonably gathered or choices it thoughtfully made.
Continue exploring travel
Return to the Setting and Lore hub for the campaign context behind the map. The survival and resources guide covers the daily travel cycle and the resource pressures that make every shift count, while the vehicles and chases guide helps the party plan around transport, fuel, and repairs.
Where To Go From Here
Maps are only half of travel. The Survival Guide supplies the other half: the Shift budget, food, water, fuel, and weather that decide whether the route you drew is one the party can actually walk. When the route is driven rather than marched, the Vehicles Guide covers fuel math, crew tasks, cargo, and the per-shift Driving roll. For the places on the map, who holds them and why they matter, go back up to the Setting and Lore Guide.
Source Scope
This is a high-level guide to using Twilight: 2000 map scales, making player-facing travel decisions, and running the open-world hex-crawl structure. It does not reproduce official maps, map keys, terrain tables, travel tables, event tables, encounter or rumor lists, scenario layouts, city or keyed locations, detailed travel procedures, or Referee-only material. Consult the official Player's Manual and Referee's Manual for those materials.


