D&D Encounter Building Tips for New GMs: From Boring Fights to Memorable Moments

You did everything right. You picked a cool monster. You set the scene. You rolled initiative. And then your four level-3 players deleted your solo CR 5 creature in two rounds because they all went first and the paladin crit with a smite.

Or maybe the opposite: you threw four ogres at the party because the math said "hard encounter," and now two characters are making death saves in round one while the remaining two are doing mental math on whether running is an option.

Both of these are the same problem. You're building encounters by looking at numbers when you should be building them by understanding how combat actually works.

The good news: encounter building isn't complicated once you understand a few core principles. You don't need to be Matt Mercer. You don't need a degree in game design. You need to understand action economy, use terrain like it matters, pace your session so resources actually matter, and mix your enemies so players have to think instead of just rolling damage.

Here's how.

Action Economy: The One Rule That Explains Everything

If you learn one thing from this guide, let it be this: the side with more actions usually wins.

Action economy is the total number of things each side can do per round. Your four-player party gets four actions, four bonus actions, four reactions, and potentially four concentration spells running. That's a lot of output.

Now imagine they're fighting one big monster. That monster gets one action (maybe with multiattack), one legendary action if it's fancy, and one reaction. The party gets roughly four times as many chances to deal damage, apply conditions, and control the battlefield. The monster's enormous hit point pool doesn't matter if it gets stunned in round one and never takes a turn.

This is why solo bosses feel anticlimactic and why five goblins are scarier than their CR suggests.

How to Use This

Rule of thumb: aim for a roughly even number of actions on each side. If the party has four characters, consider:

• 4-6 weaker enemies for a standard fight
• 2-3 moderate enemies + 1-2 minions for a focused fight
• 1 strong enemy + 3-4 minions for a boss fight

The minions don't need to be threatening on their own. They exist to eat actions. The rogue has to deal with the two skeleton archers instead of focusing fire on the necromancer. The wizard has to decide between fireballing the minion cluster or counterspelling the boss.

The Minion Principle

Minions in 4th Edition D&D had 1 hit point but dealt normal damage. Fifth Edition doesn't have an official minion rule, but you can fake it:

• Take any low-CR creature and give it 1 hit point
• Keep its attack bonus and damage the same
• Any damage kills it — no need to track individual HP
• They still threaten opportunity attacks, flanking, and action denial

Four goblin minions with a hobgoblin captain is a better fight than a single hobgoblin captain with inflated stats. The math is secondary. The tactical puzzle is the point.

Terrain: The Encounter Multiplier Nobody Uses

A fight in an empty room is a math problem. A fight on a collapsing bridge is a story.

Terrain is the most powerful encounter design tool you have, and it costs nothing in terms of monster budget. The exact same group of enemies becomes drastically different depending on where the fight happens.

Terrain That Changes the Fight

Think about terrain in terms of what it forces players to decide:

• Elevation changes — Archers on a cliff have advantage and cover. Melee characters have to spend actions climbing or finding another path. Suddenly "I run up and hit it" requires a plan.
• Difficult terrain — Thick mud, rubble, ice, dense undergrowth. Halved movement means melee fighters can't reach enemies in one round. Ranged characters and spellcasters gain relative power.
• Cover — Pillars, walls, overturned wagons, trees. Enemies that use cover force players to reposition. Cover also protects players from that archer on the cliff.
• Hazards — A pool of acid in the center of the room. A campfire that can be kicked into spilled oil. A frozen lake that cracks under weight. Hazards create zones that both sides have to navigate around — or push enemies into.
• Choke points — A narrow doorway means only one character can engage at a time. Powerful for creating tactical decisions about who goes first and who defends.

The Three-Feature Rule

Before every combat encounter, write down three interactive features of the environment:

1. Something that provides cover or high ground
2. Something that creates movement constraints
3. Something that can be used as a weapon or tool

Example: A fight in an old warehouse. The features are (1) stacked crates that provide half cover and can be climbed for elevation, (2) narrow aisles between crate rows that limit movement, and (3) a heavy chain attached to a cargo hoist that a player could swing on or drop on an enemy.

That warehouse fight is now more interesting than the same enemies in an open field, and you didn't change a single stat block.

Encounter Pacing: Why the Adventuring Day Matters

The Dungeon Master's Guide assumes six to eight encounters per adventuring day. Almost nobody runs that many. Most tables do one to three combats per session and call it a long rest.

This creates a pacing problem that breaks encounter balance. Here's why.

The Nova Problem

When the party knows they'll only face one fight before resting, they dump everything in round one. The wizard opens with their highest-level spell. The paladin burns every smite slot. The fighter action surges immediately. The cleric uses Spirit Guardians and their best healing.

