Broken Builds and How to Live With Them: A DM's Guide to Multiclass Mayhem

The Build That Broke the Encounter

You spent three hours designing what should have been a tense, climactic battle. Reinforced walls, multiple phases, a villain with a contingency plan. Then the Sorcerer-Paladin walks up, burns their resources in round one, and the whole thing crumbles before the dramatic music you had mentally queued even gets going.

If you've been DMing for more than a couple of years, you've been there. And if you're honest, maybe you've also been that player — the one who discovered a combo online, rebuilt their character around it, and then quietly felt a little hollow when the encounters stopped being challenging.

Multiclassing and system optimization are a core part of the TTRPG hobby. Figuring out how the rules interact, pushing builds to their limits — that's genuinely fun for a lot of players. The problem isn't optimization itself. It's when certain combinations blow so far past the rest of the table that the game stops being a collaborative challenge and starts being a solo performance.

Let's talk about the biggest offenders, why they work mechanically, and what you can actually do about them.

The Hall of Infamy: D&D 5e Edition

Sorcadin (Sorcerer/Paladin) remains the reigning champion of 5e brokenness, and the math is almost insultingly simple. Paladin's Divine Smite lets you burn spell slots for massive burst damage — and Sorcerer gives you more spell slots via Flexible Casting. Stack Quickened Spell for extra action economy, and you've got a character who can delete most bosses before they take a second turn. The combo has been discussed to death in the community, and for good reason: it makes single-target burst damage trivially easy at mid-to-high levels.

Coffeelock (Sorcerer/Warlock) is the optimization community's white whale. By exploiting the interaction between Warlock's short-rest spell slot recovery and Sorcery Points conversion, a dedicated player can theoretically accumulate an ever-growing pool of spell slots by simply not sleeping. It requires specific rest manipulation and a DM who isn't paying attention, but when it works, it functionally removes resource management from the game — which is a significant chunk of 5e's challenge structure.

Gloomstalker Ranger/Assassin Rogue is the first-round nuke build. If your character acts first in combat (almost guaranteed with the right ability score setup and Gloomstalker's initiative bonus), you can stack multiple attacks with Assassinate's auto-crit against surprised enemies. Against a standard encounter, this build can effectively end fights before most of the table has taken a turn.

Pathfinder 2e: A Different Kind of Problem

Pathfinder 2e's designers clearly learned from 5e's multiclassing headaches. The Archetype system is deliberately more conservative, and the three-action economy makes it harder to stack exponential effects. But that doesn't mean the system is immune.

The Magus/Psychic combination using the Spellstrike action with Amp abilities creates a damage-per-action efficiency that outpaces most other martial casters. It's not game-breaking in the same way as 5e's worst offenders, but it does create a noticeable gap between what this character contributes and what a more straightforward build can manage.

More broadly, PF2e's issues tend to show up in skill check stacking — certain Investigator and Rogue combinations can reduce social and exploration challenges to foregone conclusions, which flattens the non-combat pillars of the game in a way that's less dramatic but equally disruptive to table fun.

Other Systems Worth Watching

Shadowrun has always had a complicated relationship with optimization. The Decker/Face hybrid who can both hack the grid and talk their way past security makes entire skill trees irrelevant for other party members. Call of Cthulhu is largely immune to this problem by design — the system's lethality is a natural balancing mechanism. But Vampire: The Masquerade 5e sees significant power gaps between Discipline combinations, particularly anything involving Dominate stacked with high social attributes.

Practical Solutions That Don't Kill the Fun

Here's the thing: banning builds outright is rarely the right move. It breeds resentment and signals to players that you don't trust them. Instead, consider these approaches:

Encounter design adjustments. The Sorcadin is terrifying in single-target burst scenarios, but far less dominant in multi-wave encounters, mobile fights, or situations where the party needs to conserve resources over a long adventuring day. Design around the build's weaknesses without telegraphing that you're doing it.

The Encounter Budget Conversation. Be transparent with your table. If someone's playing a Coffeelock, have an honest conversation about rest mechanics in your campaign. Most players, when they understand that their build is affecting everyone else's experience, are willing to find a middle ground.

Bounded Accuracy Variants. Some DMs implement soft caps on certain stacking bonuses — particularly relevant for 5e, where bounded accuracy is supposed to be a design feature but certain multiclass combos quietly shred it. A simple houserule capping initiative bonuses or limiting Smite slots per turn can preserve the flavor of a build while pulling it back into the realm of manageable.

Spotlight Redistribution. Sometimes the fix isn't mechanical at all. If one player's build is dominating combat, make sure other players have equal moments to shine in exploration, social encounters, and moments of personal character development. A Gloomstalker who one-shots the opening fight still has to navigate the political intrigue that follows.

A Note on Table Culture

At the end of the day, the most powerful tool for handling broken builds is a table that talks to each other. The optimization community and the roleplay-heavy community aren't natural enemies — they're both chasing the same thing, which is a game that feels meaningful and engaging. When a build starts making the game less fun for anyone at the table, that's a conversation worth having over snacks before the dice hit the mat.