Skip to Content
2-04-2010 @ 12:17PM
I don't think Ensidia knew what was causing the platform to rebuild. How could they? It's not like the combat texts would tell them, and they were probably too busy trying to, y'know, kill the Lich King.They had never been there before. They a bug and they took it, probably thought it happens to everyone. Certainly they were much too concerned with getting a world first to verify if other guilds were experiencing the glitch. Much like the Martin Fury scandal, the "correct" approach would have been to stop high-end raiding and contact a GM. Blizzard still has the right to ban anyone, for anything. I don't agree with it, but still I don't like the banning. Blizzard had another option, they could have reset the battle, taken away the loot and the Achievements and told Ensidia to do it again. But right this time.And for all the haters that might say this isn't as big as Martin Fury, if another guild gets the world-first, Ensidia will probably wish they were perma-banned.
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.