Blizzard has fired a World of Warcraft GM (game master) for abusing their powers to help out a friend in a punishing endgame dungeon.

In the MMORPG World of Warcraft, game masters are these kind of omnipotent, god-like beings that oversee the in-game world. They tackle things like rules enforcement, support, and will also investigate cheating and do basic things like teleporting stuck players. They can even insta-kill enemies with a special death touch ability. There's one thing GMs aren't supposed to do, though, and that's using their powers to help out a buddy.
Popular Now: GTA Technical Director comments on GTA 6 running at 60 FPS on consolesBlizzard has recently let go of one such GM who used their bestowed powers to insta-kill an enemy in a Mythic+ 23 dungeon, an extremely difficult endgame activity. "I go to my GM friend and I'm like bro, can you please do a me solid? This thing has 20 million HP, bro please can you just one-shot it? Personally, I think it's harmless. I didn't expect him to do it. In hindsight, he shouldn't have done it. He was just doing me a solid," the affected WoW player said on stream.
Blizzard has responded to the situation with the following statement:

Frequently Asked Questions
TweakBot answers common questions about this news using TweakTown's own coverage from this page and related content from our archive. Tap a question to reveal the answer, or type your own below.
What specific GM powers were abused in the Mythic+ 23 dungeon incident?
How did Blizzard confirm the use of development-only spells on a live realm?
What evidence from the community or stream contributed to Blizzard's investigation?
Will Blizzard publish details about changes to prevent GMs using development-only spells on live realms?
Have a question not listed here? Ask below and TweakBot will answer it.
"As we mentioned, we internally monitored and confirmed a recent incident in which a World of Warcraft group gained an unfair advantage by abuse of access to development-only spells on a live realm.
"Our tools confirmed what was also surfaced in community discussions, and we have investigated the incident carefully. We can confirm that this was the action of a single Blizzard employee, in violation of our Code of Conduct.
"This employee is no longer with the company effective immediately. We are also taking action against the player accounts that were complicit in this violation."






