The fact smite and surge changes are intended is really, really weird

End result is very inconsistent and overall less damage than before. There is also much less feedback with killing enemies now that the “pop” is not guaranteed and a limb just randomly flies off (which in itself looks bizarre). It is mind boggling that this is all intended and has been a huge, whacky nerf to a weapon and blitz that honestly were in a good place.

3 Likes

The hotfix today included this note, which was meant for the previous patch (where the Surge/Smite behavior was changed):

Surge staff on-kill gore effects are no longer always triggered when killing an enemy - now also limbs and heads may be dismembered instead of the whole torso.

To clarify, the change in the code seems to be (please someone correct me if I’m wrong) that both attacks now target random body parts, when they didn’t before. This means weird inconsistent damage and the change in visual effect.

To me, this patch note does not confirm that the new damage behavior is fully-intended and/or not-bugged in some aspect. I think the change/damage might make sense for Smite (and I saw, but can’t locate, mention that the new behavior synergizes with something), since it’s a utility blitz meant for CC.

But for Surge, I’m not liking it.

Fingers crossed it’s addressed quickly.

2 Likes

Correct. The change was intended to allow limb dismemberment, by altering the weapon’s targeting behaviour. However, the weapon’s targeting impacts both gameplay and visual effects so changing one indirectly the other. Not entirely unusual (hit detection subsystem registers body part hit, damage and VFX subsystems take the appropriate action), but the knock-on effect of the change was overlooked/missed.

EXACTLY this, now surge desperately needs help. hell, staves in general need massive help

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.