Against a single encounter, no matter how deadly on paper, a fully-resourced party unloading everything has a massive advantage. That "deadly" encounter becomes "hard" or even "medium" because the difficulty system assumes partially drained resources.

How to Fix It

You have three options:

Option 1: Run more encounters. Two smaller fights before the big one drain spell slots and hit points, making the boss fight feel appropriately tense. These don't have to be combats — a trap gauntlet, a collapsing tunnel that costs healing, or even a well-designed puzzle (though beware the common reasons D&D puzzles fail) also works.

Option 2: Use the gritty realism rest variant. Short rests take 8 hours, long rests take a week. This stretches the adventuring day across multiple sessions without changing encounter frequency. It's a bigger rules change but works beautifully for low-magic or survival campaigns.

Option 3: Add resource pressure within the encounter. Multiple waves of enemies. A fight that lasts enough rounds for concentration spells to get tested. An objective that can't be accomplished in one round of nova damage. If the fight lasts six rounds instead of two, the party has to ration.

Mixing Enemy Types: The Art of the Encounter Roster

A fight against four identical enemies is a math problem with one solution: focus fire on one at a time. A fight against four different enemies is a puzzle with multiple solutions.

The Encounter Roster

Think of your enemy group like a party. They should have different roles:

• Bruiser — High HP, high damage, slow. Forces the party to deal with it or get hit hard. Ogres, trolls, earth elementals.
• Skirmisher — Fast, moderate damage, low HP. Flanks, hit-and-run, disrupts the back line. Goblins, wolves, shadows.
• Controller — Uses spells or abilities to restrict movement, impose conditions, or buff allies. Spellcasters, beholders, hags.
• Artillery — Ranged damage dealer. Stays behind cover or at elevation. Archers, mages, fire elementals.
• Minion — Low threat individually but consumes party actions. Any weak creature in numbers.

A goblin fight with just six goblins is straightforward. But a goblin fight with two goblin archers on a ledge (artillery), three goblin melee fighters (skirmishers), a goblin shaman casting Fog Cloud (controller), and a bugbear waiting in ambush (bruiser)? That's an encounter that makes players talk to each other and coordinate.

Example Encounters by Tier

Tier 1 (levels 1-4): A bandit ambush on the road. Two bandits with crossbows behind a fallen wagon (artillery + cover). Three bandits with swords blocking the path (skirmishers). A bandit captain (bruiser) who shouts commands and grants advantage on attacks. The bandits flee if the captain goes down — giving the party a clear tactical goal.

Tier 2 (levels 5-10): A cultist ritual in a ruined temple. Two cult fanatics channeling a spell at the altar (controllers — the ritual completes in five rounds). Four cultists with daggers (minions). A summoned demon that the ritual has partially materialized (bruiser — it gets stronger each round the ritual continues). The party has to decide: fight the demon or stop the ritual?

Tier 3 (levels 11-16): An adult dragon defending its lair. The dragon itself uses breath weapon and flight (artillery + bruiser). Four kobold dragonshields block the narrow tunnel entrance (skirmishers + choke point). Lair actions cause stalactites to fall and lava to shift. The dragon retreats to a high ledge when bloodied, forcing ranged engagement.

Using the Encounter Calculator (Without Trusting It Blindly)

The encounter difficulty math in the DMG gives you a starting point, not an answer. Here's how to use our Encounter Calculator effectively:

Step 1: Get Your Baseline

Enter your party size and level. The calculator gives you XP thresholds for easy, medium, hard, and deadly encounters. These thresholds assume a standard party with no magic items, no multiclassing, and average tactical play. If you want to understand where those thresholds come from, our XP calculation guide covers the underlying math.

Step 2: Adjust for Your Table

Your party is not standard. Adjust the target difficulty based on:

• Experienced or optimized players? Bump up one difficulty tier. Your level-5 party with a paladin/warlock multiclass hits way above their weight.
• New players? Bump down one tier. They won't use their abilities optimally and will make tactical mistakes. Setting appropriate DCs can also help you calibrate difficulty for less experienced groups.
• Magic items? A party loaded with +1 weapons and Cloaks of Protection is effectively a level or two higher.
• Party composition? A party with no healer or no frontliner is more fragile than the math suggests.

Step 3: Pick Monsters, Then Add Terrain

Choose enemies that create the action economy and role diversity described above. Then design the terrain to complement the encounter's tactical story.

Step 4: Playtest in Your Head

Run the first two rounds mentally. Ask:

• Can the party reach the enemies in round one, or do they have to spend actions moving?
• What does each enemy do on its turn? Is there variety?
• What happens if the party focuses fire on the biggest threat first?
• Is there a moment where the players have to make a hard choice?

If you can't picture an interesting decision, adjust the encounter.

