Skip to Content
2-04-2010 @ 11:16AM
@Daedalus:I'm not saying they're too stupid to find it, I'm saying that it's likely that it didn't come out of the internal tests. It may happen, there are so many things to check in an encounter, I'm not blaming them for this. The PTR testing helps reducing these situations, that's all I wanted to say.And even if Blizzard knew about the existence of the bug, if they had to fix it quickly it means that at least they didn't evaluate correctly the potential impact, as they said it greatly reduces the difficulty of the encounter. Also this point could have been evaluated with a PTR test and if there wasn't enough time to fix it, at least they had to warn the players somehow.As Chris said, they have to choose between spoiling the encounter to use a safe approach and delivering a potentially buggy product to preserve the suspense. It's not a simple choice. If they want to continue with the latter, top guilds are now adequately warned.About the kill by Ensidia, I surely agree that it has to be considered void, whether it was intentional or not. Some people say that Ensidia preferred to report the bug after the LK kill while they had to do it before that, so they probably deserve a suspension, but yet, if they're suspended because they were playing as usual, they have the right to be pissed off.
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.