Your friend alt-tabbed out ten minutes ago. Their character is still moving. The WoW ghost character bug threads all describe the same thing: disconnected characters that keep walking, turning and pulling packs while the person behind them sits at a login screen. It looks like a haunting. It reads like desync, and inside a timed key that distinction decides your run.
What the WoW Ghost Character Bug Reports Actually Show
The pattern is consistent across every thread. A party member drops connection, their body stays loaded in the world, and instead of standing still it walks. Some reports have the character turning to face threats. Others have it drifting forward into a pack the group had not pulled yet.
Nobody is at the keyboard. The server is still running an actor that behaves like a player.
Capture the Timestamp Before You Leave the Instance
If a ghost body moves in your group, grab the combat log timestamp and the party member's realm before you leave the instance. Blizzard triages desync reports far faster when the report carries an instance ID and a time window. Vague reports get closed without a fix.
Why This Reads as Server Desync, Not a Haunting
Server-side desync explains almost all of it. When a client drops, the server holds the character in the world for a grace window so a fast reconnect does not cost you your spot. During that window it keeps simulating the actor, and any queued movement finishes executing with nobody behind it.
That is why the movement looks purposeful. It is the tail end of real input, replayed by a server that has not released the body yet. A bot would not stop the instant the window expires. These do.
The Mythic Plus Cost of a Body You Cannot Control
In open world content a walking ghost is a story you retell in guild chat. Inside a timed key it is a wipe.
A body the server still owns holds threat, breaks crowd control, and drags a patrol into your pull. Your tank watches a pack turn for no reason. The timer keeps running while five people argue about a mistake none of them made.
Progression raiding carries the same risk on a longer fuse. Soak assignments assume every body in the room answers to a person.
Why a Pro Calls This Before the Wipe
Reading a desync live is pattern recognition, not game knowledge. GG Clan's Mythic+ specialists have run enough broken pulls to name the second a body stops answering, then reroute the group instead of resetting the key. Those seconds are the entire margin on a high key.
How Disconnect Handling Works in Retail WoW
Retail never hard-deletes a disconnected character on the spot. The server keeps it loaded so reconnects, phase transitions and instance handoffs stay seamless. That grace window is why you can drop mid-boss, log back in, and land exactly where you left off.
The window is short and invisible to everyone else in the group. Nothing in the interface tells you a body has lost its owner.
How to Play Around a Desync Window in a Timed Key
Treat a frozen name plate as intel. The moment a party member's frame greys out or their movement goes smooth and mechanical, stop planning around them.
Call it out loud. Reroute the pull away from the body. If the ghost holds threat, taunt off rather than fighting the pathing. On a raid boss, hand their soak or their interrupt to a living player before the next cast.
Every second the group spends deciding is a second the timer takes.
Assign Interrupt Backups Before the Cast
Name a backup on every interrupt rotation at the start of the key. When a body goes silent mid pull, the backup already knows the kick belongs to them. Groups that assign this in advance recover from a disconnect without dropping a single cast.
Tags
Share