Also on AOL
- Autos
- Technology
- Lifestyle
- Gaming
- Finance
- Entertainment on AOL
- Lifestyle on AOL
- Sports on AOL
- Travel on AOL
- More on AOL
Featured Galleries
Joystiq
© 2013 AOL Inc. All rights Reserved. Privacy Policy | Terms of Use | Trademarks | AOL A-Z HELP | About Our Ads

Reader Comments (Page 1 of 1)
2-05-2010 @ 7:24PM
Azizrael said...
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.