Feb 4th 2010 11:04AM @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.
Feb 4th 2010 9:36AM If it was a bug that was quite hard to reproduce, I'd agree with you, but as many people said, it involves an item that a good number of players in the top guilds use to maximize DPS, ignoring such a bug would be like setting a trap (clearly Blizzard didn't forecast this, as they had to hotfix it drasticly by disabling siege damage on these objects to take time to fix it).
And naturally, I'm supposing that Ensidia didn't find the source of the bug. If they knew what was causing it and used it anyway, everything changes.
Feb 4th 2010 8:29AM On a side note, this is also showing that not testing end bosses in the PTR causes them to be launched in live with all the bugs the internal testers didn't discover.
If the Lich King was in the PTR, the guilds in it would have discovered the bug immediately, and the development team would have fixed it, while at this time the guilds that erroneously suppose that everything is working fine might get a 3-day ban and have to start over while other guilds that were behind them have a 3-day advantage to get the world first.
Many people just don't care about it, because when they get to the end boss most of the bugs will be fixed, but this is surely pissing off world-first guilds.
The absence of the end bosses in the PTR was probably to reduce drama like "that guild tried it on the PTR and was advantaged", but it is creating even more drama instead.