For players who spend hours refining routes and shaving seconds from difficult dungeon runs, trust matters almost as much as damage output. The World of Warcraft GM cheating claim now under investigation cuts directly into that trust, with combat logs appearing to show an internal instant-kill effect helping a five-player group finish a timed Mythic+ dungeon.

Blizzard has said it is investigating and will take “appropriate actions.” As of July 23, however, the company had not announced any findings or disciplinary measures. The disputed run has vanished from Raider.IO’s rankings, though community discussion indicates that Raider.IO removed it independently rather than at Blizzard’s direction.

What the Nexus Point Xe'nas log showed

The controversy began when a Reddit user examining Warcraft Logs spotted unusual events in a Mythic+23 run of Nexus Point Xe'nas. Mythic+ dungeons become harder as their keystone level rises, while teams race against a fixed timer. A +23 run is demanding, but not implausible: the dungeon’s reported best at the time was a +25 completed in 24 minutes and 34 seconds.

The questioned group finished in 29 minutes and 43 seconds, just under the 30-minute limit. That result alone would not have attracted much attention. The final stretch did.

According to the log, enemies before the last boss, Lothraxion, died at 27:57. Lothraxion then appears to have been killed unusually quickly by an effect labeled “Death Touch.” Seconds later, another enemy required to complete the dungeon was struck by “Area Death (TEST),” an internal-looking ability whose tooltip says it kills every enemy within 30 yards and ends with the word “Cheater.” Subtle naming was apparently not a development priority.

The effect was attributed to Daijosai, an additional actor who was not one of the five characters listed in the party.

Why players suspect employee intervention

GamesRadar reported that the combat data records an internal instant-kill effect rather than an ordinary player ability. Wowhead separately matched the timestamp and duration to a genuine run that had appeared on Raider.IO, making a casually fabricated standalone log less likely because the data sat inside a live upload containing other runs.

That evidence is significant, but it is not the same as a completed investigation. Wowhead cautioned that, without video, investigators initially could not eliminate possibilities such as altered log data or a bug. No member of the group was streaming the dungeon, so there is no public footage showing Daijosai entering the instance or using the command.

The party included Evoker player Schizofien, known as streamer Yara, and Demon Hunter player Jabuka, known as Yiesus. Wowhead reported that four members knew one another, while the Druid tank joined as a pickup player. The distinction has become important as players debate who, if anyone, should face penalties.

The evidence became harder to dismiss after Yiesus discussed the run during an interview on Yumytv’s stream.

What Yiesus said about the alleged favor

Yiesus said the group was in voice chat with a friend connected to Blizzard while attempting the dungeon. With the timer nearly expired and an enemy still alive, he said he asked that friend to “do us a solid” and kill it so the group would not have to repeat what he called a “homework key.”

He characterized the request as a joke and the resulting advantage as harmless, while acknowledging the obvious problem: “In hindsight, he shouldn’t have done it.” Yiesus also said Blizzard could revoke the completed key or his title if the company considered that appropriate.

His account supports the central allegation that someone with privileged access intervened. It does not fully explain every event in the log. Yiesus focused on the final remaining enemy, but the recorded “Death Touch” against Lothraxion suggests the boss may also have been affected before the last mob died.

That gap leaves Blizzard with more to examine than one impulsive request. Investigators would need to determine who controlled Daijosai, what permissions that person held, whether both suspicious effects came from the same source and whether similar commands were used in other competitive runs.

Why one completed key matters

Mythic+ is not merely a private dungeon activity. Results flow through Blizzard’s application programming interface and into third-party ranking services, where players compare scores, pursue seasonal rewards and compete for leaderboard positions. An employee-assisted completion therefore affects more than five people saving half an hour.

The case also exposes a wider problem of auditability. Warcraft Logs captured granular combat events from this run, including the otherwise invisible internal spell. If a high-level dungeon is not logged, outsiders may see only summary data supplied through Blizzard’s systems. That could make comparable intervention much harder to detect.

The reporting raises practical access-control questions for Blizzard:

  • Which employee roles can enter active competitive instances?
  • Who can execute internal kill commands on live servers?
  • Are those actions recorded in a separate company audit trail?
  • Do unusual interventions trigger automatic review?
  • Has privileged access affected earlier rankings or rewards?

There is no public evidence that money changed hands or that this was part of a broader pattern. Those concerns remain questions raised by players, not established facts.

Blizzard has yet to announce an outcome

Blizzard community manager Kaivax responded to the original discussion by saying the company was aware of the incident, actively investigating and prepared to take appropriate action. That remains Blizzard’s only substantive public statement described in the available reporting.

Reaction among players has ranged from demands for account closures to calls for the employee involved to be fired. A forum poster named Stat argued for both. Others have urged Blizzard not to punish the pickup tank, who apparently uploaded the log that brought the suspicious events to public attention and was not part of the group’s reported friendship circle.

The disappearance of the run from Raider.IO removes it from that service’s rankings, but it does not settle responsibility or reveal whether Blizzard changed the underlying result. Until the company publishes its findings, the logs and Yiesus’ comments provide strong grounds for scrutiny, not a final verdict.

For the wider player base, the emotional stake is straightforward. Competitive systems work only when effort, skill and failure apply equally, including when a friend with access happens to be listening in voice chat.