Curse

Yanman.be · Dec 27, 2006, 02:34 PM // 14:34

I retired from HA because of this issue ( and many others ).

When other people rubberband, and they say it on vent, I never notice they rubberband so hard, it doesn't impact or gameplay. But when I rubberband, it's always an entire map, I get stuck behind enemy lines, and GG I'm dead.

Also happens when I can glitch between 2 rit spirts bodyblocking me from the rit owner. As soon as I can hit him, WHAM. Back to square 1.

Grolubao · Dec 27, 2006, 05:43 PM // 17:43

Yeah... HoH relics are pretty messed up

Ninna · Dec 27, 2006, 06:49 PM // 18:49

its been a problem since Prophecies (May 2005) for me

its rare tho

Lord Toast · Dec 27, 2006, 07:27 PM // 19:27

With all the people saying "oh just dont get bodyblocked"... the problem is that 99.9% of all teams in HA right now are this spirit junk. And when you are trying to run you undoubtedly run into a few spirits, which you are forced to run around. I get stuck on them all of the time.

count your fingers · Dec 27, 2006, 07:34 PM // 19:34

Quote:

Originally Posted by Divinus Stella

bind /stuck to a key using a third party program, then just mash it on relic runs, euro servers have been extra bad with rubber banding recently.

Yeah, I'm sure this would work, if only it wasn't against the rules. :P

I've had this problem too, and would have thought Anet would fix it by now since it affects PvP and PvE.

leeky baby · Dec 27, 2006, 07:44 PM // 19:44

ya iv had this alot tonight and the past week, neva had it before thou...i think with these heavy spirt builds does not help the problem ^^

nbajammer · Dec 27, 2006, 08:12 PM // 20:12

Ive had extreme lag problems since Nightfall's release, with more than my own fair share of rubber-banding. Guildie has Comcast cable, and hes got it too. I know it isnt my connection because I can surf the web fine. Other games do not lag. Only Guild Wars, and then only since the release of Nightfall. Hope Anet does something about this soon, because at times it makes the game impossible to play.

Randomway Ftw · Dec 27, 2006, 09:22 PM // 21:22

To whoever said don't get bodyblocked, its kind of difficult when you can't tell if your getting blocked or not, if you so much walk near someone you rubberband and realize your still at the stairs in Sacred Temples. It's retarted when your relic runner has to keep ask if where they are over vent.

Vinraith · Dec 27, 2006, 10:56 PM // 22:56

I'd always understood this to be a lag problem, and certainly I have been seeing more lag since Nightfall. Certainly it'd be nice to see that addressed, but surely it's very much on Anet's radar.

Mr_T_bot · Dec 27, 2006, 11:04 PM // 23:04

Poor pathing + poor character blocking + poor location detection = crappy PvP.

halbatross · Dec 28, 2006, 02:35 AM // 02:35

With this amount of players indicating it has only happened to them after the NF release I doubt this is lag-related... One of the recent updates must have changed something.

Divinus Stella · Dec 28, 2006, 04:07 AM // 04:07

Well its gotten a lot worse over xmas, lot more people playing. i dont really know much about the communication to the servers, but i get the feeling the character location isnt updated as often as usual, which causes small jumps all the time, where my character moves from its location on my screen to the location the server says its at. perhaps its something anet did to reduce server load at their end.

Shendaar · Dec 28, 2006, 04:25 AM // 04:25

I have been experiencing this "rubber-banding" effect on numerous occasion too. I must also say that I don't ever recall having this problem before the Nightfall release.

I would like to get an official word on this, as this is really an annoying glitch.

trobinson97 · Dec 28, 2006, 04:33 AM // 04:33

Well, it's happened to me before NF, but it was a long time ago. Around June of 05, during the Great Northern Wall mission, there was a period of about 10-15 minutes where I couldn't go anywhere. I'd move to a certain spot, only to be pulled back to my original spot. It had nothing to do with body blocking.

The same is here. I was doing a Do Not Touch run in the Forum Highlands. I killed the first group of Skree Harpies and kept going. After a few seconds, I get pulled back to the spot where I killed the harpies. THis happened 3 or 4 times. Maybe it could be because so many people are on for the event I don't know, but yeah it pretty much breaks the game for me.

unspokenglory · Dec 28, 2006, 04:45 AM // 04:45

ok here i sa simple way of ffixing it kinda .. say your runnign and your taking damage with no mosters around simply stop press c and use an attack skill it will shot u back to your position and will help you not to lose alot of life ^_^ its what i do not to die :P

shardfenix · Dec 28, 2006, 06:55 AM // 06:55

Quote:

Originally Posted by Lord Toast

I think that rubber-banding is probably the number one biggest issue in guild wars right now, and definetly needs to be fixed.

I think the broken metagame is a bigger issue than people who try to run through walls.

Quote:

Originally Posted by Lord Toast

As of right now, does anybody know any ways to avoid being rubber-banded?

Using a skill that has more than 0 cast time will set your character to where you actually are on your screen. If you think you may not be where you appear to be, cast healing touch on yourself, or start a signet and cancel it.

If you have no skills requiring activation time, press c and see where the closest enemy is.

Also, using the mouse cuts down on rubberbanding 99% because it forces anets servers to give your character pathing, whereas using the WADS ignores pathing.

Whiplashr · Dec 28, 2006, 07:06 AM // 07:06

For those who say it's not lag related.. I just don't know, because I have only ever seen this type of thing happen in online games (several of them over the years. This used to happen ALL THE TIME in Ultima Online when it first came out, and it was definately related to connectivity in that game).

I've never seen this happen in any single player games. And it seems to me that this is a case of .. you are moving, and you briefly lose a few packets from the server. So the server is not getting info on your real position from the client for a bit.. So the server thinks you are sitting still in your last known position, until the client and server manage to resync.. At that point, I assume the server over-rides the client to move you back to your last known, server approved position... or something like that