The so-called “Next Hit Always Miss” bug will not be fixed for the Diablo 2 remake. At least, if the community doesn’t complain after launch.
Diablo 2: Resurrected does a lot of things new, but not everything. After all, the remake of the classic action role-playing game wants to capture the spirit of the original and make veterans happy above all. Curiously, for this very reason, a bug from Diablo 2 will not(!) be fixed for Resurrected. Rod Fergusson from Activision Blizzard reveals this.
If you want to find out everything you need to know about the remaster before the release of Diablo 2: Resurrected on 23 September 2021, the following overview will provide you with all the important information: What you should know about the classes, the gameplay, the changes and more.
Diablo 2 Resurrected: Release, Beta and more – all info on the remaster
A bug stays as it is
What bug is it? For Diablo 2: Resurrected, the so-called “Next Hit Always Miss” (NHM) bug of the original is not to be fixed, but will remain. NHM is actually a useful feature and can be summarised as follows: If your character is stunned or knocked back in melee combat, there is a 100 percent chance that their next attack will miss its target.
This problem results from this: Due to the bug, however, an endless loop of animations can occur, which must be manually interrupted by the player himself. It then looks like this:
- Your character strikes a blow.
- Your character is interrupted and stunned by an opponent while attacking, for example by blocking with a shield.
- You swing again with your character, but miss the target with a probability of 100% due to NHM.
- In the worst case the procedure repeats itself: Your character takes a swing, is interrupted by the opponent and misses again with the following attack.
- An endless loop is created, which can only be interrupted by actively moving away from the opponent and restarting your attack.
Why isn’t the bug being fixed? According to Rod Fergusson of Blizzard, this bug will now not be fixed for Diablo 2: Resurrected because it is “part of the original game experience”. The development team had discussed it and decided that the game bug should remain part of the remake.
Real talk though @RodFergusson, any chance we will see a fix to NHAM (Next hit always misses)? Would really open the game up in some beautiful ways
Bug reference: https://t.co/8yGc3Hrybg
— MrLlamaSC (@MrLlamaSC) August 31, 2021
Not everyone is enthusiastic: In the comments under the corresponding tweet, but also in the original Reddit post that is the starting point of the discussion, not all Diablo fans agree.
For example, they criticise that especially melee classes are “actively disadvantaged” by the bug. Some commentators are also not satisfied with Fergusson’s compact explanation of why exactly this bug is not fixed, but other, “less serious” ones are.
However, there are Diablo 2 players who don’t mind the preservation of the bug for Resurrected. They argue that it would add a touch more realism to the fights if a character misses his target after a stun and has to regroup. In addition, one could easily escape the endless loop by simply changing the position of the character or timing the next attack differently.
Last but not least, this restriction would prevent melee fighters from becoming too overpowered and provide for more variation in the classes and their skills.
The community has a say: According to Fergusson, the NHAM bug will remain part of Diablo 2: Resurrected for the time being. The emphasis is on “for the time being”, because the developer promises that the community’s feedback will be taken into account after the launch. Therefore, it cannot be ruled out that the game bug will be fixed sooner or later after release.
What players are saying about the current closed beta
Diablo 2: Resurrected – What players are saying about the current closed beta
What do you think about the return of the NHAM bug in Diablo 2: Resurrected: Are you in favour of keeping the old bug around, at least for now, or would you rather see it go away as soon as possible? Let us know in the comments!