Common Encounter Building Mistakes (and How to Fix Them)

Mistake 1: The Solo Monster

You build one big monster fight. The party stuns it in round one and it never gets a turn. Fix: add minions or use legendary/lair actions.

Mistake 2: The Symmetrical Fight

Four bandits vs. four players. Both sides have the same action economy and similar power. The fight is a coin flip that takes 45 minutes. Fix: asymmetric encounters where one side has a terrain advantage, a time constraint, or a different objective.

Mistake 3: The Death Box

An encounter that's accidentally way too hard because you forgot to account for action economy, terrain disadvantage, or surprise rounds against the party. Fix: know your players' resources before the fight. If they're already spent from a previous encounter, dial back. Keep a "retreat valve" — a way the enemies might flee, negotiate, or change tactics if the fight is going badly for either side.

Mistake 4: No Retreat Condition

Every intelligent enemy should have a reason to stop fighting. Bandits surrender. Wolves flee. Even demons might withdraw to regroup. Fights to the death are rare in reality and should be rare in your game. When enemies retreat, it also creates future story hooks.

Mistake 5: Static Encounters

The enemies stand in a room and wait for the party to kick down the door. They don't patrol, don't have lookouts, don't react to noise from the last fight. Fix: think about what the enemies were doing before the fight started. Patrols, guard rotations, and alerted enemies who've prepared defenses all make encounters feel alive.

Putting It All Together: A Complete Encounter Design Walkthrough

Let's design an encounter from scratch for a party of four level-4 characters.

Step 1: The Situation. The party needs to rescue a kidnapped merchant from a bandit camp in a quarry.

Step 2: The Calculator. A hard encounter for four level-4 characters is roughly 1,000-1,500 adjusted XP. We'll aim for the middle.

Step 3: The Roster.

• 1 Bandit Captain (CR 2, 450 XP) — the leader, bruiser role
• 2 Bandits (CR 1/8, 25 XP each) — skirmishers guarding the quarry rim
• 3 Thugs (CR 1/2, 100 XP each) — bruiser minions around the campfire
• 1 Scout (CR 1/2, 100 XP) — artillery, perched on a high ledge with a longbow

Adjusted XP with the multiplier for 7 enemies: roughly 1,350. Hard encounter. Perfect.

Step 4: The Terrain. The quarry has:

1. High ground — the scout's ledge (20 feet up, half cover from below)
2. Movement constraint — loose gravel slopes (difficult terrain to climb into or out of the quarry)
3. Interactive element — mining carts on a rail track above the quarry that can be released to roll down the slope

Step 5: The Complications.

• The merchant is tied up near the campfire. If the fight goes badly for the bandits, the captain threatens to kill the hostage.
• The scout rings a bell after one round, alerting a second patrol (2 more bandits) that arrives in 3 rounds from the north trail.
• The bandit captain offers to negotiate if reduced to half HP — she'll trade the merchant for safe passage.

Step 6: The Decision Points.

• Do the players sneak in or assault directly?
• Do they take out the scout first to prevent the alarm?
• If the alarm sounds, do they rush to finish the fight or set up a defensive position?
• Do they negotiate with the captain or fight to the end?

This encounter uses action economy (7 vs. 4, but the enemies are weaker individually), terrain (elevation, difficult terrain, interactive carts), pacing (reinforcement timer), and mixed enemy types (bruiser captain, skirmisher bandits, artillery scout). And it wasn't hard to build — just methodical.

The Quick-Start Checklist

Before your next session, run through this for every combat encounter:

1. Action economy — How many actions does each side get? If one side has double, adjust.
2. Enemy variety — Do you have at least two different roles in the enemy group?
3. Terrain features — Can you name three things in the environment players can interact with?
4. Pacing — Is the party fresh or drained? Adjust difficulty accordingly.
5. Retreat condition — Why would the enemies stop fighting?
6. Player decisions — Is there at least one moment where the players have to choose between two valid options?

If you can check all six, you've got a good encounter. If you can't, pick the weakest area and improve it. You don't need all six to be perfect — you need zero of them to be absent.

Further Reading

Building better encounters is one piece of becoming a confident GM. These guides cover the rest:

• How to Make D&D Combat More Interesting — Once you've built the encounter, here's how to run it at the table.
• D&D Campaign Ideas for New GMs — Twelve campaign premises with session 1 outlines.
• How to Be a Better DM — The broader toolkit for running great games.
• How to Run a One-Shot — Encounter pacing for single-session adventures.
• Session Zero Checklist — Set expectations before the dice hit the table.
• Random Encounter Generator — Need an encounter idea right now? Let the generator surprise you.
• Encounter Calculator — Crunch the numbers for your next fight.