Hello all!
As a Bladedancer main, even after the update to fix frontstab, I still get yellow number frontstabs and white number backstabs. The patch notes states that the angles were fixed, but Just thinking on the pooper today, I had an idea that may be presenting some issue.
Now, I'm not a programmer, so I may just be crazy, and feel free to tell me if this is implausable, but how about this:
The problem is not related to hit detection angles at all.
Blink strike is actually NOT a "extended reach" melee, but actually a short teleport into melee range, then a normal range melee to follow up. (Thereby allowing you to melee from "extended range" but not actually making the melee longer. Contrast to Warlock Thunderstrike, and ACTUALLY longer range melee)
Now what do I think this might mean? It means we may actually be backstabbing from the front and frontstabbing from the back if this brief teleport were to overlap our hitboxes.
This would be much easier to explain with pictures than words, but here goes. If I were to teleport into your hitbox as you face me head on, and my blink strike carries me past the centerpoint of your hitbox, then executes a melee, then the contact point of my melee may actually be on the rear angle of your hitbox.
Conversely, the same could happen if that midpoint is passed from behind, meaning that a stab starting from the rear would pass through the person, hitting from a front angle.
Is this possibly the problem that we're dealing with? Would a change to blink strike's programming to prevent it from ignoring collisions solve the frontstab/failed backstab issue?
Thanks!
-
Edited by Creatioux: 7/2/2016 1:24:07 AMBackstab actually registers player sides as well as their back. So if you run at someone diagonally and Melee their shoulder, it registers as a side/backstab hit. Edit: Also, I can't really imagine a blink strike would overlap hit boxes.