Guild Wars 2

Thats is becoming over the top. First were issues with quickness stomping, but now it even affect my normal ones where i can execute 3x stomps in a row without any effect and it happen too often. I just cleave now as i basically cant stomp anyone.

+1
I’ve been having this problem pretty kitten often.

I thought it was just me….but i have experienced this in PvP way too often after HOT was released…
Start to stomp…finish it…but target is not killed..start to stomp again…fininh it…but alas target is still alive…..start to autoattack till he is dead..

Yah..that kitten started after HOT for me.

Same here. Pls fix, made me loose a couple of 1v1s i origanilly won against reapers. If stomp fails, i die and in downstate is reaper just to strong.

Yes. Noticed this too.

I’ve noticed the same: first it was quickness stomps that lagged, now it’s normal stability stomps too.
The delay is very long, around 3 seconds I’d say.
My abilities don’t lag at all.

Bump. That issue is still here, devs.

Btw are you experienced problem when was stomping a revenant?

Yup. Had this idiot engineer talk crap to me because of 2 failed stomps that look successful. Like being able to do a stomp requires some kind of skill if you aren’t interrupted. This crap needs to be fixed

Mak.2657:

Btw are you experienced problem when was stomping a revenant?

I am playing revenant and it happen with any class im trying to stomp at random times. I can try to stomp over and over without any result let it be warrior, engi, ranger or w/e. I do not use quickness as that thing is bugged as kitten when it comes to stomping. But now even normal ones fail.

Yes, I saw this too. Stomped an enemy, walked away for a second, then the enemy is dead. It has some sort of delayed activation.

I think it might be related to the way they change stomping so Thief skill can work.

Mak.2657:

Btw are you experienced problem when was stomping a revenant?

I actually have this issue only when stomping a revenant, playing one myself, too.

Most of my failed stomps caused by quickness (being not full duration of stomp) or by slow (e.g. revenant downed skill). Just need to wait another second to be secure stomp.
But some of my failed stomp tries wasn’t affected by quickness/slow if I recall right. I did it on practice dummies and sometimes even with additional seconds of waiting after landing stomp animation and sometimes without result. It wasn’t accurate test though.

I think the root of the problem is quickness and slow and how they glitch out the actual animation of stomping. Basically you just have to not pay attention to the animation anymore because they never sync up correctly, just watch to make sure there is a cast bar and the stomp will eventually go through after like a second of delay even if it doesnt sync up with the cast bar, just dont move

I’ve been having this issue too. Haven’t noticed it being related to quickness or slow though. Just seems to be a delay from when I finish the stomp and the enemy is actually finished.

The problem is that during that delay it’s still possible for them to rally. Had this happen a few times now where I finished a stomp, it wasn’t interrupted, and nothing happened; two seconds later they rallied off a dead ally.

Just wanted to resurrect this thread because of how hilariously broken stomping is. Time after time last night I’d execute a stomp…and nothing. Lost a couple fights because of this bug. I didn’t even have quickness on me these times, those ones always bug out.

Just an FYI it is the fact that the enemy is desynced and is not where the toon looks to be so u are out of range. The fact that the core function of pvp “stomping” is broken by desync makes the game mode a joke right now and i haven’t played it seriously from the first time is found it not working. so if this doesn’t get fixed then pvp doesn’t mean a thing. Plus if that can work like this is it really far fetched to thing to a do lag hacks by just suspending your router before going down and trolling this game? Just wanted to add the fact that i play engi and WITH elixir S it still happens so its not quickness tho quickness is delayed and rev quickness isn’t so ya =)

Same, I have experienced the same issue described in here. Pls fix this and at the same time the problem with quickness stomping.

I can’t imagine why this game hasn’t taken off as an esport.

cotton.3147:

Just an FYI it is the fact that the enemy is desynced

I know how desynced look and how it work. And explain me now.

When someone is desynced i cant cleave him in the place wheres hes supposed to be. If my ally is desynced i cant rez him too. In this situation howered my sotmp doesnt way to go off no matter what, yet i can cleave him in the spot where he is and ally can rez him there too. Its not desync in this case. Desync wont let me cleave him nor ally rez him.

cotton.3147:

Just an FYI it is the fact that the enemy is desynced and is not where the toon looks to be so u are out of range.

Not likely for most cases. When 1st attempt of stomping failed 2nd/3rd try at the same position usually helps. Seems like HoT issue.

Either you’re lagging, or the enemy is lagging. If its neither, go to your general options and see if your “Allow Skill Retargeting” is checked. If it is, and you swap to a different target while your stomp is still casting, the game will think you’re stomping the current target you have and ignore the one in downstate. Other than that, I haven’t had any issues with stomping.

NotoriousNaru.1705:

go to your general options and see if your “Allow Skill Retargeting” is checked. If it is, and you swap to a different target while your stomp is still casting, the game will think you’re stomping the current target you have and ignore the one in downstate.

+1
Probably you are right.

Imho it is not correct and should be fixed.

Hmm, checked it on dummies. Sometimes fails, sometimes not. Even with turned on option. Thus, not sure.

Hm, I always assumed it was a last second blind that negated my missed stomps. Are you sure you are not getting blinded?

Blind does not affect stopms.
Most likely new option is a reason.

Mak.2657:

cotton.3147:

Just an FYI it is the fact that the enemy is desynced and is not where the toon looks to be so u are out of range.

Not likely for most cases. When 1st attempt of stomping failed 2nd/3rd try at the same position usually helps. Seems like HoT issue.

Ya i could be wrong it’s just the only thing that made sense and when i fail the first one and go to the other side of the downed guy it normally works. So maybe the desync just catches up or something else happen ether way stomps SHOULD NOT be something that bugs out cuz it makes pvp a joke

