WoW Players Report Characters Fighting Bosses After Disconnecting

A peculiar discovery has surfaced within the World of Warcraft community this week following the release of patch Curse of Ula’tek 12.1. Multiple players have reported encountering a strange phenomenon: when their characters disconnect during dungeon encounters, rather than freezing in place or disappearing from the battlefield, the characters appear to continue engaging enemies autonomously. For a game built around player coordination and real-time control, this behavior represents something genuinely unexpected—and raises questions about whether it’s an intentional feature, an elaborate bug, or something else entirely.

The Reports Emerge From Myth+ Dungeons

The initial incident came to light on Reddit when a player shared video evidence from an M0 dungeon run. According to their account, they were grouped with an Evoker who disconnected approximately 39 seconds into a boss pull. While the player confirmed they had disconnected—and you can hear them announcing this fact—the video shows the Evoker character continuing to function, casting spells and performing actions as though controlled by an active player. The Evoker remained in the fight, clearly visible by its distinctive dragon wings, pressing abilities despite its controller being offline.

This wasn’t an isolated claim. The original Reddit post attracted multiple corroborations from players who reported witnessing or experiencing the same behavior themselves. One commenter described their brother’s experience in detail: the brother’s Warrior client crashed during a boss encounter, and the character remained active and fighting through nearly the entire boss fight. After approximately 30 seconds of being disconnected, the Warrior suddenly charged the boss and began attacking. The player noted their brother was actively narrating his re-login process, having forcibly closed the game with Alt+F4 and restarted it, only to watch his character continue fighting without his input.

Understanding What’s Actually Happening

Read also: Insomniac Explains Practical Design Behind Wolverine’s Self-Healing Suit · Twitch Forces AI Training on Creators, Admits No One Would Opt In · Insomniac’s Wolverine: Seven Key Details From Preview Coverage

The Botting Possibility and Why It Doesn’t Fit

The first question any seasoned WoW player might ask is whether this represents botting activity or some kind of exploit being disguised as a legitimate bug. One Reddit commenter did propose this theory, suggesting the video could be evidence of a player secretly running automated software. However, this explanation seems unlikely for practical reasons. Purposefully fabricating evidence of botting—a serious violation of Blizzard’s terms of service—would be an enormous risk for little to no benefit. The players posting these reports appear to be describing genuine mechanical behavior they encountered, not something they orchestrated themselves.

The Action Queue Theory

Another explanation gaining traction involves World of Warcraft’s one-button rotation feature, a relatively recent addition to the game. The theory suggests this system might be queuing up optimal actions in advance, and when a disconnect occurs, the character could be completing whatever commands remain in that queue before stopping. This would explain why the character performs specific actions—it’s simply finishing what was already set in motion before the connection dropped. However, observers who watched the video closely noted that the character in question appeared to be actively moving in response to the fight, not simply completing pre-queued actions. The fluidity of motion and decision-making suggested something more intelligent than a simple action buffer working through its list.

The Followers Mechanic as Possible Explanation

The most compelling theory centers on an existing World of Warcraft feature: the followers system. This mechanic allows players to complete easier dungeons by bringing NPC companions who fight alongside them or, in some configurations, fill dungeon slots entirely. The proposal is that upon a sudden disconnect, the game’s systems might be automatically converting the disconnected character into a temporary follower—an NPC under AI control that attempts to execute a roughly optimal rotation and navigate dungeon mechanics. If this were the case, the player would have a window of time to reconnect and regain control of their character while the NPC AI handles the combat temporarily.

On the surface, this would be a genuinely helpful feature. A player who unexpectedly loses connection wouldn’t immediately doom their group to failure. Instead of their character becoming deadweight, standing motionless while the boss attacks freely, the AI would keep the character mobile, casting abilities, and attempting to avoid mechanics. The group wouldn’t face the sudden loss of DPS or healing, and the player wouldn’t feel like they’d sabotaged their teammates through no fault of their own. For someone who has experienced the guilt of a mid-boss disconnection—the sinking feeling of letting your group down during a critical moment—such a safety mechanism would be welcome.

The Exploitation Problem and Blizzard’s Silence

Yet there’s a significant problem with this theory, one that points toward this being an unintended bug rather than a feature. If Blizzard had intentionally implemented a system allowing characters to fight autonomously after disconnects, you would expect the company to announce it. Major gameplay changes, especially ones affecting dungeon mechanics and group dynamics, warrant explanation. The absence of any official announcement about this behavior suggests it’s more likely a glitch that emerged during the Curse of Ula’tek 12.1 patch development.

The exploitation angle is equally troubling. If players discovered that they could reliably trigger this behavior—deliberately timing a disconnect or network interruption to activate NPC control—the system could be abused. A player could potentially have their character continue fighting while they handle real-world tasks, essentially farming dungeons passively. They could also manipulate disconnections strategically during difficult mechanics, letting the AI handle dangerous portions of fights while they step away. The potential for abuse is substantial enough that Blizzard might have intentionally kept quiet about the feature, even if real, to avoid drawing attention to it.

Waiting for Official Clarification

As of now, Blizzard Entertainment has not publicly commented on these reports. The developers have been contacted for clarification about whether this behavior is real, intentional, or something they’re investigating. Until an official statement emerges, players are left to speculate based on video evidence and secondhand accounts. What seems clear is that something unexpected is happening within dungeons during disconnection events—the community reports are too consistent and detailed to dismiss entirely.

For the broader WoW community, this incident highlights how even massive, well-established MMOs can produce genuinely surprising behavior. Whether this turns out to be an elaborate safety feature, an accidental bug waiting to be patched, or something else entirely, it’s a reminder that thousands of players engaging with the same game world can surface behaviors the developers didn’t anticipate or highlight. The coming days will likely bring either an official explanation from Blizzard or a hotfix that removes the behavior—at which point players will finally know whether they witnessed intentional design or an accidental quirk of the game engine.