WoW 12.1: Evokers Hit by Stuck Disintegrate Beams and Disconnect Combat Bug

World of Warcraft’s Evoker class is having a rough patch cycle. Since Patch 12.1, Curse of Ula’tek, went live, players have logged two separate and possibly related bugs: Disintegrate beams that lock onto corpses instead of shutting off, and a stranger issue where disconnected characters, Evokers included, keep fighting for tens of seconds after the player has left the client.

Patch 12.1 deployed during the August 12-13, 2026 regional window, ahead of Midnight Season 2 on August 18. Bug reports on Blizzard’s official forums began stacking up almost immediately.

Disintegrate Beams Won’t Let Go of Dead Mobs

The first thread, filed on the Blizzard forums under “Permanent Disintegrate Visual on Evoker,” describes the spell’s beam effect forming between an Evoker’s chest and a mob that is already dead. The Evoker reported that during combat, after combat, or just randomly when running past a deceased mob, the Disintegrate visual will form between the character’s chest and the mob.

A follow-up report on the forums, titled “Disintegrate Visual Effect Bug, Possibly Causes Disconnects,” adds detail on how the beams behave once stuck. The player wrote that Disintegrate’s beams sometimes fire at dead enemies’ bodies the Evoker had previously defeated, regardless of range, until the bodies despawn. The poster admitted the trigger is inconsistent, noting they could not replicate it consistently and had no idea what causes it to happen exactly.

What makes the bug more than cosmetic is the possible knock-on effect. The same forum post claims that stacking several broken beams can crash the client outright: there are reports of the issue causing disconnects if four or five Disintegrate beams get stuck on dead bodies at once. A separate thread on the official forums, simply titled “Disintegrate bug,” shows the problem is not isolated to one player, with a second poster describing their Disintegrate animation bugging out and staying attached to dead mobs, with as many as four beams stretching roughly 50 yards.

Read also: WoW: Guild 清水 Claims World First Heroic Kill of Ula’tek in Venomous Abyss

Disconnected Characters Keep Fighting for Up to 39 Seconds

The second, more widely reported bug has nothing to do with visuals and everything to do with what happens after a player’s connection actually drops. PC Gamer, citing a report first surfaced by Kotaku, wrote that since WoW: Midnight’s 12.1 patch dropped, players have started reporting uncanny behavior from disconnected fellows, with characters seemingly moving and fighting on their own rather than going unresponsive.

The clearest documentation came from a Reddit user. PC Gamer noted that redditor Stuperstrong shared a YouTube video on the WoW subreddit recorded of their Evoker friend disconnecting and continuing to participate in combat. In the clip, the dragon-winged Evoker shows the typical signs of a mid-encounter connection drop at around the 39-second mark, and then starts fighting again.

BlizzPro corroborated the account independently, reporting that someone disconnects, or deliberately Alt+F4s out of the game, and their character continues to move, cast spells, and participate in combat for a noticeable period afterward, with one player documenting their friend’s Evoker disconnecting around the 39-second mark of a dungeon run before continuing to cast abilities and fight enemies. The same outlet added that the tester tried it again with a forced disconnect and got the same result.

Evoker Cases Are the Clearest Examples of a Wider Problem

The disconnect glitch is not confined to a single class. BlizzPro’s testing notes referenced other affected roles beyond the Evoker footage that made the bug famous. Reports of a warrior continuing to auto-attack and charge a boss after losing connection have circulated on the WoW subreddit alongside the original Evoker clip, and both cases were traced to instanced group content, specifically Mythic 0 dungeon pulls in King’s Rest and Ruby Life Pools.

What ties both bugs together, at least circumstantially, is timing. Both surfaced within days of the same patch and both involve Evoker characters as the most visible examples, even though the disconnect issue reportedly affects other classes too. Whether the stuck Disintegrate beams and the phantom post-disconnect combat share a root cause in the patch’s networking or visual-effects code has not been confirmed by Blizzard.

No Blizzard Statement Yet as Midnight Season 2 Approaches

As of publication, Blizzard has not posted an official response to either bug on the forums or in hotfix notes. The company’s published patch changes for 12.1 covered the new Lair instance type, the Venomous Abyss raid, class adjustments, dungeon work, and UI changes, but nothing in that list addresses disconnect handling or the Disintegrate visual glitch.

Players chasing Mythic 0 clears or pushing into the new raid ahead of Midnight Season 2 are left documenting the bugs themselves, timestamps and combat logs included, in hopes a hotfix follows before the new season begins on August 18.

Reported from

• Blizzard Entertainment Forums
• PC Gamer
• BlizzPro