Eviscerator Heavy following a shove attack has a long charge time before registering as a heavy attack

Issue Type (Required):

Other

Issue Description (Required):

When I am clearing hordes with eviscerator, one of the combos I used a lot before the class overhaul patch (I don’t know if this patch broke it, but it felt like it did) was:

shove → shove attack-> H1 L2 L3, repeat.

The problem with this combo is that the shove + shove attack acts as an L1 L2, so following it up with a charged attack that isn’t charged enough follows up with L3 instead of an H1 and turns the combo into:

shove → shove attack-> L3 L4 L1.

It doesn’t help that visually the L3 and H1 look exactly the same on execution, so you don’t know if you messed up until you start doing the L4 L1 instead of L3 L4. But I learned that visually if I waited for the eviscerator to move across the bottom right of my screen, the heavy would be charged (you can see the eviscerator being lifted up for the heavy attack). However, as of late, waiting for this moment to occur was not in fact long enough, and I’ve been accidentally executing the L3 instead of the H1 a lot more often. I end up having to hold the heavy just a short moment longer for it to actually execute as an H1 than my muscle memory remembered.

A bit of background with eviscerator, the light combo is strikedown, vanguard, vanguard, strikedown, so if you don’t hold the attack following the shove attack long enough, your cleave combo (L2 L3) becomes a double strikedown combo (L4 L1).

What got me suspecting something was wrong was that it felt like if instead of a shove attack, I simply did H1 L2 L3 L4 on loop, or H1 L2 L3 block cancel, the H1 came out a LOT faster (barely any charging time). So I did an experiment and was like what if I held down the block button following the shove attack? The combo then incorporates a “block cancel” like below.

shove → shove attack → hold block following shove (just for a split second) → H1 L2 L3

The above combo was just as fast if not faster than the first combo, despite incorporating a block cancel, which leads me to believe that there is a bug where following a shove attack, the H1 is slower than any other H1 (from neutral, following L4, or following a block cancel).

Edit: to do the first combo, I hold down the attack button to execute the shove, attack, H1 with a single mouse hold. Letting go of the mouse button for a moment after the shove attack before holding again for the H1 does not appear to fix the issue.

TLDR: First heavy on eviscerator following shove attack is slower than first heavy from neutral or following the appropriate light attack or block cancel.

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