Diablo 4 Player Beats Pit 150 Completely Naked

Jaym0 Avatar by Jaym0

Gear is optional, or at least, it was for a few days.

Diablo 4 content creator Mekuna stunned the community by clearing Pit 150, the game’s most difficult endgame content, completely naked, thanks to a now-fixed bug affecting the Sorcerer class. No armor, no accessories, just a common wand, a focus, and an absolutely broken build.

Watch the run here:

How the Sorcerer Bug Worked

The bug revolved around the Sorcerer’s EnlightenmentEnlightenment Key Passive, which builds stacks as you cast spells of different elements. Once at 100 stacks, you become “Enlightened”, boosting damage, mana regeneration, and attack speed.

The bug appeared when EnlightenmentEnlightenment was combined with the Smoldering EmberSmoldering Ember seasonal power from Season 9. If triggered right before entering a portal (like those in the Pit), the elemental damage bonus would skyrocket into absurd territory. At one point, Mekuna’s Sorcerer had a staggering +581,000,000,000% Lightning damage.

With damage numbers that high, even Pit 150’s beefiest enemies melted instantly.

Blizzard Has Already Fixed the Bug

Sadly (or thankfully?), this naked Sorcerer dream is no longer possible. Blizzard has since dropped a hotfix patch that removes the EnlightenmentEnlightenment damage stacking bug, shutting down one of the most broken builds Diablo 4 has ever seen.

So if you were thinking of stripping down and joining the leaderboard ranks, don’t bother. The naked meta is officially dead.

…But Another Bugged Sorcerer Build Just Surfaced

Interestingly, this was not the only Sorcerer bug of the season. A few days ago, players discovered a more complicated version of the EnlightenmentEnlightenment + Smoldering EmberSmoldering Embers interaction. This variant requires carefully cycling EnlightenmentEnlightenment with a secondary modifier, making it much harder to execute consistently.

In contrast, the build Mekuna used was so easy to pull off that any player could replicate it, which is likely why Blizzard reacted so quickly. But now, the new version of the bug is here, despite working off a slightly different interaction. There is no official fix yet, but chances are high that Blizzard will take care of it as well.