Encounter prep

How to Turn a Generated Tavern Into an Encounter

A good tabletop encounter is not just a room with people in it. It has a reason to happen, something that can change, and at least one clear way for the players to push on the situation. ReadyScene gives you the ingredients for that kind of encounter without deciding your rules, difficulty, or outcome for you.

Use this guide after the venue exists

This page is for a generated location that already has a name, atmosphere, people, and a hidden problem but still feels static. If you need the whole session outline, start with the Session Prep Guide. If the players are already waiting, use the shorter GM Improv Checklist.

Start with the encounter's pressure

Before choosing names or details, decide what makes the scene unstable. The pressure might be a debtor hiding in the kitchen, a patron spreading a false rumor, a customs officer watching the door, or a storm keeping everyone inside. A generated hidden problem is often the fastest place to find that pressure.

Once you know the pressure, write it as a table-facing question: who notices the stolen badge, what does the fixer want before closing time, or why is the keeper suddenly refusing old friends? Questions are easier to run than plots because they invite player choices.

Give every important NPC a motive

Generated patrons are strongest when each one wants something simple. One wants safety, one wants money, one wants someone blamed, and one wants the conversation to stop. You do not need a full biography. You need a motive that explains what the NPC does when the characters intervene.

If an NPC feels flat, pair a visible detail with a private reason. A bruised courier may be desperate to sell a route map. A cheerful barkeep may be keeping guests loud so nobody hears the cellar door. Small contrasts make scenes feel playable quickly.

Prepare three ways into the scene

A generated venue can support different table entries. Characters might arrive looking for rest, tracking a rumor, following an NPC, or avoiding trouble elsewhere. Keep three openings ready so the encounter still works if the party approaches from an unexpected angle.

1. Soft entry: the characters notice atmosphere, gossip, or a request before danger appears.
2. Direct entry: the key NPC approaches them with a problem, warning, or offer.
3. Complication entry: the hidden problem interrupts the room before anyone can settle in.

Add clues, not conclusions

For mystery, intrigue, and faction play, use the generator to create signs that something is wrong, then let the table decide what those signs mean. A half-burned ledger, too-clean boots, a sealed bottle, or a nervous regular can all point toward the same hidden problem without forcing a single path.

Try to prepare at least two clues for any fact the characters need. If one clue is missed, ignored, or interpreted strangely, the scene still has another route forward.

Know how the encounter can end

Social encounters end more smoothly when you know what changes the room. The characters might earn trust, expose a lie, buy time, start a chase, make an enemy, or turn the venue into a recurring safe place. You do not need to predict which ending happens, but you should know what the scene can hand to the next session.

After play, save only the facts that became true at the table. The generated draft is a starting point; the campaign version is whatever survived contact with the players.

Worked example: turn a generated cantina into a decision

Suppose the generator gives you the Relay House, a crowded transit cantina, a careful keeper named Olan, a stranded courier, and a hidden problem involving a copied travel permit. Do not add a larger plot. Connect those pieces so the players can change the room now.

The encounter is complete because it has a clock, competing motives, readable evidence, responsive NPC behavior, and several exits. System-specific checks or combat rules can be added only if the table calls for them.

Use this frame in a fantasy tavern: the fantasy tavern session workflow connects a complete example, the preselected generator, one rumor, one recurring NPC, this encounter frame, and the final prep-sheet or Markdown export.

Next reads