It seems it was considered at one point, but it was ultimately decided to be a “part of the original experience.” Indeed, it is part of the original Diablo 2 experience and, no matter what, some players will be mad about any changes outside updated graphics. Unfortunately for those fans, it isn’t being fixed and won’t be for launch, but perhaps down the road, it could be.Īs seen above, when Diablo 2 executive producer Rod Fergusson was asked if the bug would be fixed or not, he confirmed that it won’t be. Zeal Paladins, Fury Druids, Fend Amazons, and more suffer greatly because it undermines their core skill as such, many were hoping this is one of the bugs that would be squashed come the release of Diablo 2: Resurrected. Auto-hit attacks miss, and skills that include multiple hits are affected the worst. The very fact that it is so rampant and so obvious really proves how big the bug actually is, and why some could even think it was an intentional design.īut it’s not.

In short, after a player’s hit interruption animation comes into play due to effects like stun, knockback, block, and more, they will miss the next hit 100% of the time. It is possible, though, for more casual players to go through the entire game without realizing it wasn’t intentional. Number one thing is the amount of data which has to be managed properly, and number two is making it work even if the duped items never appear on the same character/game/realm/server again.While mostly self-explanatory, Diablo 2’s NHAM bug is notorious because it is predictable, well-known, and build-breaking. The best way todo it, which would elimate any possibility of duping, would be to track every item even if it’s “used” (like socketed items and runes). But depending on how well coded the server-side is this can lead to permanent character corruption or other side effects.Īside from that, there is no easy fix. The easiest way to fix this would be to save the characters state when the game instance goes down for whatever reason. If one dupes a Jah and immediately makes an Enigma, the duped rune will stay forever. On the other hand, this mechanics doesn’t work for runewords.

However, as soon as original and dupe appear in the same game, one of them will be removed. The dupe-procedure alone does work, But I don’t know if it works to forcefully crash the server, or more specifically the game instance running on it to ensure the character the item originates from is rolled back.

Shako lightning bug diablo 2 bug