Encounter Builder
Encounter toolset framework for DMs to structure scene setup, participant roles, tactical behavior, and scaling before play. Define premise, difficulty, and participants; add setup...
Encounter toolsets help a DM turn a scene idea into a table-ready encounter: who is present, why the scene matters, how the opposition behaves, how to scale it, and what changes after the dice stop. Treat the saved encounter as a reusable prep object that can feed the DM screen, combat setup, scene generation, and recap context.
Start from the campaign DM screen at `/campaigns/{campaignId}/dm-screen`, or use the general DM toolbox at `/dm-screen` when you are drafting outside a specific campaign.
1. Define the table job
Pick one job for the encounter before filling in numbers. A good encounter creates pressure the party can act on: stop a ritual, survive an ambush, extract a witness, hold a bridge, bargain under threat, or learn what the enemy wants.
| Field | What the DM needs |
|---|---|
| Premise | One sentence that explains why this scene is happening now. |
| Difficulty | The expected pressure for the current party size and level. |
| Participants | Monster, NPC, hazard, or environment entries with counts and roles. |
| Setup | Read-aloud or staging text that starts play quickly. |
| Tactics | How the opposition behaves when the party disrupts the plan. |
| Scaling | How to adjust for smaller, larger, weaker, or stronger parties. |
| Aftermath | The clue, consequence, reward, or complication that points forward. |
2. Build the saved entry
- Choose the campaign, party level, and intended difficulty.
- Add participants with clear roles such as boss, elite, minion, support, or environment.
- Write setup text the DM can read or paraphrase at the table.
- Write tactics in behavior terms, not stat-block reminders.
- Add scaling notes before the encounter is used live.
- Add aftermath hooks so the scene connects to the next campaign beat.
3. Use examples as templates
Graveyard at Midnight is a compact low-level example: simple participant roles, obvious pressure, and aftermath that reveals a larger cult thread.
Glacier Cult Guardians is a higher-level example: a boss, chained battlefield pressure, escalation if the party changes the state, and evidence that connects the fight to a broader quest.
When building a new encounter, copy the shape of the example that matches the DM's table need, then replace the participants, pressure, and aftermath. Keep rule text in monster or NPC entries; keep scene operation here.