How to Fix Overpowered Abilities in D&D 5e Without Ruining Player Fun

Watch or listen to this blog post here.

When a mechanic is overpowered or out of balance in your game, what should you actually do about it? In most cases, I think you have three basic options. You can do nothing and let it ride. You can tweak other parts of the game to compensate for the overpowered mechanic. Or you can directly change the mechanic that is causing the problem.

For the sake of this discussion, I’m mostly talking about D&D 5e because the game system matters a lot here. A grittier system like Shadowdark or many OSR games may be perfectly comfortable with things being somewhat unbalanced. That can even be part of the appeal. On the other hand, a crunchier and more tightly tuned system like Pathfinder 2e is much more interested in mathematical balance and keeping things within a narrower range.

D&D 5e falls somewhere in the middle, which means game masters are often left making these judgment calls for themselves.

Recently, my friend Joe and I got into a discussion about this after one of our Mothership sessions. There were some elements in the game that felt pretty badly out of balance, but that is also somewhat the point of Mothership. It is a horror game. Monsters are supposed to be terrifying, characters are vulnerable, and sometimes a combat encounter can go horribly wrong very quickly.

For a one-shot, I think that kind of brutality works great. For a long-term campaign, though, it is not really my cup of tea. I prefer characters to have at least some staying power, so Joe and I started talking about what I might tweak if I were going to run a longer Mothership campaign.

That conversation reminded me of something Joe did years ago in one of my D&D 5e campaigns. Joe has a very analytical mind, he is extremely intelligent, and he may have min-maxed the absolute crap out of one of his characters.

When a Powerful D&D Build Becomes Too Powerful

A few years ago, Joe created a ranger named Grist for my Sword Coast Guard campaign. Grist was a bugbear with five levels of gloomstalker ranger and eleven levels of assassin rogue, and the build was phenomenal. It was extremely effective, extremely deadly, and very clearly built by someone who knew exactly what he was doing.

Now, as a general rule, I do not have a problem with players min-maxing or creating powerful characters. I may roll my eyes at it from time to time, but I do not forbid it. Different players enjoy different parts of the game, and for some people, building a highly optimized character is a major part of the fun.

The problem with Grist was not simply that he was powerful. The problem was one particular ability: the gloomstalker ranger’s Umbral Sight.

In addition to granting darkvision, Umbral Sight makes the character invisible to creatures that rely on darkvision to see them while they are in darkness. If that does not sound like a huge deal at first, it absolutely can be depending on the campaign.

If Grist was invisible to a monster, that monster had disadvantage when attacking him, while Grist had advantage when attacking the monster. In D&D 5e, that is already a massive swing in his favor. Then you add the fact that Grist had an Armor Class of 20, and suddenly many creatures could barely hit him at all.

Now pile rogue levels on top of that. Because Grist frequently had advantage, he was landing Sneak Attack constantly, and his odds of scoring critical hits were substantially higher. When those crits happened, all those Sneak Attack dice doubled.

So now we had a character who was extremely difficult to hit and capable of dealing absurd amounts of damage. That is a nasty combination.

The Campaign Made Umbral Sight Even Stronger

Under different circumstances, Umbral Sight might have been powerful but manageable. My campaign made it ridiculous.

Most of the campaign took place in the Underdark. We were talking caves, tunnels, underground ruins, and lots of darkness. On top of that, the rest of the party had darkvision, so there was almost never any practical reason for them to carry a light source.

As a result, Grist functionally had something very close to permanent greater invisibility in a huge percentage of encounters. He was standing in darkness almost all the time, the enemies were using darkvision to see, and the party was not carrying torches or lanterns that would ruin the effect.

After seeing this play out for a while, I came to the conclusion that matters most in situations like this: the ability was too powerful in this campaign.

That was the real issue. Not that the rule was universally broken. Not that Joe had done anything wrong. The interaction between the ability, his build, and the campaign environment was creating a problem at the table.

At that point, I had to decide what to do about it.

Doing nothing was not really an option. The ability was having too much impact on the game, and pretending otherwise was not going to make the problem disappear. That left me with two realistic choices: I could adjust other parts of the campaign to compensate for Umbral Sight, or I could directly change Umbral Sight itself.

Want to Get Better at Making Tough GM Calls?

Game mastering is full of situations where the rules technically work, but the result at the table does not. An ability may be too strong in your particular campaign, an encounter might not function the way you expected, or a perfectly legal player option may create consequences you never anticipated.

The Secret Art of Game Mastery is packed with practical advice for handling those situations. It covers player management, encounter design, preparation, improvisation, pacing, and the countless judgment calls game masters need to make when the rules alone do not provide a satisfying answer.

If you want to get better at diagnosing problems, adapting your game, and making stronger decisions behind the screen, check out The Secret Art of Game Mastery.

Why Compensating for an Overpowered Ability Can Backfire

There was actually a very simple way I could have dealt with Grist without technically changing anything on his character sheet. I could have started putting light sources everywhere.

If most dungeon rooms, caves, and underground areas were brightly illuminated, monsters would no longer need darkvision to see him. That would effectively shut down Umbral Sight in a large percentage of encounters while still letting Joe benefit from it occasionally.

