Bluetracker

Tracks Blizzard employees across various accounts.


Can we talk about dragonblade's no hit registration issue?

For those who don't know what the no hit registration issue is:

When Genji swings his dragonblade on an enemy there is a chance that the damage doesn't get applied. You will be able to see a clear hit indication on your screen, but the server doesn't recognize that it hit and therefore doesn't apply the damage. The bug (gonna call it a bug since I'm not sure what else to call it) doesn't happen that often, but it happening once can be the difference between winning and losing a match in rare cases.

Here is a moment that happened to me earlier that demonstrates the bug in action:

Click here for demonstration

(this video highlights an extreme case of no hit registration. It will normally not happen at all)

Here is a clip from Shadder2k's stream

This bug has been around since Overwatch was in beta and has yet to be addressed. I know Blizzard listens to the community, so I'm pretty sure they know about this issue already. I just find it weird that they haven't talked about it at all. If it's hard for them to fix it, that's fine, I can understand that, but at least acknowledge the problem.

Here is a great post by Ancine_ on the CompetitiveOverwatch subreddit where he explains a bunch of other issues with Genji

Lastly, I would like to compliment Blizzard on their dedication to Overwatch and their openness with the players as well as the fact that they actually take community feedback into consideration. It is something not many developers do.

(EDIT) Someone posted a link to a very detailed thread on the Overwatch forums that was posted in November. I'm gonna link it here.

Genji is the most bugged hero. 9 major bugs in total

Thank you to Spilledexpression for linking this.

(EDIT 2) We have an official response from Blizzard where they confirm it as a bug


  • Bill Warnecke

    Posted 8 years, 9 months ago (Source)

    Hey folks, we're aware of this bug. I posted a quick note in this thread on our official PTR bug report forums, but also wanted to share that information here as well.

    Thanks for the report.

    edit: oops, fixed link to the correct post.




Tweet