Guild Wars 2

Does it happen because I have change attack to new target enabled, so it tries to stomp my new target instead of stomping who I pressed F on?

Its because the person you are trying to stomp has horrible latency. When this happens you gotta move in the direction they were moving before you downed them and try again. If youre in doubt as to where they are, use a projectile or auto attack without moving to “ping” their direction.

To me what is happening is the stomp fails when I am using quickness.

Using a ranged attack on the downed enemy will show you their actual location usually (follow the projectile location)

It is a lag/latency issue, it happens alot when people are in mid-jump, or falling from a ledge when being downed.

Coelho Nat.4697:

To me what is happening is the stomp fails when I am using quickness.

Depends on when you activated the stomp, you will speed up the animation, but the timer will remain the same when you activate it before quickness (this is being removed from play on the 26th anyways, so quickness stomps won’t exist anymore)

I’m of the impression it has something to do with the coding of ’interactions’’ and this cause some sort of desync. PvE communes come to mind at first. This thought process has been even more cemented, imo, b/c the Devs would rather go through and recode which ‘skills+stomps/rezzes’ can even be affected by quickness/slow. I’m no programmer, but it seems like logic and experience support this case.

sometimes the player isn’t down where they appear to be. when I use a movement skill they are somewhere else and I have to cleave the air where they supposedly are.

Stand The Wall.6987:

Its because the person you are trying to stomp has horrible latency. When this happens you gotta move in the direction they were moving before you downed them and try again. If youre in doubt as to where they are, use a projectile or auto attack without moving to “ping” their direction.

This isn’t an issue of latency as, after you fail the stomp, you can still cleave the body lying right in front of you. You can even get the stomp on a second or third try after quickness/slow have dissipated. Server desync is much easier to detect client side just by cleaving or dropping AoE in the general area.

I like that momentary pause in the middle of a big fight.

Where you wait to see if you really did stomp your opponent.

xD

I have had several stomps fail from what appears to be Quickness, the entire animation completes with the golden ball (the thing that really dictates the stomp not your model) hitting the ground and doesn’t finish. This is not me being unsure as to when the finish should complete, I even don’t move after for a few seconds but the target isn’t stomped.

This could be latency but it is happening FAR more frequently atm than used to.

mrauls.6519:

Does it happen because I have change attack to new target enabled, so it tries to stomp my new target instead of stomping who I pressed F on?

There isn’t any one reason for stomps to be bugged. This is one of them, but not the only reason. Don’t change targets if you are using that option.

Tman.6349:

This isn’t an issue of latency as, after you fail the stomp, you can still cleave the body lying right in front of you. You can even get the stomp on a second or third try after quickness/slow have dissipated. Server desync is much easier to detect client side just by cleaving or dropping AoE in the general area.

Oh I didnt know that. Interesting. Must be embarrassing if it ever happens live on twitch.

Desyncs have caused me so many pains though….