I could also have started using more creatures with blindsight. Or, if I really wanted to force the issue, I could have simply added blindsight to monsters that did not normally have it.

Technically, none of that would change Umbral Sight. Joe would still have the exact same ability written on his character sheet.

But come on.

That would still be a nerf. It would just be a nerf with extra steps.

And frankly, I think that would kind of suck for Joe. If I constantly redesigned the world specifically to make his cool character ability stop working, what was the point of him having it in the first place?

Fixing One Problem Can Create Several More

The bigger issue with indirect fixes is that they rarely affect only the thing you are trying to fix.

Giving monsters blindsight would not just affect Grist. It would also affect other characters trying to hide, a wizard casting invisibility, fog created by an eversmoking bottle, and any number of other abilities or tactics.

The same thing happens with lighting. If I suddenly fill every Underdark cave, dungeon, and ancient ruin with convenient light sources, the rest of the players may reasonably start wondering why they bothered choosing races with darkvision.

Now I have changed the game for everyone because of one character ability. That is not ideal.

It also creates more work for the dungeon master, which I hate. Now I need to constantly remember which rooms have light sources, which monsters need special senses, and which encounters need to be modified specifically to deal with one character.

Lame.

This is one of the main reasons I usually prefer to address the root cause of the problem rather than building an elaborate collection of countermeasures around it.

If Umbral Sight is the thing causing trouble, why not change Umbral Sight?

Fix the Root Cause Instead

In Grist’s case, I decided to change how the ability worked.

Instead of Umbral Sight being permanently active whenever he stood in darkness, Joe would need to use a bonus action to hide. Once he did, the invisibility effect would activate. Then, when Grist attacked, the effect would end and he would become visible again until he spent another bonus action to hide.

That was it.

The ability was still very useful. Joe could disappear into darkness, gain advantage, avoid attacks, and use the ability tactically. What he could no longer do was walk through almost every underground encounter with what amounted to permanent invisibility.

That was the goal.

I was not trying to destroy the ability or punish Joe for making a powerful character. I was trying to bring one mechanic back into a range where it remained fun and useful without distorting the entire campaign around it.

Don’t Nerf an Ability Into the Ground

This is where game masters can easily make the opposite mistake.

You notice that something is too powerful, get frustrated with it, and then nerf it so aggressively that the player wishes they had never chosen the ability in the first place. That is not really solving the problem. You have just created a new one.

If a player chose an ability because it sounded cool, it should still feel cool after you adjust it. The goal is not to make the problem disappear by making the option worthless. The goal is to preserve the fun part while removing the piece that is disrupting the game.

In Grist’s case, hiding in darkness and becoming invisible was still strong. It still gave Joe meaningful tactical choices and let the character feel like a gloomstalker. The difference was that the ability now carried an action economy cost and required active use instead of functioning as a permanent passive advantage.

To me, that was a much better compromise than turning every cave in the Underdark into a brightly lit shopping mall.

Talk to the Player Before Changing Their Character

There is another part of this that I think is extremely important: talk to the player.

Do not simply show up one week and announce that you changed their character because you were tired of dealing with it. Explain the problem you are seeing at the table, why you think the mechanic is creating issues, and what you are trying to accomplish with the change.

Then listen to what they have to say.

Most players are reasonable when you approach the conversation as a shared problem rather than accusing them of doing something wrong. Joe had not cheated. He had not exploited some loophole I had explicitly banned. He had simply built a character using legal options available in the game.

That distinction matters.

The problem was the interaction between the rules, his build, and my campaign. So we talked about it, came up with a solution, and moved on.

When Should You Nerf an Overpowered D&D Ability?

I do not think game masters should start nerfing abilities simply because a character is strong. Powerful and overpowered are not the same thing.

If one player deals a little more damage than everyone else, who cares? If a character has one encounter where their perfect ability completely dominates the situation, that can be awesome. Players should get opportunities to feel powerful and have moments where their character choices pay off.

I start worrying when a mechanic consistently distorts the game. Maybe it trivializes encounter after encounter. Maybe it forces you to redesign large portions of the campaign specifically to counter one character. Maybe it prevents other players from getting opportunities to shine because one ability solves almost everything.

That is when I start looking at adjustments.

Even then, I would usually rather make one small, targeted change than redesign the rest of the campaign around the problem.

Balance Is About the Table, Not Just the Rules

At the end of the day, balance is not only about numbers on a character sheet. It is about what is actually happening at your table.

Two abilities may look perfectly reasonable on paper and become ridiculous when combined. A mechanic might work fine in one campaign and become overwhelming in another because of the environment, adventure structure, party composition, or the way the game master runs encounters.

That is why game masters need to be willing to adjust.

Not constantly. Not because you lost one combat encounter to the players. And definitely not because a player used their character effectively.

But when something is repeatedly harming the game, deal with it. Preferably at the source.

Make the smallest change you can. Preserve the part that makes the ability fun. Explain what you are doing and why. Listen to the player, try the new version, and see how it works.

You can always adjust it again.