horde vanish concern!!!

[falinx]

Hey everybody,

something is up. this weekend and only this week during bg's this happened to me twice. I am alliance rogue and I jumped a hunter hordie on horseback and was about to kill him when he vanished. Didn't dismount, just literally vanished. Then a couple of hours later I jump a hordie while mounted, it starts running away and next thing it vanishes. So I'm like sitting there going wtf, so I start searching the area and using perception to no avail. It's one of those hmmm moments then while I'm creeping away, I notice that not like 30 seconds it reappears still mounted and rides off into the distance. Anyone seen this? What gives?

[mmorpg man]

which BG was this in?

[Zachariah]

Before you go crying wolf, it's worth bearing in mind that any sort of lag or timing discrepancy can easily give rise to this sort of experience. And before you say "But I wasn't lagging!", I mean THEIR lag.

I often find myself right behind someone in a BG, chasing them up and down hills, yet am constantly being told on-screen that they are out of melee range. What you see, what they see and what the server decides is the truth are not the same thing.

[WatcherZero]

They could be doing the trick of killing the client with an alt-f4 or ctrl-alt-del then logging back in.

[falinx]

It was AV on the sylvanas realm. If it was caused by lag they must have a ping time of around 30000 ... and I don't think that's possible :)

[TPMdm]

......If it was caused by lag they must have a ping time of around 30000 ...

They must? Who decided this? It actually doesn't take much to cause the type of behaviour you saw. You've never had a mob evade who was standing right in front of you? You've never been unable to loot a corpse that was right in front of you because "You're too far away"? Those mobs and corpses had a lag of 30000 while actually living on the server? :wink:

We throw the word "lag" around to describe many different performance issues: high latency, lost packets, unresponsive server, client/server miscommunication.....

[PlayThemAll]

Sometimes I think the server client sync gets screwed up. I've had several times where I didn't appear to lag but could not loot bodies because they said I was to far away. A simple log off and back on seems to resync things and everything is fine.

[WatcherZero]

yeah you log back in and their bodies in a totally diffrent place :)
Its the pain of both the client and the server controlling things, when a desync happens its chaos.

[falinx]

Sure I understand this but I have been playing for more than 2 years now and this is the first time I've seen this sort of thing happen. yes, I've seen the running on the spot action, the B line eternal jog, and the hey I'm dc'ing someone smash my skull in behaviour. I'm actually going to get a friend of mine to do the ctrl alt del thing to see if that's what it was. Hopefully it was. Cause I'm certainly going to use that trick in future... heh heh, me liiiike :)

[Kasal]

They could be doing the trick of killing the client with an alt-f4 or ctrl-alt-del then logging back in.

That was my first guess.

[irogue]

They could be doing the trick of killing the client with an alt-f4 or ctrl-alt-del then logging back in.

I think it is more of a "disconnect" issue.

I believe if you unplug your internet connection or alt+f4, your body would stay on the server (AFK) for at least 20 seconds like when you log out outside of an inn or a major city.

If you can't kill that logging out AFK ppl in 20 seconds, it will disappear.

It seemed that the 2 hordies op was killing got disconnected before he jumped on them. I don't think a rogue has any problem killing any AFKer in 20 seconds.

[Cerberus]

Feign death and joining another BG that pops up would do the trick. Sounds like the most plausible explanation to me.

Invisibility pots should work as well if someone actually bothered to go that far.

[Justinledwards]

I like Cerberus' explanation - another queue popped and off they went.

[Trakamoocow]

Cant believe it took 11 posts to get to the most obvious answer. And I see that ALL the time. Hay better queue popped/this bg sucks *clicky*

[mmorpg man]

but then the OP said they came back a moment later. how do you explain that?

[irogue]

Cant believe it took 11 posts to get to the most obvious answer. And I see that ALL the time. Hay better queue popped/this bg sucks *clicky*

You can't queue out when you are engaging battle....

/sigh

[Cerberus]

You can't queue out when you are engaging battle....

/sigh


You can if you leave combat by feigning.

If they reappeared I suppose a dodgy connection could make you fade in and out. I wouldn't rule out the possibility of a trick that makes you do this. A hack or messing with the connection in some other way could log you out and get you back in in a matter of seconds on a decent computer. As I'm writing this I just realized how to do this and I'm not sure I want to type it out ;)

[WatcherZero]

err yeah, we mentioned it earlier, kill the client, you can also pull the plug on your modem which ive been known to do in really really useless pugs.

[Cerberus]

That would keep you logged in for 20 seconds and get you killed. People that DC and manage to log in before the 20 seconds are up won't disappear ingame unless they get a forced DC on Blizzards end. I see this all the time in raids. The person remains ingame and gets parasites, doom, shadow of death air burst+grip etc ;)

There is another way that will DC you instantly and can be done on your end and there may be more methods as well.

[mmorpg man]

You can't queue out when you are engaging battle....

/sigh

if you are in a queue for AV and WSG and you enter a battle for AV, you will still be in the queue for WSG

[elsegundo]

its lag i tell you... lag.

[zodiac66]

Nah, it is a super secret Horde ploy to get Alliance all riled up :rolleyes:.

Its lag.

[irogue]

if you are in a queue for AV and WSG and you enter a battle for AV, you will still be in the queue for WSG

Sorry, I meant to say engaging combat meaning attack or being attacked. You can't hop around BGs unless you are out of combat.

[fallenxangel]

I've also used alt+F4, but it logged me out instantly which allowed me to log right back in. Lagging would cause you to be in-game longer (taking longer to log out) which could get you killed (happened to me before). And if they were lagging, but logged out to them, wouldn't they have been standing still? And logging out on mount then when logged back in with mount wouldn't be because of disconnection, they would've had to press Ctrl+Alt+Delete and/or Alt+F4. So lagging could be a reason for a little bit of not being able to attack them, but logging in and out of game on a mount would have to be from something other than lagging.