WoW: Blizzard Calls Evoker Disconnect Bug in Patch 12.1 High Priority

Blizzard has told World of Warcraft players that a bug disconnecting Evoker characters mid-fight is a high priority, Wowhead reported, closing out a week of forum complaints and a viral clip showing a disconnected dragon still swinging spells in a dungeon.

Curse of Ula’tek’s Ghost-Fighting Evokers

A growing number of WoW players have reported the issue since the Curse of Ula’tek 12.1 patch dropped for World of Warcraft: Midnight. The pattern is consistent: an Evoker drops connection mid-pull, briefly freezes the way any disconnect normally does, then keeps attacking as if nothing happened.

PC Gamer traced the clearest example to a Reddit video from user Stuperstrong. The clip shows a dragon-winged Evoker exhibit the typical signs of a mid-encounter connection drop at around 39 seconds, and then it starts fighting again. Other players in the same thread described near-identical moments with different classes, including a warrior whose character reportedly kept charging a boss after the owner’s game had already crashed.

Wowhead: Blizzard Marks the Bug High Priority

The phantom-fighting clips followed days of quieter, more mundane complaints. Evokers had already been beset by many bugs in Patch 12.1, resulting in frequent disconnects and broken spell visuals, as players tried to figure out what was going on. One player wrote on Blizzard’s official technical support forum that their Evoker was dropping every few minutes.

The player reported their Evoker getting disconnected and sent to the login screen at a frequency of every five to ten minutes, while their Druid and Monk on the same account ran fine. Wowhead’s later report confirmed Blizzard has now acknowledged the disconnect problem directly and classified it as high priority, a label the studio reserves for bugs it intends to fix ahead of routine tuning passes.

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

Disintegrate Beams Add a Second Disconnect Trigger

A separate bug report on Blizzard’s forums points to a related mechanical culprit. Disintegrate’s beams sometimes keep firing at dead enemies’ bodies the Evoker had already defeated, continuing regardless of range until the bodies despawn. Players reported that the issue can cause disconnects outright when four or five Disintegrate beams get stuck on dead bodies at once.

Whether the visual glitch and the phantom-combat disconnects share one root cause or two, both point at the same spell. Evoker has been the class most cited in bug threads since Patch 12.1 launched, and Blizzard’s high-priority label suggests a hotfix is being worked rather than merely logged for a future patch.

As of Wowhead’s report, Blizzard had not published a hotfix note specific to either the disconnect loop or the stuck Disintegrate beams, leaving both bugs live in Patch 12.1’s Curse of Ula’tek content for now.

Reported from

• Wowhead
• PC Gamer
• Blizzard Entertainment Official Forums