devtrackers.gg
Unrelated to spin reductor, he was already in a parry a while before blocking your attack (blocking even the enemy's) which has disabled the spin reduction already.
Unrelated to spin reductor, he was already in a parry a while before blocking your attack (blocking even the enemy's) which has disabled the spin reduction already.
That was our other theory, that it was the very edge of the active parry box. To that fact, that angle looks like a back/ side parry which were supposed to be eliminated or reduced? I think the general reaction myself included while spectating of shock the attacker I'd say is enough to tell something ain't right here still. The swing was fine Rty should have parried it. The issue is it looking as if he was blocked by a force field on an attack that should have gone through.
Ideally, this swing should've gone through, we definitely agree on that front. However it is still working correctly -- the parry box is very big, but it is only the first filter for deciding a parry, we check for various angles afterwards. This one passed the positioning angle, which we're looking to reduce further. We have already reduced it in this patch, but not enough. It can be a little tricky because it can lead other situations where the attack passes through. But we're now using several more filters to decide a parry, so hopefully these hits should be eliminated in the future.