WoW Players Are Disconnecting, And Their Characters Keep Fighting Without Them

Normally, when somebody disconnects in the middle of a World of Warcraft dungeon, you know exactly what happens. Their character stops moving. Maybe it runs heroically into a wall. Maybe it stands perfectly still while the boss converts it into a decorative floor stain. Since Patch 12.1 arrived, however, players have started reporting something considerably stranger. Their disconnected friends are apparently continuing to fight. Not lagging. Not finishing one queued spell. Actually moving, casting abilities and participating in combat while the player is no longer connected. A Reddit video posted by Stuperstrong shows an Evoker disconnect during a Mythic 0 dungeon, stop briefly, and then resume casting and fighting. The player says it happened twice, in King's Rest and Ruby Life Pools, and that deliberately testing it with Alt+F4 produced the same result. And nobody seems entirely sure why.

The Evoker Just Started Playing Again

The video is what makes this story considerably more interesting than another collection of “something weird happened in WoW” forum posts. Around 39 seconds into the footage, the Evoker appears to lose connection. There is the familiar pause. The character stops responding normally. Then it starts participating again. Abilities fire. The character moves. Combat continues. According to the person recording it, their friend was genuinely disconnected at the time. They later repeated the test by intentionally closing the game with Alt+F4, and the character once again continued participating in combat. That is difficult to explain with ordinary latency. A delayed spell cast is one thing. A character deciding that the dungeon must continue regardless of whether its owner is currently present is another.

Other Players Say They Have Seen It Too

The original report quickly attracted players describing similar experiences. One player said their brother's Warrior crashed during a boss fight while they were talking together on Discord. The Warrior initially remained idle, but roughly 30 seconds later it reportedly charged the boss and began attacking while the actual player was still narrating his attempt to log back in. Another player described seeing a disconnected Hunter continue jumping around and participating in combat before the real player returned. Yet another claimed a Protection Paladin had used defensive abilities while disconnected during PTR testing. These remain community reports rather than Blizzard-confirmed documentation, but there are now enough similar accounts for the phenomenon to be difficult to dismiss as one player's unusual connection problem.

Is WoW Using Follower Dungeon Tech During Disconnects?

The obvious theory is that Blizzard may be experimenting with some form of disconnect protection. World of Warcraft already knows how to control player-like characters. Follower Dungeons use NPC companions capable of tanking, healing, dealing damage, following mechanics and generally doing a respectable impression of people who have read the dungeon journal. So the technology exists for the game to temporarily replace a missing player with automated behavior. Using something similar when somebody disconnects would make a certain amount of sense. Instead of instantly reducing a five-player dungeon to four people because someone's router has decided to explore the Twisting Nether, the character could continue performing a basic rotation until its owner reconnects. PC Gamer raised exactly that possibility when examining the reports. There is just one fairly important problem. Blizzard has not said that is what this is.

Blizzard Hasn't Announced Any Disconnect Protection

There is currently no official Blizzard announcement describing a system where disconnected characters are taken over by bots, follower NPC logic or anything else. The behavior also does not appear in the Patch 12.1 feature announcements. Discussion has now reached Blizzard's own forums, where players are debating whether this is an intentional disconnect system, a bug or simply automation being triggered unexpectedly. But those discussions are from players, not Blizzard developers confirming the feature. That distinction matters. Calling this “Blizzard's new AI feature” would be getting well ahead of the evidence. We know characters have apparently continued fighting after their players disconnected. We do not yet know why.

And Calling It AI May Be Getting Ahead of Ourselves

There is another slightly amusing part of the discussion. Everyone immediately started calling it AI. It might not be. Even if Blizzard is intentionally controlling disconnected characters, a system like this could simply be scripted combat logic similar to existing NPC companions. It would not require machine learning, a sentient Mage or Microsoft's latest attempt to put Copilot inside your toaster. Players on Blizzard's forums have already pointed out that automated NPC behavior has existed in games for decades. So until Blizzard explains it, “automated character behavior” is probably the safer description. Slightly less exciting. Considerably less likely to result in headlines about your Paladin achieving consciousness.

If It Is Intentional, It Could Actually Be Extremely Useful

The funny thing is that if this really is experimental disconnect protection, it is not necessarily a bad idea. Anyone who has played Mythic+ knows the familiar disaster. Someone disconnects during a boss. The group keeps going. Their character dies. The timer keeps running. Four people begin staring angrily at a motionless avatar as though intimidation might repair an internet connection. A basic automated stand-in would not need to play perfectly. It would merely need to survive, press some buttons and prevent a temporary connection issue from immediately destroying the run. Of course, that raises other questions. Could players deliberately disconnect to let automation handle mechanics? How long would the game control the character? Would it work in raids? Mythic+? PvP? Could it use cooldowns? Could the bot somehow be better than the player? That last one is probably the question nobody wants answered.

For Now, WoW Has a Ghost in the Machine

At the moment, we have videos. We have multiple player reports. We have a growing discussion on Blizzard's own forums. What we do not have is an explanation from Blizzard. Maybe Patch 12.1 quietly contains an early disconnect-protection system. Maybe some existing follower technology is activating where it should not. Maybe it is simply a very strange server-side bug. Until Blizzard says something, all three possibilities remain more sensible than pretending we know. But one thing appears increasingly clear: If your friend disconnects in a WoW dungeon and keeps doing damage, do not immediately celebrate their miraculous internet recovery. They may not actually be back. Their character just has places to be.