WoW: Wrath Of The Lich King Classic Bug That Went Unnoticed For 14 Years Finally Fixed
The bug made one of World of Warcraft's best weapons, Val'anyr, Hammer of Ancient Kings, even stronger than intended.
One of World of Warcraft: Wrath of the Lich King Classic's most powerful weapons has been more powerful than intended for 14 years, all thanks to a simple typo that went unnoticed by both Blizzard and players back when the weapon first debuted back in 2009.
The weapon in question is the Legendary healing mace Val'anyr, Hammer of Ancient Kings, which can be acquired by gathering fragments from the expansion's iconic Ulduar raid and completing subsequent quests. What makes the weapon so powerful is its special effect tailor made for healers. When using Val'anyr, heals have a chance to activate a shield on their respective targets that can absorb up to 15% of the amount healed. Ulduar released back in 2009 originally, and arrived in Wrath of the Lich King Classic on January 19, 2023.
TODAY was HILARIOUS this is literally the funniest thing to have in QA. A war room going down where we're trying to hackerman out solutions only for the solution to be... a single fucking 0 tacked to a script causing things to break. S+ tier problem lmao#ClassicWoW pic.twitter.com/6BavsHTe9k— Morgan K. 🐝🐝 (@Artemishowl_) March 28, 2023
That makes it an incredibly powerful weapon for tank healing, but as Blizzard notes in a March 27 hotfix, the weapon's special effect was actually stronger than originally intended due to a nearly 15-year-old typo. The shield granted by the weapon was always intended to cap out at 20,000, but an extra "0" in the weapon's spell script actually made that amount 200,000. That's a big difference.
"The absorb shield from Val'anyr was always intended to have a cap of 20,000 health, but there was a typo in the spell script in original Wrath of the Lich King version 3.3.5," Blizzard's hotfix reads. "The script was set the absorb amount to 200,000! This was never noticed by players in original Wrath."
Now, the reason this bug looks to have largely gone unnoticed for so long is likely due to the fact that the number of players who actually ever acquired Val'anyr back in the day is relatively small. Ulduar was a punishingly difficult raid when it debuted, and the long process of acquiring Val'anyr made it so only the most dedicated players that were members of the best guilds had the chance to wield it. The final quest to obtain the weapon requires players to toss the fragments of Val'anyr into the mouth of the final boss, Yogg-saron, at a specific moment and then defeat it.
There's also the fact that the few players who did originally obtain the weapon likely never even approached the unintentional 200,000 shield cap, due to the fact that the shield is based on 15% of healing received. However, players completing Ulduar in 2023 have much more experience (and online guides and resources) to help min-max their characters, meaning more players are likely using Val'anyr now than back in 2009. It also means that the shields granted due to the weapon's effect are much more likely today to surpass the intended cap of 20,000 than in 2009, making the already powerful weapon extra potent and finally catching Blizzard's eye.
Wrath of the Lich King Classic released in September 2022, introducing the Death Knight to the old-school version of Blizzard's MMO. Since then Blizzard has introduced a number of changes to the game's most popular expansion, including the addition of a new dungeon difficulty and the ability for players to create one Death Knight character free of the expansion's original restrictions. Blizzard recently reverted that particular change, once again making it harder to create Death Knights in order to deter bots and bad actors from being able to take advantage of easily making a level 55 character.
The products discussed here were independently chosen by our editors. GameSpot may get a share of the revenue if you buy anything featured on our site.
Got a news tip or want to contact us directly? Email firstname.lastname@example.org
Join the conversation