Phobos.3197:

Eliminate downstate already.

I’m finally beginning to agree with this…

Had some issues as well.

To all:
uncheck “Allow Skill Retargeting” in general options (”Combat/Movement" section) and try to test.

Just disable down state all together, worst part of the game by far. In PvP.

Mak.2657:

To all:
uncheck “Allow Skill Retargeting” in general options (”Combat/Movement" section) and try to test.

I’ve never had that enabled, and my stomps still bug out regularly.

Hmm, I hope anet will fix it soon.

Laraley.7695:

Mak.2657:

Btw are you experienced problem when was stomping a revenant?

I actually have this issue only when stomping a revenant, playing one myself, too.

Yeah, an immediate stability stomp sometimes fails for no reason.

Just disable down state all together, worst part of the game by far. In PvP.

Why’s that? Many people find it awesome. I actually find it one of the best parts of the game.

Mak.2657:

To all:
uncheck “Allow Skill Retargeting” in general options (”Combat/Movement" section) and try to test.

This. Maybe it doesnt explain all stomp bugs, but as soon as I realised that retargeting when stomping will make my stomp to miss I usually dont have any problem for stomping

I’ve been playing Revenant alot in PvP the last couple days and have been seeing/having this problem ALOT. It’s true that Quickness/Slow royally kittens up stomping. I think the issue is when Quickness/Slow are applied/removed in the middle of a stomp animation. I’ll often try and stomp and accidently initiate the stomp before activating IO, which is where I’ve noticed I’m having the issue. The stomp animation will speed up and complete, but the stomp doesn’t go through until a couple moments later; the time it takes for a normal stomp, I assume.
I’ve also had a couple of hilarious but broken encounters whilst downed, the number of occasions I’ve had 2-3 opponents gathered around me continually missing stomps because I applied Slow on each them mid animation is insane. It’s gotten to the point where, against players unaware of the issue, I can stall stomps just long enough for a teammate to come over and rez and eventually end up winning the fight.
That’s my personal experience with it anyway, I’ve not encountered any issues with it where Quickness/Slow are not involved just yet thankfully. In any case though, it’s definitely something that needs to be fixed.

P.S. I also agree with the removal of downstate. I feel that it’s not necessary in a mode like PvP and simply provides crutches to larger groups and an even bigger disadvantage to outnumbered groups. It’s something I’ve been calling for alot in WvW as well, because it’s a problem there too. It’s frustrating when you clutch that 2v1, get both into downstate and they down you with #1 spam. You won the fight, but then… you lost it.

+1 also seen issues, thought i was interrupted at first but the feeling grew on me that something else was going on. most of the time as a revenant where i mix quick stomp with normal stomps.

Yep, stomping on my ranger has been a struggle. Finish the stomp, pole goes down through(nothing yet), stand there for a second for good measure. Guy still laying there on the ground unharmed…. continue to stand there confused as to what just happened. Then end up just cleaving..

Yes this is still a problem.

Has happened in a variety of situations and nothing to do with quickness or slow.

Can make a huge difference between winning or losing a teamfight and the match. As such I can’t take this game seriously until stomping is guaranteed to work every time.

Krysard.1364:

Mak.2657:

To all:
uncheck “Allow Skill Retargeting” in general options (”Combat/Movement" section) and try to test.

This. Maybe it doesnt explain all stomp bugs, but as soon as I realised that retargeting when stomping will make my stomp to miss I usually dont have any problem for stomping

This is a pain because one of my favourite things to do while stomping is to switch target to an enemy resser and interrupt them (Diversion) while finishing a downed opponent.

So you’re saying the reason it might be failing sometimes is because of switching targets?

Curunen.8729:

Krysard.1364:

Mak.2657:

To all:
uncheck “Allow Skill Retargeting” in general options (”Combat/Movement" section) and try to test.

This. Maybe it doesnt explain all stomp bugs, but as soon as I realised that retargeting when stomping will make my stomp to miss I usually dont have any problem for stomping

This is a pain because one of my favourite things to do while stomping is to switch target to an enemy resser and interrupt them (Diversion) while finishing a downed opponent.

So you’re saying the reason it might be failing sometimes is because of switching targets?

Yes, because skill retargeting, when switching targets you will “stomp” the current target, which makes you to fail the other stomp. Maybe Anet could fix this so if you retarget when stomping to someone who cant be stomped, it just stomps the first target, but I dunno if this is really hard to write when programming

Krysard.1364:

Curunen.8729:

Krysard.1364:

Mak.2657:

To all:
uncheck “Allow Skill Retargeting” in general options (”Combat/Movement" section) and try to test.

This. Maybe it doesnt explain all stomp bugs, but as soon as I realised that retargeting when stomping will make my stomp to miss I usually dont have any problem for stomping

This is a pain because one of my favourite things to do while stomping is to switch target to an enemy resser and interrupt them (Diversion) while finishing a downed opponent.

So you’re saying the reason it might be failing sometimes is because of switching targets?

Yes, because skill retargeting, when switching targets you will “stomp” the current target, which makes you to fail the other stomp. Maybe Anet could fix this so if you retarget when stomping to someone who cant be stomped, it just stomps the first target, but I dunno if this is really hard to write when programming

It used to always work for me whenever I did that in the past (swap target, F3, finish stomp), so it must be something that changed with HoT.

Bump. The problem is still there with normal stomps (tried the option mentioned in this thread). But most of all quick/slow stomps are bugged as kitten for far too long. Aiming for “esport” with such important yet so bugged mechanic is a joke.