Horrible Rubberbanding only when Body Blocked!?

Not much to this, just as the title says. I occassionaly suffer from terrible rubberbanding (about 4 seconds worth) however I've noticed it only EVER happens when I am body blocked by either a group of enemies or a single enemy and a wall.

Happens in both PvP and PvE.

Just wondering if anyone else has noticed the same.

I play with a reasonably high ping because I'm in Australia (averages 300-500ms) which I suppose could be the culprit.

Yes, me too. I experienced it this weekend in HA (the first time I arrive to HoH, I solo capped a shirne, ran away from enemies, and pluf! I was back, bodyblocked and almost dead.), in AB, and in PvE while running through silent surf on cantha.

Same here, has been happening since i started playing 2 years ago and i dont think my ping is the problem, I ping around 50 normally. This really does need to be fixed, but I doubt it ever will.

The problem occurs when the server and client disagree about the position of the player. The client decided that the player was not body blocked while the server thinks otherwise. The result is that after some time the server overrules the player's position.


Or maybe it just was a ranger using a 'Rubber Band Trap' ;-)

/stuck is your friend, learn to use it like the rest of the community have

And how is that? I'm not stuck until after I rubberband.

You're missing the point. A game bug means that the server has your character in one place and your client shows your character in another. This means that the player can't act/react appropriately. Using /stuck works to align the server and client but it might be too late and your character dies.

It's annoying in PvE and a killer in PvP, that has been around since 2005. It happens with and without lag.

As explained, this doesn't have anything to do with lag or ping. It is known as 'desync' when the predictive position algorithm on your client and on the server disagree on character positions by a minute amount at a crucial moment, the result being that your character gets bodyblocked on the server but not on the client. It may be quite persistent, even way past radar range and the most obvious signs of a desync are the lack of mobs (since servers spare resources by only creating mobs as a player gets close enough to their spawning point) and/or getting attacked by 'invisible' monsters (since the server thinks that they reach you and sends hit events to the client which shows them despite the respective monsters apparently being elsewhere - that is a common occurrence when corralling raptor nestlings). The /stuck command forces a resync, i.e., the actual state is sent from the server to the client.

At the root of the issue is the way GW manages player interaction with the game world. To conserve bandwidth the client is relatively autonomous and full status check is done quite seldom.

What's fascinating about this is the fact it happens (for me at least) at same locations and in same situations. Like aggroing all 3 groups of Grasping Darknesses in UW and aggroing all Raptor Nestlings. It's really fun to watch yourself casting Radiation Field, only to see it two aggro bubbles behind.

Anet make it happen in uw 90% for the lulz !

I believe it's because there is a time delay between using the Keyboard for movement, and the Mouse for movement, so if you click, you don't get bodyblocked as the client reacts faster to the server, as opposed to the Keyboard...

Another fantastic 'feature' Anet included in their awesome game.

As said above the solutions are:

1. Type /stuck ,it will 'teleport' you to your correct place on the server
2. Click to move and it shouldnt really happen much

It happens to me sometime mainly when i'm running, but since i have 300~400ms ping i thought that that happened because of my ping, but you guys are saying that this problem is not because of the ping...

BTW, i tryied /stuck before, it doesn't works...

why are you guys talking about the /stuck command? It's clear from people's descriptions of the issue (and I've seen it firsthand as well) you don't know you're stuck till the rubberband has already occurred and at that point you're screwed. Clearly the /stuck being the fix for this is, as Gaille would say, not an elegant solution to the problem.....

i think /stuck works only when the game is glitched and you cant move anywhere, not cause you are body blocked... like when u run relics and ur body is stuck in between the bridge in burial mounds or something. Body blocks are legit and can be done.

Or 3. they can fix it.
Just a thought.

I agree on that. I got killed so many times by a particular group of Aatxes while running to the Ice Wastes... I now make sure they are well out of my range before I rush through. It always happens at the same spot, so I now know how to avoid the Rubberbanding 'o Death.

I hate it when they use those.

Yeah, I've noticed it is really bad in UW when doing the 'clearing the chamber' quest, I'll often group a few together, skip past them, and then be unable to agro anything else as I stand around waiting to suddenly teleport back to them.

You always know there is trouble when you start a casting animation and continue moving at the same speed.

This is not a bug per se but instead an unavoidable consequence of game design decisions. ANet could 'fix' the issue any time at the cost of (a) requiring high speed DSL to play the game and (b) radically increasing the amount of servers/server bandwidth. Unfortunately, that would cost a lot of money that players are not throwing in on a monthly basis as is the case with many other online games. Would you tolerate, e.g., in-game product placement as an additional source of revenue, just to fix a minor issue?

The /stuck command was implemented for a completely different issue and it is only applicable here because one of the things that it does is a resync which resolves the desync.

The real thing is that most of the times when you realize that you are in the limbo, it's too late to /stuck.