RULEBOOK

Creating Locations

A location is not a description. It is a node — a place where something can happen, filled with people who want things. The ones your players remember are never remembered for their walls. They are remembered for who was in them and what was at stake.

The map says "trading post" and "temple" and "waystation." That tells you where things are. It does not tell you why anyone would care. That comes from what is happening inside.

What a Location Is For

Every location is for something. It is somewhere to meet people. Somewhere decisions get made. Somewhere the world shows its face.

Ask yourself: what does this place do for the story? A tavern can be a tavern — that is fine. Set dressing is fine. But your prepped, named, ready-to-run locations should be doing work. They should be somewhere the players want to go back to, or cannot afford to avoid.

A location with no answer to that question is furniture. Give it a function, or save it for background.

The Three-Question Location

Answer three questions and you have a location ready to run.

Who lives here? Not a demographic. A handful of specific people with specific faces. The nervous one. The patient one. The one who has been here too long.

What do they want? Right now, this week, in this place. Not an abstract goal — a concrete desire with a direction.

What is wrong right now? Something is always wrong somewhere. That "wrong" is the reason the players will care. Without it, you have a place. With it, you have a scene.

Three sentences. Five minutes of prep. A location ready to run.

The Roadside Temple. A small temple on a quiet road. Three people: the priest (wants his quarterly stipend to arrive — the donation box has been empty for two months and the order is asking questions), the traveling scholar (wants access to the old records stored in the back room, but the priest keeps stalling with polite excuses), and the local widow (wants the priest to bless her husband's grave — he keeps saying "tomorrow, tomorrow").

What is wrong: the priest is hiding something in the back room and it is consuming all of his attention. The records the scholar wants to read would reveal what it is. The widow's husband was the one who put it there before he died.

Three wants, three doors into the same secret. The players can pull any thread.

You do not need more than that. The players will generate the rest.

Locations as Anchors

Prep Philosophy introduced the phrase "anchors, not rails." Locations are the purest form of anchor.

A well-built location can travel. The smuggler's waystation you wrote for the coast can be a smuggler's waystation on the river. The tense temple you built for one city can appear in another. The people make the place — and if the people are specific enough, the place will work anywhere the story needs it.

This means location prep compounds. The Crossed Anchor does not disappear when the players leave it behind. It waits. It moves if it needs to. The keeper still wants the debt paid. The supplier still wants answers. That tension travels.

Prep that travels is prep that compounds. Every location you build adds to a toolkit you will use for years.

Connecting Locations

A travel-time map tells players how long it takes to get somewhere. That is useful. But an information map — who knows what, and where — is how a world feels alive.

NPCs in one location should know things about another. The innkeeper has a cousin two towns over who owes money to someone the players met last session. The priest knows the merchant's shipment is late. The blacksmith heard the bandit camp moved.

Players navigate by following threads, not by measuring distance. When they walk into a room and the person behind the counter says "you're the ones who were asking about Varro — you should talk to the woman at the north mill," that is the world acknowledging that things are connected. It does not require you to have planned that connection from the start. It requires that each of your locations has people who pay attention to the world around them.

Give your NPCs one piece of knowledge about somewhere else. That one detail becomes a bridge. Bridges are how players find their way.

Signature Details

One sensory hook per location. Pick it before the players arrive and use it every time they come back.

A signature detail is a sensory thing the players can perceive, attached to a sliver of story that nobody has explained yet. The two halves are what make it stick — the sensory hook gets their attention, and the implied story keeps it.

  • The ceiling beam above the corner table with three deep parallel gouges running across it. Nobody will explain them. The marks are not new.
  • The keeper's dog, always asleep in the same spot by the fire, with one ear that never stops twitching — even when she is dreaming.
  • A single candle on the altar, always lit, always burned down to the same length. The junior acolyte's only real job is running in every hour to replace it before anyone notices.
  • The innkeeper's limp, worse on cold mornings, and the sword hanging above the fireplace that she will not answer questions about.

A single detail, reused consistently, does more work than a paragraph of description on the first visit. Players latch onto the concrete. They will remember the sword. They will probably not remember the vaulted ceilings.

Specific beats comprehensive. The players fill in the rest.

A location is only a node if there are people inside it worth pulling on. Creating NPCs covers how to build the characters whose wants become the engine of every scene. And locations do not stay static — a plague, a festival, a fire, a change in ownership. In-Game Events covers what happens to locations when the world moves, and why that gives players a reason to return.