The change arrived in Diablo IV Hotfix 2 for patch 3.2.1, where Blizzard says it fixed an issue causing Rogue's Dance of Knives to sometimes deal far more damage than intended. That wording matters. This was not presented as a normal balance adjustment to an overperforming but correctly functioning Rogue build. Blizzard classified the behavior as a bug.
So if your Dance of Knives Rogue suddenly feels considerably more attached to the laws of arithmetic, this is why.
Dance of Knives Damage Kept Growing as Players Continued Spinning
Players started noticing the problem almost immediately after Season 15 launched. Dance of Knives appeared perfectly ordinary at first, but during sustained combat the damage could begin climbing well beyond what the character's gear and Paragon progression should reasonably support.
One player described entering The Pit around Paragon 140 and initially seeing ordinary numbers before the build began dealing hundreds of billions. Continuing the Dance pushed individual hits into the tens of trillions. Other clips shared by Rogue players showed the numbers escalating far beyond that.
The important observation was not simply that Dance of Knives hit hard.
Seasonal builds are supposed to hit hard.
The suspicious part was that the damage appeared to keep ramping during prolonged use instead of settling around a value explained by the character's normal multipliers.
Players quickly began referring to it as infinite scaling, although Blizzard has not used that term or explained the exact internal calculation that was failing.
Some Damage Numbers Apparently Rolled Into the Negative
The community knew things had become properly unreasonable when damage displays started producing negative values.
One widely shared Season 15 example showed Dance of Knives reaching an enormous displayed value before the number appeared with a minus sign. Players familiar with numeric overflow immediately suggested that the underlying damage calculation had exceeded the positive range of whatever signed number format was being displayed and wrapped around into negative territory.
That interpretation is technically plausible, but Blizzard has not published an engineering explanation confirming exactly what happened inside the damage calculation.
What matters for ordinary players is simpler.
If your damage number has become so large that the interface appears to have developed philosophical objections to positivity, the build is probably not behaving as intended.
Pit 150 Was Already Falling Days Into Season 15
The bug became particularly visible when Rogue players started posting Pit 150 clears almost immediately after the season began.
One Rogue community post showing a Dance of Knives Pit 150 clear arrived while many players were still leveling their first seasonal character. The discussion around it was unusually blunt: even Rogue players were treating the clear as evidence of the bug rather than a legitimate demonstration of what an ordinary Season 15 Dance of Knives setup could accomplish.
That distinction matters because Pit 150 is supposed to represent the extreme end of Diablo IV progression. Reaching it normally requires a mature build, optimized equipment, substantial Paragon investment and enough understanding of the game's multiplicative damage structure to make a tax accountant consider changing careers.
Doing it on the second or third day of a season raises questions.
Doing it while your damage keeps growing until the numbers stop fitting politely on screen answers several of them.
Blizzard Has Not Confirmed What Actually Caused the Scaling
Community theories appeared almost as quickly as the damage videos.
Some players suspected interactions involving Season 15 Charm sets. Others focused on Imbuement-related bonuses and suggested that repeated activation might have been stacking a damage effect that should have reset or remained capped. Several Rogue discussions pointed toward newly changed seasonal interactions rather than Dance of Knives itself being fundamentally broken.
Those theories may eventually prove useful in understanding what happened.
They are not an official explanation.
Blizzard's Hotfix 2 notes only say that Dance of Knives could sometimes deal much more damage than intended. They do not identify the specific item, Charm, passive, Imbuement or stacking calculation responsible.
So we should resist converting the community's best theory into patch documentation Blizzard never wrote.
This Was Not Just a Naturally Strong Dance of Knives Build
That distinction is especially important because Dance of Knives was already shaping up to be a strong Season 15 starter before the bug became widely understood.
Rogue build creators had been recommending it for rapid early progression, with players reporting comfortable movement into high Torment levels. Season 15's hidden Runewords made the early setup even easier because Stealth and other secret Diablo II-inspired recipes gave players accessible equipment options through the Horadric Cube.
In other words, Dance of Knives did not need infinite mathematical enthusiasm to be useful.
The bug simply took a good build and removed the ceiling.
Hotfix 2 Has Now Removed the Unintended Damage
Blizzard deployed the fix on September 17 as part of Hotfix 2.
The same small update also corrected several other wonderfully strange Season 15 interactions. It fixed Ancestral Stealth Runewords accidentally inheriting Enigma's power, repaired a Splinter of the Mother interaction with Leoric's Crown, and stopped Messerschmidt's Reaver from healing enemies.
Then there was Dance of Knives.
Blizzard's entire official description is one line: Rogue's Dance of Knives could sometimes deal much higher damage than intended.
The brevity does not really communicate what players had been seeing.
Season 15 Rogue had briefly discovered compound interest for knives.
This Is a Bug Fix, Not a Conventional Rogue Nerf
That wording also matters for anyone logging into a Rogue today and wondering why the build suddenly lost an extraordinary amount of damage.
Hotfix 2 did not announce that Blizzard had decided Dance of Knives was generally too strong and reduced its base damage by 20 percent.
It did not say an Aspect was being intentionally toned down.
It did not change the documented balance target of the skill through an ordinary tuning pass.
It fixed unintended damage behavior.
There will inevitably be players who experienced the bugged version for a day and now describe the correction as a catastrophic nerf. That is understandable emotionally. Once your Rogue has dealt numbers normally associated with national debt, returning to legal arithmetic can feel oppressive.
But a bugged damage multiplier cannot reasonably become the permanent baseline simply because people enjoyed it for forty-eight hours.
The Real Question Is How Strong Dance of Knives Is Without the Bug
That is what Rogue players should be testing now.
The useful question is not:
"Can Dance of Knives still make Pit 150 disappear while my damage counter attempts to escape the integer range?"
The answer is presumably no.
The useful question is whether the intended Season 15 version remains a competitive leveling and endgame build once the runaway scaling is removed.
Early evidence before the exploit became widespread suggested that it probably does. Dance of Knives was already being recommended as a strong seasonal starter, and it benefits naturally from the mobility-heavy Rogue toolkit. The hidden Runewords discovered this week also give the class additional gearing options during early progression.
But anyone comparing post-hotfix performance with videos recorded during the bug should be extremely careful.
Those videos are now archaeological evidence.
Rogue Has Been Here Before
The community reaction also contained a familiar joke: somehow, Rogue keeps finding damage interactions capable of bending the endgame around them.
That is not entirely imaginary.
Earlier this year, high Pit rankings were heavily influenced by bugged Rogue interactions, while Season 14 produced its own collection of strange behavior. In July, we covered the Shadow Clone bug that could trigger additional Shrine effects, including extra Soul Eaters during Deathtoll Chamber runs.
That bug was far more amusing than meta-defining.
The recurring high-end damage bugs are another matter.
When leaderboard content exists, a bug that multiplies damage far beyond intended values does not merely make one build funny. It can distort rankings, progression expectations and the entire conversation around what constitutes a legitimate clear.
Pit Rankings Become Meaningless Very Quickly When Damage Bugs Appear
This is why players pushing high-end content tend to be less enthusiastic about these bugs than casual players watching the numbers explode.
If a build can reach Pit 150 through an unintended interaction that other classes cannot reproduce, the leaderboard stops measuring normal build strength.
It begins measuring who adopted the bug quickly enough.
Rogue players in the community were already complaining about exactly that before Hotfix 2 arrived. Several responses to early Pit 150 posts argued that the clears should not be treated as legitimate progression because the build's damage was obviously being driven by the bug.
That does not mean the players who discovered the interaction did anything mysterious or malicious. Many encountered it through ordinary gameplay. One player specifically described noticing the numbers rising unexpectedly and only later realizing something was wrong.
The problem exists at the system level.
Once a bug affects competitive progression, Blizzard needs to move quickly.
The Timing Before Wider Leaderboard Competition Matters
The timing of the fix is therefore fortunate.
Dance of Knives started producing extreme results before Season 15's competitive ecosystem had fully settled. Players were already worrying that the bug would immediately dominate ranking conversations.
Hotfix 2 closes the interaction early enough that the majority of the season can proceed without Rogue damage climbing indefinitely in the background.
Whether Blizzard needs to address any records achieved during the bugged window is a separate question. The Hotfix 2 notes do not announce leaderboard removals, resets or penalties.
So we should not invent any.
Players Should Not Worry About Being Banned for Accidentally Using Dance of Knives
Another recurring concern in community discussion was whether simply playing the build could be considered exploiting.
Some players reported discovering the damage ramp naturally while running The Pit. They were not editing game files, injecting code or performing some elaborate sequence involving seventeen vendors and a sacrifice beneath Kyovashad.
They held down the skill.
The damage became ridiculous.
Blizzard has not announced disciplinary action against ordinary players who encountered the bug, and nothing in the Hotfix 2 notice suggests that playing Dance of Knives itself was prohibited.
That does not mean deliberately abusing known bugs to manipulate competitive systems is something we would recommend.
It means rolling a Rogue and noticing that the skill Blizzard gave you deals too much damage is not automatically evidence of criminal intent.
Season 15 Has Produced an Impressive Number of Strange Bugs Already
Dance of Knives is also joining a surprisingly crowded Season 15 bug list.
The season itself launched late after login problems.
Solo Self Found remained unavailable.
Some seasonal characters appeared with old Paragon, Gold and progression.
Warlock class quests became stuck.
Old Eternal Mythics collided with the returning Crafted Mythic restriction.
And yesterday's hidden Runeword discovery almost immediately produced a Stealth and Enigma interaction Blizzard had to remove.
Season of Hell's Legacy has excellent ideas.
It is also currently generating hotfix notes like somebody left the Horadric Cube unattended with root access.
The PTR Could Not Catch Everything
There is an interesting contrast with the Season 15 PTR.
We spent August discussing the overpowered interactions players found during public testing, and whether the PTR gave Blizzard enough time to clean them up before launch.
But Season 15 deliberately withheld some content from the PTR. Blizzard wanted the anniversary season to contain discoveries that players had not already dissected weeks before release.
That decision paid off beautifully with the secret Runewords.
It also means the live game contains combinations that never received the same mass testing as the publicly available PTR systems.
We cannot say that missing PTR content specifically caused the Dance of Knives problem. Blizzard has not said that.
But Season 15 demonstrates the unavoidable tradeoff.
If you want surprises, some surprises will be bugs.
Dance of Knives Is Back in the Realm of Normal Numbers
For now, the situation is straightforward.
Dance of Knives is still in Diablo IV.
Rogue has not been disabled.
The build has not been deleted.
Blizzard has removed the unintended scaling that allowed its damage to rise dramatically beyond the intended level.
Players who copied early Season 15 videos should therefore expect their post-hotfix results to look very different.
That does not necessarily mean the build is bad.
It means the game has remembered where the top of the calculator is.
Season 15 Dance of Knives had roughly forty-eight hours where continuing to spin appeared to make the damage increasingly absurd.
Hotfix 2 ended the dance.
Or at least taught it how to count.
