Random Encounters 5e: How to Make Them Matter (Not Just Filler Fights)

You’ve rolled on a table, deployed three wolves, and watched the energy leave the room. Nothing changed except hit point totals and real time. Random encounters aren’t a failure of old-school play; they’re pacing tools. Used well, they’re how travel stops being a fade-cut and starts being a place.

Treat every encounter, even a rolled one, like a scene with a job. This guide covers how often to roll, how to build a table that fits your campaign, how to run the result, and a worked travel day.


How the rules frame random encounters

The 2014 Dungeon Master’s Guide treats random encounters as an optional tool. The suggested method:

That’s a solid default. A roll of 18+ is a 15% chance per check, so if you check three times a day, the party meets something on roughly 4 travel days out of 10. Raise or lower the interval to match how dangerous you want the region to feel.


Rule of thumb: one job per encounter

Before you run it, name one outcome it’s allowed to push:

If you can’t name the job, don’t run the encounter, or rewrite it until it has one.


Build your own table in 15 minutes

Generic tables give generic results. A short custom table for each region beats a long one from a book.

  1. List three things that live or move here: a faction, a predator, something weird.
  2. Write 6 to 8 entries using those three things in different situations: hunting, fleeing, trading, dead, arguing.
  3. Make at least half of them non-combat.
  4. Add one entry that ties to the main plot.
  5. Note a job next to each entry (drain, reveal, foreshadow, map, choice).

Example: the Ashwood Forest (d8)

d8EncounterJob
1Three hungry wolves stalking the party’s pack muleDrain
2Pale Hand cultists burying something at a crossroadsForeshadow
3A woodcutter with a broken leg asks for help to his villageChoice
4The old stone bridge has collapsed; a detour costs half a dayMap
5A burned campsite with a half-written letterReveal
6Fog rolls in; navigation becomes difficult until morningDrain
7An owlbear’s territory, marked by gouged treesChoice
8Elf hunters who demand a toll or a favorChoice

When you need stats for the fights on the list, the free Encounter Generator gives you a balanced group in seconds. When the woodcutter or the elf hunters need a personality, NPC in a Hurry gives you a want, a mannerism and a secret.


Rotate encounter types, not just combat

Combat is loudest, but it’s only one instrument:

You’ll travel more often in your campaign if every hour isn’t initiative.


When you do fight, make motive and distance quick

Three questions on a notecard beat a novel:

  1. What do they want? Food, territory, coin, orders, panic.
  2. What will make them stop? Low hit points, easier prey, negotiation, a display of power.
  3. What clue do they carry if players loot or question them?

Decide the starting distance and who notices first. Compare the party’s passive Perception with the creatures’ Stealth, or the reverse if the party is sneaking. Starting an encounter at 120 feet with both sides aware gives players the option to talk, hide or run, which is often more interesting than an ambush.


Worked example: two days through the Ashwood

The party (four level-4 characters) travels two days through the forest. You check three times per day: morning, afternoon and night.

Three encounters, one fight, and the “random” results built a small story because the table was written for this campaign.


Tie “random” to things the players already know

The fastest way to banish filler is continuity:

Random should feel inevitable, like the world was listening.


Common pitfalls

For the travel rules themselves, including pace and navigation, read travel pace and overland journeys. For night travel, darkvision and light matters more than most players expect.

Frequently asked questions

How often should you roll for random encounters in 5e?

The 2014 Dungeon Master's Guide suggests choosing a regular interval, such as every hour or every few hours depending on how dangerous the area is, and rolling a d20, with an encounter on 18 or higher. Adjust the interval to the region and the pace of your game.

Are random encounters a waste of time?

Only when nothing changes because of them. An encounter that drains resources, reveals a clue or forces a choice makes travel feel real and dangerous instead of a fade-to-black.

Do random encounters have to be combat?

No. Travelers, patrols, weather, tracks, abandoned camps and strange landmarks all count. Mixing in non-combat entries keeps travel varied and saves table time.

Should random encounters be balanced to the party?

Mostly yes, but a dangerous encounter the party can avoid or flee is fair if they get a clear warning. Keep most entries at easy to medium difficulty so travel drains resources without stalling the session.

Can players avoid a random encounter?

Often they should be able to. Stealth, a good watch rotation, or simply taking another route gives players agency. Use the party's passive Perception and the creatures' Stealth to decide who notices whom first.

Useful at the table

As an Amazon Associate we earn from qualifying purchases, at no extra cost to you. More about this.

← All articles

Free: Class Quick Reference

All 12 Player's Handbook classes on one printable page each: levels 1 to 5, subclasses, a standard array and the mistakes new players make. Leave your email and the 12-page PDF is yours, plus the occasional new guide.