Skip to Content
2-05-2010 @ 7:24PM
This.I'm sure Ensidia discovered the bug accidentally and through legitimate use of saronite bombs. They may not have realised that this wasn't "working as intended" for the encounter either.If it was an innocent mistake as Ensidia protest, the right thing to do (if it's technically possible for Blizzard to even do) would have been to remove the loot and achievements, respawn the Lich King and let them have at it with the Saronite Bomb hotfix. The 72 hour ban implies Blizzard believes Ensidia deliberately exploited a bug, and only Blizzard and the 25 guys from Ensidia in the raid will ever know the truth.As far as Blizzard having "shitty QA" - no matter how thoroughly you test something, the userbase will always find a way to break it. I'd rather have the big fights go live cold with no planned tactics and risk something like this happening again than four weeks of trial and error for the top guilds to come up with a detailed strat before the fight goes live and have the World First go within an hour of maintenance ending.
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.