All posts

Guides

How to Make Random Encounter Tables

Learn how to make random encounter tables for D&D: weight results, mix in non-combat entries, avoid repeats, and link each roll to the creature you'll run.

By Mythical AtlasLast updated

To make a random encounter table, pick one place and level range, list 8 to 12 things the party could run into there, and give the common ones more weight than the rare ones. Mix in encounters that aren't fights, give each entry a reason to be there, and cross off or reroll results the party has already seen. That's the whole method, and it works whether you play D&D 5e, Pathfinder or an old-school game.

This guide walks through each step. You'll learn how to weight entries, how to keep results from repeating, and how to link each result to the creature you'll actually run, so a roll at the table turns into an encounter in seconds instead of minutes.

What a good random encounter table does

A random encounter table isn't just a monster list. It's a quick way to make a place feel alive. When it works, it does three jobs:

  • It tells players something about the area. Goblin scouts on the road say "the goblins are getting bolder." Wolves at the edge of the forest say "this is wild country."
  • It adds pressure. The chance of something showing up makes long rests, slow searches and wandering off the path feel risky.
  • It saves you when players go off-script. If the party heads somewhere you didn't plan for, a table gives you something ready to run.

A table that only produces "2d4 orcs attack" does none of this well. The steps below fix that.

Step 1: Scope the table to one place

One table per region or situation works better than one giant table for the whole world. "The Old King's Road," "Sewers under the city" and "Night in the haunted marsh" each deserve their own list.

Keep two things in mind when scoping:

  • Level range. Encounters should suit the party now, with a few that are clearly easier and one or two they should probably avoid.
  • Tone. A busy trade road and a cursed ruin need very different entries, even at the same level.

Step 2: Write 8 to 12 entries, and not all combat

Fewer than eight entries and the table repeats too quickly. More than about twelve and the table gets hard to keep consistent. Aim for a mix along these lines:

Kind of entryExampleWhy it helps
Common threatA patrol of bandits demanding a tollShows who runs the area
WildlifeA bear guarding a fresh killDanger that can be avoided
Traveler or NPCA lost pilgrim with a rumorRoleplay and information
Sign or clueBurned wagon, tracks leading off-roadHints at a bigger story
EnvironmentA storm, a washed-out bridgePressure without a fight
Rare dangerA young dragon hunting overheadA memorable, rare moment

Give every entry a short "what they want." Bandits want the toll, not a fight to the death. A bear wants its meal. Once you know what a creature wants, the party has options other than combat, and the encounter writes itself.

Step 3: Weight the results

Not every result should be equally likely. Patrols on a busy road should show up far more often than the dragon. There are two common ways to handle this.

Weighted entries on a single die

Give common entries a bigger share of the range. On a d20 table, the bandit patrol might cover 1–6, wildlife 7–10, travelers 11–14, signs 15–17, weather 18–19 and the dragon only 20. You decide exactly how likely each result is, and it's easy to change later.

Bell-curve tables with two dice

Roll two dice and add them, such as 2d6. Middle totals like 6, 7 and 8 come up far more often than 2 or 12. Put the everyday encounters in the middle and the rare or dangerous ones at the edges. It feels natural, but it's harder to fine-tune than a weighted single die.

Either way, a good rule of thumb is that the most common result should come up roughly a quarter to a third of the time, and the rarest about one roll in twenty or less.

Step 4: Avoid repeats

Nothing deflates a table faster than meeting the same wolf pack three trips in a row. A few ways to keep it fresh:

  • Cross results off. Once the party has dealt with the bandit patrol, mark it used and reroll if it comes up again.
  • Escalate instead of repeating. If a result repeats, make it the next step in a story: the bandits come back with a leader, or the bear's tracks lead to its den.
  • Replace used entries. Swap a used entry for something that reflects what changed. If the party cleared the bandits, maybe a merchant caravan feels safe to travel now.
  • Roll twice. Combine two results into one scene, such as a lost pilgrim fleeing a bear. It turns two plain results into something more interesting.

Step 5: Link each result to what you'll run

The slowest part of a random encounter isn't the roll. It's what comes after, when you dig through a book for the stat block. Before the session, note where each result's details live: a page number, a stat block, or the NPC's name and motive. For non-combat entries, write one line of what happens and one line of what the party can learn.

Step 6: Decide when to roll

A table is only as good as your rule for using it. Pick a simple trigger and stick to it, for example a roll per day of travel, per long rest in a dangerous area, or whenever the party makes a lot of noise. Many GMs also roll a separate check first to decide whether anything happens at all. You can also roll ahead of time during prep and pick the results you like best. That's not cheating; it's using the table as an idea generator.

Random encounter tables in Mythical Atlas

If you'd rather not keep tables on paper or in a spreadsheet, the Codex in Mythical Atlas is built for this kind of list.

  • Weighted rolls. Each row can have a roll weight. A row with weight 2 comes up twice as often as a row with the default weight of 1, so you set likelihood directly instead of working out dice ranges.
  • Avoid repeats. Mark rows as used and turn on "skip rows already marked used," or use "no repeats until every row has come up" so nothing repeats until the whole list has been rolled.
  • Combine tables. Select several tables and roll once, with an option to give every table equal odds. That's handy for pairing an encounter table with a weather or complication table.
  • Link results to creatures. Any row can link to a Glossary creature or a quest, so the result points straight to the stat block. Glossary entries can be private, so you can prepare monsters the party hasn't met yet.
  • Private by default. Codex tables stay private unless you turn on sharing, so players won't see what's lurking.
  • A head start. The Encounter Prep template sets up a starter group, and you can import an existing table from a CSV file.

Once a fight starts, the GM Glossary Roller on the Dice Roller rolls ability checks and saving throws straight from a Glossary creature's stat block. For more on keeping tables, NPCs and quests tidy between sessions, see our guide on how to organize a D&D campaign.

Quick checklist

  • One table per region or situation
  • 8 to 12 entries, with a mix of combat, travelers, clues and environment
  • A motive for every creature or NPC
  • Common results weighted up, rare ones weighted down
  • A plan for repeats: cross off, escalate or replace
  • Stat blocks or notes linked to every result
  • A clear rule for when to roll

Start with a single table for the region your party is in right now. After a session or two you'll see which entries land and which ones fall flat, and you can tune it from there.