Ion Hazzikostas explains how a 2013 elevator broke WoW housing in patch 12.0.5

World of Warcraft game director Ion Hazzikostas has opened up about what actually went wrong with patch 12.0.5 — the messy April update that broke multiple systems and left players questioning whether Blizzard was trading quality for speed. In an interview with YouTube channel Psybear_tv, Hazzikostas says the real culprit wasn't the faster patch cadence itself, but the team being too aggressive about fixing bugs in the final days before release.

The most striking example involves player housing getting disabled for an entire day. During internal checks on patch day, Blizzard discovered that any housing decor placed off the ground was snapping to the floor — permanently altering players' carefully arranged setups. The root cause traced back to a last-minute fix for the Siege of Orgrimmar elevator, a piece of content from 2013 where players were falling through the floor. The fix went in just a few days before 12.0.5 shipped. Because WoW is built on roughly 20 to 25 years of layered, interdependent code, the logic controlling how a player attaches to an elevator object also touched how items can be parented or stacked in housing placement. Nobody went back to check housing in that final day and a half before the patch went live — until it broke in production. Hazzikostas is candid about the call that should have been made: ship the stable build, then push the elevator fix as a hotfix afterward rather than rushing it into the patch itself.

Hazzikostas has been a consistent defender of the faster patch cadence Blizzard adopted starting with Dragonflight, arguing it lets the team deliver a broader spread of content for players with different playstyles. WoW's content drought problems in earlier expansions — particularly Battle for Azeroth and Shadowlands — made that cadence shift a deliberate design priority. The 12.0.5 situation is an uncomfortable test case for that philosophy, and Hazzikostas acknowledges the optics were bad: players saw bugs, saw speed, and connected the two dots. His argument is that the connection is real but the direction of causation is wrong — it wasn't moving fast that caused the damage, it was a specific late-stage decision to squeeze in one more fix.

Whether players buy that distinction likely depends on how much goodwill Blizzard has in the bank at any given moment. Hazzikostas says the team takes "half-baked" releases seriously and wants to understand what players were hoping for from affected systems. The more concrete takeaway from his own post-mortem is procedural: late bug fixes on complex legacy systems need a housing check — or equivalent regression testing — before they go anywhere near a live patch.