{"id":24819,"date":"2026-04-28T08:42:33","date_gmt":"2026-04-28T08:42:33","guid":{"rendered":"https:\/\/immortalboost.com\/blog\/?p=24819"},"modified":"2026-04-28T08:42:33","modified_gmt":"2026-04-28T08:42:33","slug":"wow-patch-12-0-5","status":"publish","type":"post","link":"https:\/\/immortalboost.com\/blog\/world-of-warcraft\/wow-patch-12-0-5\/","title":{"rendered":"WoW Patch 12.0.5 Broke Almost Everything \u2014 Here’s What’s Actually Fixed, What Isn’t, and What You Should Do Now"},"content":{"rendered":"\n

Published: April 28, 2026 | WoW: Midnight<\/strong><\/p>\n\n\n\n

<\/p>\n\n\n\n

Let’s skip the recap. You already know Patch 12.0.5 launched badly on April 21. What you actually need is a clear answer to one question: “Is it safe to play yet, and which parts of the patch can I actually trust right now?”<\/strong><\/p>\n\n\n\n

That’s what this article is for.<\/p>\n\n\n\n

Still paying full price for your subscription while the patch stabilizes? Grab your WoW 30 day game time<\/a> on Eneba at the best market rate \u2014 instant key delivery, no auto-renewal, no surprises.<\/p>\n\n\n\n

<\/p>\n\n\n

\"wow<\/figure>\n\n\n

<\/p>\n\n\n\n

The Bug That Nobody’s Talking About Properly: The PTR Trap<\/h2>\n\n\n\n

Before getting into the bug list, here’s the thing that should make every WoW player genuinely angry \u2014 and it’s being underreported.<\/p>\n\n\n\n

Player Housing was disabled during the entire 12.0.5 PTR testing cycle<\/strong>. That means when players were testing the patch before launch, they couldn’t even access Housing. The critical bug that caused Housing to go offline for North American and Oceania servers on day one? It almost certainly could have been caught if Housing had been available to test. It wasn’t. So it wasn’t caught.<\/p>\n\n\n\n

That’s not bad luck. That’s a broken testing pipeline. Blizzard shipped a feature in a patch without actually testing that feature in the patch environment. The community flagged the Haranir clipping bugs and certain class issues weeks before launch<\/strong> in PTR feedback threads \u2014 and they still made it to live servers.<\/p>\n\n\n\n

This is the part of the “we will do better” apology that the official statement quietly skipped over.<\/p>\n\n\n\n

What Actually Broke \u2014 And the Part Each Bug Hit<\/h2>\n\n\n\n

Here’s the honest bug-by-bug breakdown, with current fix status as of April 28, 2026:<\/p>\n\n\n\n

\ud83d\udd34 Voidforge Bonus Roll System \u2014 Gave Duplicate Items<\/h3>\n\n\n\n

What happened:<\/strong> The entire selling point of the Voidforge was bad luck protection. Get an item from a bonus roll, and it gets removed from your loot pool so you won’t see it again. It did the opposite. Players were getting the same item \u2014 same slot, same piece \u2014 multiple times from bonus rolls.<\/p>\n\n\n\n

The technical reason: the new bonus roll tech was saving loot data to the wrong database on live realms. The PTR and live environments have separate databases, which is why the bug didn’t surface in testing.<\/p>\n\n\n\n

What it means for you:<\/strong> If you used Voidcores before the fix on April 22, your rolls were wasted. Blizzard confirmed a refund is being issued to everyone affected \u2014 check your currency tab. The system is safe to use now.<\/strong><\/p>\n\n\n\n

\ud83d\udd34 Decor Duels \u2014 Broken in Three Separate Ways Simultaneously<\/h3>\n\n\n\n

This one is worth breaking down because it wasn’t just bugged \u2014 it was broken on a design level that no amount of hotfixing fully solves.<\/p>\n\n\n\n

Bug 1 \u2014 Track Humanoids exploit:<\/strong> Hunters (and anyone using a Blackened Worg Steak food buff) could activate an ability that shows all player locations as dots on the minimap. In a hide-and-seek mode. The tracking ability has existed in WoW for years and nobody on the development team flagged it as a conflict with a game mode built around not being found.<\/p>\n\n\n\n

Bug 2 \u2014 Out-of-bounds hiding:<\/strong> Some hiders found ways to clip outside the arena’s invisible walls, making themselves impossible to tag. Standard map boundary issue that was somehow missed.<\/p>\n\n\n\n

Bug 3 \u2014 Anti-AFK system punished good hiders:<\/strong> The penalty system designed to flag players who weren’t participating was triggering on people who were just… hiding well and staying still. The core mechanic of the mode. Players were losing rewards for playing correctly.<\/p>\n\n\n\n

Current status:<\/strong> The Track Humanoids exploit and the penalty system were hotfixed on April 22-23. Out-of-bounds exploits have been partially addressed. Decor Duels is playable now but has not recovered its reputation from week one. Community sentiment is still largely “wait and see.”<\/p>\n\n\n\n

\ud83d\udd34 Player Housing \u2014 Disabled Entirely for ~24 Hours<\/h3>\n\n\n\n

US and Oceania servers lost access to the entire Housing system \u2014 not just housing zones, but the Housing Dashboard and the ability to learn new decor \u2014 the moment 12.0.5 went live.<\/p>\n\n\n\n

Europe got the patch 24 hours later and never hit this issue, which tells you the bug was environment-specific in a way that PTR testing (which mirrors EU server architecture more closely) wouldn’t have caught.<\/p>\n\n\n\n

Current status:<\/strong> Fully restored and stable. No data loss was reported.<\/p>\n\n\n\n

\ud83d\udd34 Holy Paladin \u2014 50% Below Other Healers in Damage<\/h3>\n\n\n\n

This one hit a specific and vocal part of the playerbase hard. Holy Paladins launched Patch 12.0.5 with a talent that was actively tanking frame rate, and were missing a hotfix that left their damage output roughly half of comparable healer specs.<\/p>\n\n\n\n

If you’ve been playing Holy Paladin this week and feeling like something is wrong, something is wrong. Multiple hotfixes have gone out since April 22 to address this.<\/p>\n\n\n\n

Current status:<\/strong> Partially fixed. Check the latest hotfix notes for your specific talents before assuming it’s fully resolved \u2014 Blizzard has been pushing targeted spec fixes across several batches.<\/p>\n\n\n\n

\ud83d\udd34 Keystone Myth Achievement \u2014 Disabled at Launch<\/h3>\n\n\n\n

Players who hit the 3,400 Mythic+ rating threshold to unlock Keystone Myth logged in on patch day to find the achievement itself had been disabled entirely.<\/p>\n\n\n\n

Current status:<\/strong> Re-enabled via the April 24 hotfix. Players who qualified before the shutdown will receive the achievement and its Timelost Saddle reward retroactively \u2014 you don’t need to do anything to claim it.<\/p>\n\n\n\n

\ud83d\udd34 Void Incursion Progress Bars \u2014 Vanished or Not Triggering<\/h3>\n\n\n\n

Void Incursions \u2014 the large-scale world events that are supposed to unlock after enough Void Strikes are completed \u2014 were either showing no progress bar or failing to trigger at all depending on which phase layer players were on.<\/p>\n\n\n\n

Current status:<\/strong> Blizzard disabled Void Incursions entirely on April 25 to work on a fix. They are currently offline. No confirmed return date as of publishing.<\/p>\n\n\n\n

\ud83d\udfe1 L’ura Raid Boss \u2014 Attack Pattern Bugged<\/h3>\n\n\n\n

The final boss of the March on Quel’Danas raid was executing attack patterns incorrectly, which on Mythic difficulty has a compounding effect on wipe rates for progression guilds.<\/p>\n\n\n\n

Blizzard also quietly reduced Gravity Collapse damage on Crown of the Cosmos by 10% in the April 23 hotfix. That’s not a bug fix \u2014 that’s a tuning change that was probably overdue regardless of the patch chaos.<\/p>\n\n\n\n

Current status:<\/strong> Addressed in hotfixes. If your guild was wiping on L’ura more than expected this week, the encounter now behaves as designed.<\/p>\n\n\n\n

The Subscription Price Hike Nobody Wanted to Talk About<\/h2>\n\n\n\n

On the same week this patch launched, Blizzard announced a WoW subscription price increase in the United Kingdom and Georgia.<\/p>\n\n\n\n

Timing is a choice. Blizzard chose to announce this while the community was already fielding broken systems, an apology post, and a week of hotfixes. The Reddit reaction was exactly what you’d expect. There was no functional reason to make that announcement in the same news cycle.<\/p>\n\n\n\n

This isn’t about whether price increases are justified. It’s about the signal it sends when your product launches broken and your business team sends a price increase notice in the same breath.<\/p>\n\n\n\n

What the “We Will Do Better” Apology Actually Said<\/h2>\n\n\n\n

Blizzard’s official statement used careful language. Here’s what it committed to and what it didn’t:<\/p>\n\n\n\n

What it committed to:<\/strong><\/p>\n\n\n\n