Guild Wars 2

You know…..those people who are downed. But you can’t target them, or attack them.

wtf is up with that?

Apparently…. it seems to happen lot more during competition. What is it that I don’t know about this?

I’d love to not die as well. How does it work?

It seems to be lag related.

Basically they are not lying down on the location shown ingame. They can still be killed if you find the real location.

btw: They can’t be rezzed too, so also a disadvantage.

Desync position.

Good AoE spam can fix it

Hit them with a projectile and go to where it landed. Sometimes it’s close enough to the position you see them on your screen and you can interact to stomp, other times you just have to cleave.

The problem is the UI to interact with the downed (be it a stomp or a res) will appear only if you are close to their apparent position, but will trigger only if your are close to ther real position.
When interacting, your character will automatically turn towards the real body. What I usually do is moving in that direction a bit while spamming the interaction button: most of the times, the apparent and real positions are close enough that I’ll find a point where my stomp/res will trigger

makes sense, thanks everyone

Definitely connection related. I was in a game where my connection wasn’t all too great (satellite internet). When I got downed they were probably 900 yards away (not exaggerating, they were incredibly far). Saw the poor chaps stomp and cleave like there was no tomorrow. I don’t remember it ever happening again so it must be a rare occurrence.

While it is related to latency to a certain extent, it is absolutely a bug, and a fault on the net code’s part. Upon being downed, the downed character’s position should be sent to all clients within render distance, but it isn’t.

I’m wondering if they ever intend to fix bugs like these. They’re game breaking, extremely easy to fix, and yet, they’ve have been around since day one.

Rangelost.4857:

While it is related to latency to a certain extent, it is absolutely a bug, and a fault on the net code’s part. Upon being downed, the downed character’s position should be sent to all clients within render distance, but it isn’t.

I’m wondering if they ever intend to fix bugs like these. They’re game breaking, extremely easy to fix, and yet, they’ve have been around since day one.

No this is worse than last year. Nowadays it like every bloody fight I’m in. I try to pull someone to get a burst off and they don’t go the full distance, then they teleport all over the place and I miss my burst. Then when I eventually down them, I have to use magical mathematics to stomp them.

Nope, something definitely happened between December and February because it’s a lot worse now than it was before.

I wonder if there is a way to “play” with the cable once down to force “lag” and abuse it to stay un-stompable while downed.

maddoctor.2738:

I wonder if there is a way to “play” with the cable once down to force “lag” and abuse it to stay un-stompable while downed.

You’d also be unrezzable but totally cleavable.

Tao.5096:

Desync position.

Also note, this can be done purposely as a really simple hack in some games, for instance you could do this in the original halo over XBL just by metering your bandwidth up and down. I’m not sure if you can do it here in GW2, but I’d watch anyone who does this consistently when it isn’t happening to anyone else on the map.

maddoctor.2738:

I wonder if there is a way to “play” with the cable once down to force “lag” and abuse it to stay un-stompable while downed.

Conncept.7638:

I’m not sure if you can do it here in GW2, but I’d watch anyone who does this consistently when it isn’t happening to anyone else on the map.

It’s called a lag switch, and it can be used to cheat in any game that has major netcode flaws, such as Guild Wars 2.