Scene-Stealer in Your Own Campaign: How to Keep Your NPCs in Their Lane

Every DM has that one NPC. You know the one. You built them with a rich backstory, a distinctive voice, maybe a tragic arc that felt important. And then somewhere around session six, you looked up and realized your players were basically escorting this character through their own adventure.

Welcome to the DMPC problem — and the tricky part is, most DMs don't see it coming.

A DMPC, or Dungeon Master Player Character, traditionally refers to a fully statted-up character the DM runs alongside the party. But the more common and sneakier version isn't some sword-swinging tag-along. It's the beloved mentor who always has the right answer. The roguish ally who swoops in during every climactic moment. The mysterious benefactor whose personal drama keeps bleeding into the main plot. These NPCs aren't sitting at the table, but they're absolutely running it.

How It Happens (And Why It's Not Really Your Fault)

Here's the thing: good worldbuilding creates compelling characters. You're supposed to care about the people who populate your world. The problem isn't that your NPCs are interesting — it's when their interests start overriding your players' choices.

It usually starts small. An NPC gives the party a quest. Then they show up to help. Then they start offering opinions. Then the players are making decisions based on what this character wants instead of what they want. Before long, the campaign has quietly shifted from "the story of your players' characters" to "the story of your NPC, as witnessed by some adventurers."

This drift is especially common when DMs are emotionally invested in a particular NPC's arc. And honestly? That investment is what makes you a good storyteller. The trick is learning to redirect it.

The Diagnostic Questions Every DM Should Ask

Before your next session, sit down and run through these honestly:

Who solved the last three major problems? If the answer involves your NPC more than once, that's a flag. Players should be the primary problem-solvers in their own campaign.

Whose backstory drove the last story arc? Player characters' histories should be the fuel. If your NPC's past trauma or personal vendetta has been the engine for multiple sessions, you've crossed a line.

When your players describe the campaign to friends, whose name comes up first? This one stings a little, but it's worth asking. If they're leading with your NPC instead of their own characters, something's off.

Does the NPC have opinions about player choices? Occasional input is fine. Consistent judgment — especially if players feel pressure to accommodate it — is a problem.

Can the story move forward without this NPC? If the answer is no, you've accidentally made them load-bearing. That's a structural issue, not just a narrative one.

What Good NPC Support Actually Looks Like

Compelling NPCs don't solve problems — they create opportunities. There's a massive difference between an NPC who rides in and defeats the villain's lieutenant and one who gets captured, forcing the players to make a hard call about whether to rescue them or press forward.

The best supporting characters in any story exist to make the heroes more interesting. Think about the role of characters like Alfred in Batman, or Samwise in Lord of the Rings — they're essential, but they never take the wheel. They reflect the protagonists back at themselves. They create stakes. They occasionally complicate things in ways that require the hero to grow.

Your NPCs should do the same. Give them wants, not solutions. Give them needs that your players can choose to address — or ignore. Give them flaws that create friction, not wisdom that eliminates it.

Course-Correcting Mid-Campaign

If you've recognized the problem in an ongoing game, don't panic. You don't need to kill the NPC (though sometimes that's narratively earned — just don't do it as a punishment). Here are some gentler approaches:

Step them back physically. Have the NPC get reassigned, injured, or pulled away by their own obligations. You don't need a dramatic explanation. Just reduce their presence and let the players fill the vacuum.

Make them need something. Flip the dynamic. Instead of the NPC being a resource the party draws on, make them a liability or a dependent. Players who have to protect or rescue an NPC feel far more agency than players who follow one.

Let them be wrong. Nothing deflates an NPC's authority faster than having them give bad advice that leads to real consequences. Do it once, clearly, and your players will start trusting their own instincts over this character's.

Ask your players directly. This is the nuclear option, but sometimes it's the right one. A quick out-of-character check-in — "Hey, how are you feeling about Seraphine's role in the story?" — can surface resentment before it curdles into checked-out players.

The Real Test

Here's the simplest way to know if your NPCs are working correctly: after a session ends, are your players talking about what they did, or what happened to them?

Players who feel like the authors of their story will show up excited. Players who feel like audience members will start canceling sessions.

Your NPCs are part of the world. Your players are the story. Keep that hierarchy intact and you'll never have to worry about whose campaign it really is.

Now go run your game — and let your players run it with you.