Guild Wars 2

No, you were not. You were downed again just before you got finished. I DL, ed the video, played in slomo to see.

Yeah, you can see your character get downed (the red “Fight for survival!” message appears) right before the enemy player completes the “Finish”.

Have you watched your own video? Doesn’t seem so.

TheQuickFox.3826:

You were downed again just before you got finished.

^this

Yea get downed to many times in a row and your insta dead no news here.

The person started the stomp before I was up again. Which should’ve reset it. Or were you all going to ignore that?

He was up, with very low health then there’s red damage numbers and he’s downed, looks like he died and the stomp started and finished.

What else does he want us to see?

Edit: up. Damage, downed, stomp starts, he died, stomp finishes. is what I saw.

Just a flesh wound.3589:

He was up, with very low health then there’s red damage numbers and he’s downed, looks like he died and the stomp started and finished.

What else does he want us to see?

Edit: up. Damage, downed, stomped is what I saw.

If you slow it down you see the stomp started before he was up. then he was downed right when the stomp finished. The stomp shouldn’t have still worked through him being up and downed again. I know when I try to stomp and the person gets up the stomp resets. This time it didn’t. And you can tell the stomp went through because of the stomp animation. The mage or whatever it is. I think maybe this is an issue of lag perhaps.

charrboiledeggs.8164:

Just a flesh wound.3589:

He was up, with very low health then there’s red damage numbers and he’s downed, looks like he died and the stomp started and finished.

What else does he want us to see?

Edit: up. Damage, downed, stomped is what I saw.

If you slow it down you see the stomp started before he was up. then he was downed right when the stomp finished. The stomp shouldn’t have still worked through him being up and downed again. I know when I try to stomp and the person gets up the stomp resets. This time it didn’t. I think maybe this is an issue of lag perhaps.

It’s pretty close together in time but there was red damage numbers immediately before the stomp starts. I’d guess lag.

However if he thinks there’s a problem then he should take his video and log to support. It’s not like he’s going to get an answer or satisfaction on the forum.

Nocturnal Lunacy.8563:

The person started the stomp before I was up again. Which should’ve reset it. Or were you all going to ignore that?

You seem to not understand how stomping works. It doesn’t really matter when how or why he began stomping, what matters is that he finished the stomp within range of you while you were downed.

Should stomping work like that? That’s up to debate. Feel free to suggest to Anet how to rework it, all players have the freedom to provide suggestions and feedback. But at this very moment, the stomping funcionality works EXACTLY the way it was intended to, because the devs programmed it this way.

Tarasicodissa.7084:

Nocturnal Lunacy.8563:

The person started the stomp before I was up again. Which should’ve reset it. Or were you all going to ignore that?

You seem to not understand how stomping works. It doesn’t really matter when how or why he began stomping, what matters is that he finished the stomp within range of you while you were downed.

Should stomping work like that? That’s up to debate. Feel free to suggest to Anet how to rework it, all players have the freedom to provide suggestions and feedback. But at this very moment, the stomping funcionality works EXACTLY the way it was intended to, because the devs programmed it this way.

Actually, when I rallied the stomp should’ve reset. The stomp is not working EXACTLY the way it is intended. So it’s obv you don’t seem to know how stomping works.

From the wiki

A finisher is an action in PvP play that is used to finish an opponent while they are in a downed state. This will immediately put the enemy in a defeated state regardless of their health while downed. When near a downed enemy, the message F “FINISH THEM!!” is displayed. Interacting begins an action similar to a channelled skill which takes 3.5 seconds to execute. Moving or being disabled will interrupt this action, but taking damage will not. The finishing activation can’t be reduced with quickness.

I don’t see why that means that “rallying” will interrupt the channeling. There’s a game design question about whether rallying briefly should interrupt the stomp. My guess is that ANet didn’t encounter the scenario when designing/playtesting… so it’s not as intended nor a bug.

In ANet’s shoes, I don’t think I’d change it. I’m not against the logic that “rallying should interrupt stomping” — I just don’t think it’s worth ANet’s time to change it for such a rare situation. Arguably, if the victim is too weak to stay up during the short channeling period, their opponents ‘earned’ the stomp by downing them again so quickly.

Otherwise, you could have a situation in which it’s actually advantageous to go down and rally in exceptionally dangerous areas — you end up with an extra chance to escape, which doesn’t seem “fair” to the stomping side.

tl;dr doesn’t seem like a bug. Doesn’t seem like it was deliberately programmed either. I’m not altogether sure that it’s worth changing; there’s also an argument to be made that it’s logical the way it is.

If a player was downed and then he gets “rally” when you’re stomping, the stomping will countinue until you cancel it, the only difference is that the finisher animation will not appear when you stomp the ground. It makes sense to be this way, it’s a movement of stomping something below you, doesn’t matter if you’re stomping the ground (when a thief uses his 2, or when someone defeat the downed player before you finish him, for example) or if there’s a player downed.