Notorious Apex Legends 'Hit-Reg' Bug Has Reappeared Following Recent Update
By Jack O'Dwyer
An infamous bug that almost entirely negates damage to enemy players has resurfaced following this past week's update.
The "hit-reg" bug — called as such due to its effect on user hit registry against enemy players — has returned to Apex Legends. Obviously, in a situation where hitting opponents in a firefight is, quite literally, the cornerstone of gameplay, this bug is nothing short of disastrous. It's no surprise that players are exceedingly frustrated by the hit-reg's return as several have discovered their bullets going right through the enemy and vanishing on the other side.
Here's what you need to know about the bug's resurgence.
Notorious Apex Legends 'Hit-Reg' Bug Has Reappeared
Fortunately, since this bug has appeared before, it's likely that the fix will be twice as quick to apply the second time around. Respawn Entertainment have seen this before and, as a game-breaking bug, it wouldn't surprise us if the development team jumped on it as soon as possible.
In fact, that appears to be exactly the case, as the Live Customer Service Twitter account for Apex Legends, (@RSPN_Pav) has already issued a post regarding the issue.
The account replied to a tweet thread by Vaifs (@Alliance_Vaifs) a Swedish professional Apex Legends player, who happened to catch the bug on film yesterday, May 11. His attempts to take down an enemy player in close combat were unsuccessful as the hit-registry bug kicked in, making his shots null and void. TSMFTX ImperialHal (@ImperialHal) replied to the video explaining that the same thing happened to him, as well, "with the same exact scenario , wraith leaving Q and the new skin."
ImperialHal tagged both Pav and John Larson (@RSPN_JayBiebs), the popular Live Balance Designer turned unofficial community liaison, for help. Pav responded less than a minute later, writing they'll take a look at the issue.
Respawn Entertainment has yet to officially acknowledge the bug's return at the time of writing. DBLTAP cannot confirm a date for it to be patched out.