News

Diablo 2: Resurrected EP Addresses ‘Next Hit Always Misses’ Bug

Diablo 2: Resurrected is an attempt to resurrect and remaster the original experience of Diablo 2, which is still considered a classic game over 20 years after its release. However, it appears that Diablo 2: Resurrected will also be incorporating negative aspects of the original Diablo 2 experience, such as the infamous "Next Hit Always Misses" bug.

The "Next Hit Always Misses" bug is a glitch that affects Diablo 2 players whenever their hit interruption animation is triggered by effects like stun, knockback, hit recovery, block, or dodge. Once the animation is triggered, the bug causes the next hit the player makes to automatically miss no matter what kind of attack it is. Reportedly, even auto-hit attacks are guaranteed to miss if the player tries to use them right after recovering from the interruption. This could lead to players being caught in a cycle of being hit and missing their counter-attacks, leaving them open to be hit again.

RELATED: Diablo 2 Development Involved 'Brutal 18 Month Crunch' Where Employees Were Given Sleeping Bags

While this bug isn't game-breaking by any means, its effects can still be very noticeable in regular play, so it's easy to understand why players wanted to see if Blizzard would fix the bug in Diablo 2: Resurrected. Unfortunately, according to Diablo EP Rod Fergusson's official Twitter account, the developers have decided to leave the glitch intact to make sure they are accurately recreating the Diablo 2 experience. Like the popular loot feature that will be absent at launch, Diablo 2: Resurrected could see the glitch addressed later on.

As of writing, several fans have stated that they would prefer the "Next Hit Always Misses" bug be fixed in Diablo 2: Resurrected. One user even noted that the point of a remaster was to fix old bugs that negatively impacted the player experience. They also openly wondered what the point of leaving the bug in would be, aside from helping the caster class. Another user argued that leaving this bug in would be no different from leaving Fend and Fury bugged. One user stated that this decision is disappointing specifically because Diablo 2 is already geared toward caster and cast-like skills.

Fergusson's apparent willingness to revisit the issue after launch may reassure disgruntled fans. However, it can't be denied that many players seem genuinely frustrated about this. While the Twitter replies to Fergusson's post did acknowledge that a certain portion of the player base would complain if any changes were made, the overall consensus was that they'd prefer the issue be addressed soon after Diablo 2: Resurrected launches.

Diablo 2: Resurrected releases September 23 on PC, PS4, PS5, Switch, Xbox One, and Xbox Series X/S.

MORE: Complete Diablo 2: Resurrected Barbarian Class Breakdown

Original Article

Spread the love
Show More

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button