Intro
Sometimes we design a combat encounter, and we think it is good. It is going to be fun. And then thirty minutes in — maybe an hour in — we start to realise we made some mistakes along the way.
Because here is the question: how many times can your players fight monsters to the death and have it still be interesting?
Sometimes the stakes of the plot carry it. But think about it honestly. When was the last time you ran an encounter that was about something other than “kill the monster”?
If it was last session, fantastic. Genuinely, that is great. But if you are sitting there going oh God, I cannot even remember — this one is for you.
Secondary objectives enhance D&D combat to an exponential degree, and I am going to give you ten of them. Ten different types of secondary objective you can drop into your encounters to make combat more compelling, more engaging, and just plain better.
Let us count down.
10. Rescue Missions
Task your players with rescuing an NPC or retrieving an item during the fight. It adds urgency, and potentially a moral dilemma on top.
My favourite version of this: instead of sending the party to wipe out the goblin camp that might raid the village — which is a fine consequence, and sometimes that is enough — the goblins have abducted the blacksmith. Now the party has to save the blacksmith and deal with the goblins.
And you can push it further. It is not “kill the goblins, then untie him.” The goblins are planning to sacrifice him. Now there is a dilemma, a time frame, and a fire lit under the party.
9. Protective Actions
Assign an area or object the players have to defend against enemy forces. A magical artifact. A gate. A besieged city. You are essentially turning the encounter into a tower defence game.
Here is the important part, and it is the part DMs get wrong.
We all joke that D&D players spend three quarters of a session planning, and then in the last quarter something goes wrong on step one and the plan goes out the window and they have to improvise. That is great. I love improvisation.
But in this scenario — let the players set up defences, and let those defences work.
When you let players succeed, they do not just feel good, they feel heroic. If they defend the city, if they establish positions, if they set traps and the traps actually function and the encounter gets easier as a result — as the DM you might be tempted to think well, that kind of sucks, my encounter got trivialised.
No. That is the whole point. That is completely different from the sorcerer casting chain lightning and vaporising four enemies instantaneously. This is the players making a plan and executing it well. Let them have it.
8. Environmental Challenges
Use the environment to add complexity. This is one of my favourites.
Fighting on unstable ground. It is a world full of magic — there are earthquakes that have left this one area with constantly shifting plateaus and platforms. Enemies fall through the cracks, and if the players do not keep moving, so do they.
Or: the party is in a dungeon and fails a puzzle on the first attempt. The room starts filling with water, and undead begin forming around the puzzle. Now they either solve the puzzle or swim for the exit — while fighting the undead.
The difference is layers. Instead of you failed the puzzle, now kill the undead, whack whack whack, you have an encounter with thickness to it. Like a good layered bean dip. You want your players under pressure, because the moment they overcome it, that feeling is fantastic.
7. Time-Sensitive Goals
I love this one, and I have used it with varying degrees of effectiveness.
I do not mean “you have to do this before the week is out.” I mean set a real timer. Thirty minutes of actual, real-world time to resolve this situation.
You will watch your players move at a speed you did not know they were capable of. Everyone firing on all cylinders. You genuinely do not realise they can operate at that level until you put that pressure on them.
So introduce a countdown: either a set number of rounds, or a set number of real-life minutes. Both work incredibly well.
Baldur’s Gate 3 uses the round-limit version constantly, and it makes those encounters enormously spicy. The Iron Throne is the great example — four rounds to save as many people as you can. That is such good design. (If you have not played BG3: do it. Thanks. Bye.)
6. Non-Combat Objectives
You are probably saying: but this is supposed to be a secondary objective in combat, what do you mean it is not combat? Relax. The professor will explain.
What I mean is introducing something like a puzzle, or a negotiation with a potential ally, in the middle of a fight.
Here is the scenario. The party is delving into a gnoll camp, and there are a lot of prisoners here — including bandits they recognise from the surrounding region, who could be allies. So they parlay with the person they take to be the bandit leader. And mid-conversation, the gnolls discover them and attack.
Now the gnolls outnumber the party badly. Two options: fight insurmountable odds, or spend their turns talking. Debating. Negotiating. Fight with us. We will let you out, we will let you live, we will make it worth your while.
They agree. The tide turns. The fight shifts in the party’s favour because of a secondary objective, and then it is combat as normal.
But here is the beautiful part: that layer does not end when combat ends. You now have an NPC the party has allied with who is not a good person. A bandit leader who, once they are out of that camp, is going right back to pillaging and robbing. And the party made a deal with them.
Where does that go? I do not know. You tell me. It is your game.
5. Sabotage
The goal here is for the players to discreetly sabotage enemy equipment or disrupt a ritual without being detected.
Here is how I would run the mechanics, because this is where it lives or dies.
Make the map of the camp where the device or the ritual is. Then have only the party roll initiative — not the enemies. Never roll for an enemy near the party. But every so often, move an enemy who is far away: after your turn, John, the bandit on the opposite side of the map moves over here. That adds a layer of change without breaking the stealth.
And let the entire party act as a group on initiative. Let them swap actions back and forth, move together, coordinate. Let them have the feeling of tactically dismantling this camp.
Then, when it goes wrong — and it will, because eventually your fighter-barbarian-paladin friend in plate armour with two tower shields and five hundred pounds of equipment steps on a twig and alerts the entire camp — that is fine.
Because it was never about killing the bandits. It was always about clearing a path to sabotage the ritual, or destroy the artifact, or whatever it is. That was the objective the whole time.
The recommendation on mechanics is simply: give your party a fun way to go about the sabotage. It is still combat, but the power to succeed at the stealth part belongs to them.
4. Escort Missions
If you have ever played a Bethesda game, or an Assassin’s Creed game, or honestly any RPG — you know escort missions can be the absolute worst. There is nothing more miserable than being made to protect something that cannot defend itself, with bad AI and worse pathing, forcing you to change your entire playstyle to babysit something dumber than it should be.
Lucky for you, my good DM friend, I would hope you are smarter than Bethesda’s AI. I really hope so.
So play the NPC smart. My biggest caveat here is: make the escorted NPC comparable to the party. The party is level 10 — the NPC is level 7. They are strong. They are competent. They can handle themselves. They just cannot cross this particular area alone.
Better still, make the party need them. The cleric has a mobile protective shield — something like spirit guardians — that is the only thing keeping the party alive as they cross somewhere like the Shadow-Cursed Lands. Now the party protects the cleric because the cleric is keeping them safe. And the cleric is still a level 7 character with spells to cast; maybe they just cannot hold concentration on anything else.
And if the escort fails
Very important caveat: fail forward.
If the cleric dies, it cannot be well, screw you guys, figure something else out. The cleric dies — struck by an arrow, hit by a bolt of chaos energy, whatever it is — but the party can still grab their staff. They can still channel the magic. It is just significantly harder for the sorcerer to do it than it was for the cleric who owned the thing.
Failure changes the shape of the problem. It does not end the story.
3. Gathering Intel
Make extracting information from the enemy a key objective during the fight.
Picture it. The party finds a den of cultists inside the city. They kick the door down and start carving through them — eldritch blast, action surge, slash, slash. But the moment the first cultist drops, someone hurls a fireball into the wall. It clips a couple of the players. The building starts to burn and crumble. And the valuable information inside it — information that cannot be replaced — is being torn to shreds and burned to a crisp.
Meanwhile some of the cultists are cutting their own throats, because what they know is too valuable to let the party take.
Now the party has a genuine problem. The building is coming down. There are still cultists who will fight to the last breath. And the longer those cultists are alive, the more of the building burns.
So it splits: some of us have to prioritise the information, and the rest have to prioritise the cultists. A dual-pronged encounter, and a real decision about who does which.
If you want the cult itself to be worth infiltrating in the first place — the doctrine, the hierarchy, the reason those people would rather die than talk — that is a whole build of its own.
2. Recovery of Secret Artifacts
Design a scenario where the players have to retrieve a hidden artifact during the fight.
They are sent to a crypt — not to slay every undead thing in it, but because the item they need is inside. The moment they take it, the undead stir, and they will keep coming until the party reaches the exit. Relentless. Undead fortitude, over and over, all the way out.
Now it is not about killing the monster. It is about carving a path with the thing you came for: the item that opens the door, the item that revives the companion who died in the last fight, the item that is the big bad’s weakness and was hidden down here on purpose.
And you know what this actually is? It is a heist.
That is all it is. Take a heist and reflavour it. Do not call it a heist — your players might, but you should not. Think about what makes heists great in films, in TV, in video games, and start pulling those beats into this kind of encounter.
Uncharted is the reference I keep coming back to here. Uncharted 4 opens strong with a heist, and it is such a well-built sequence — twists, reversals, the plan degrading in real time. If you have never played them, go play 1 through 4. The sheer action-packed storytelling in those games will make you a better DM.
They are already on my list of stolen goods, along with the jeep chase that taught me most of what I know about pacing a set piece — the full list is here.
Steal an artifact and get out. It is so spicy. Fat droplets of sriracha all over your campaign.
1. Magical or Non-Magical Disruption
Picture the scenario. The players enter the lair of a technomancer — someone who melds magic and constructs into their own horrifying creations. The party fights through the place, and eventually reaches one of the final encounters.
There is an endless stream of constructs. And on top of that, glyphs keep spontaneously appearing on the floor. Somebody with high Arcana can work out that the glyphs are being drawn by modrons — tiny constructs floating near the ceiling. Or just mechanical servants. Either way: something is making this happen.
This is different from the environmental challenge back at number eight. An earthquake shattering the ground is a condition the party endures. This is a threat the party can address.
It does not have to be magical, either. It could be a bank of mechanical traps that keeps firing arrows or darts on a cycle. The point is that the hazard has a source, and the source can be destroyed.
Why this one is number one
When you give players the agency to shut down the hazard, the psychological effect is enormous. What they experience is: the DM put a really hard encounter in front of us — and then we made it easier, because of what we chose to do. That feels incredible.
So give them the opportunity, and then actually let them take it. Do not be precious about it. Do not think but I designed so many cool things. Stop. You have an entire campaign ahead of you. You will get to design so many cool things.
From me to you: I am giving you permission to let your baby die. Put it on the altar. Sacrifice it to your players’ enjoyment. Because I guarantee you that two sessions from now you will have an even better idea and you will think hot diggity dog, that is fantastic.
Let the players succeed. Let them destroy the traps. Let them get away with it. Let them completely negate the point of there being a secondary objective at all — because it feels good when they succeed.
Closing Thoughts
That is the ten.
If there is a single thread running through all of them, it is this: a secondary objective gives every player something to think about on turns that are not theirs. That is the actual mechanism. Nobody is scrolling their phone while the rogue takes eleven minutes to decide where to stand, because what the rogue does changes what they are going to do next.
It is also the single best fix for martial classes who otherwise experience combat as I swing, I miss, I wait two hours. Give them a ritual to interrupt, a prisoner to cut loose, a burning ledger to grab.
Secondary objectives are one of the three combat pillars in six tips to never have a boring BBEG again — this article is the long version of that section. The other two are boss design and the arena you fight in.
And if the underlying problem is that your high-level party steamrolls everything you build regardless of objectives, that is a different diagnosis: it is usually about resources, not hit points.
If combat has just become the part of the session where energy drains out of the room, it might not be the encounters at all. Ten things to clean up in your D&D game covers the rest of the usual suspects.
One last thing. If you are a DM reading this because you want to improve your games — thank you. Your players might not say it, but they appreciate you. Any DM willing to take the extra steps to make the game better, regardless of how much experience they have, is a good DM.
What secondary objectives have worked at your table? I would genuinely love to hear them — drop them in the comments on the video.