You forgot a few:

Thank you for making World of Warcraft
Thank you for providing information when there is any
Thank you Sir may I have another?

---

Q u o t e:

That said, I thank them every month with 15 bucks.

---

---

Q u o t e:


I try not to genuine appreciation in with sarcasm. That said, I thank them every month with 15 bucks.

---

Is it really that hard to have the NPC reappear after a soft reset? Is it really that hard to hot fix that?

If you pay for it I'll fly there and do it for you. I give you my money for your service and you do it wrong, if you pay me I'll do it right and smiling.

Ty blizz for wasting my time and fúking up my schedule much <3

red text: forgot to mention the servers that we pay for and don't get the right maintenance or don't get upgraded based on player population. I play on a mid-pop server and my holy light took 8 seconds to cast.

---

Q u o t e:

my holy light took 8 seconds to cast.

---

You should really stack more haste.

---

Q u o t e:
I play on a mid-pop server and my holy light took 8 seconds to cast.

---

This. We can't even do a raid right now because 1-2 minutes into Heroic Beasts, everyone starts getting 2-3 second lag for all abilities. This has been going on since last night's Anub'arak attempts.

In fact, lag is why we called our raid... only to find out the soft reset caused by calling the raid locked us out of the encounter. And now the lag is preventing us from doing any of the hard modes too ;-(

I haven't seen any acknowledgment from Blizzard that they know about the lag issues and it's a little discouraging. I really hope Blizzard is reading this.

Thanks for the update, Daelo. I'm hoping the ToC instance lag issue on various realms/battlegroups can get addressed though, or this fix doesn't really help us. :\

---

Q u o t e:
Update for you all...

A hotfix has been deployed that will prevent the instance from entering a bugged state where Barrett does not spawn after a soft reset. If you haven't gotten to Anub'arak yet, you'll be fine now.

For those of you already afflicted with this bug in your saved raid, I'm still working on a method to correct the issue via hotfix for everyone so afflicted.

In the meantime, our customer service staff has been informed how they can resolve the bug for a raid with a bugged instance.

---

Thanks for the fast response. You rock.

---

Q u o t e:
Dear Blizzard,

Thank you for not thoroughly testing this encounter before sending it live.
Thank you for screwing guilds out of valuable raid time.
Thank you for caring enough to tell us how to avoid this problem after it's too late.
Thank you for being inconsiderate enough to not even give us a timeframe on a fix.
But most of all, Thank you for thinking we're stupid enough that we'll believe you really care.

---

alot of people seem to think this was done intentionally to hurt them...

---

Q u o t e:
Update for you all...

A hotfix has been deployed that will prevent the instance from entering a bugged state where Barrett does not spawn after a soft reset. If you haven't gotten to Anub'arak yet, you'll be fine now.

In the meantime, our customer service staff has been informed how they can resolve the bug for a raid with a bugged instance.

---

Sweet, thanks mate.

cool, just gotta wait 20 hours for a response from one of them

---

Q u o t e:
cool, just gotta wait 20 hours for a response from one of them

---

pffft if only it was that short

On mannoroth we seemed to have a slighty different issue. We have not soft reset instance, but when you talk to barrett he just babbles about preparations being finished next week, as though its a week behind

We got a GM to respawn the NPC to start the floor event. However, after speaking with him he just disappears and the floor remains =/

Ok, WOW.

Four pages of QQ for a broken-floor glitch. A glitch which within a DAY was found, tracked down, a fix written for, and hotfixed into live servers. A glitch which Customer Service can now resolve for folk who were stuck due to it. A fix which had Blue posts along the way as the looked in to it, and fixed it. And the Blues posted even though the thread was hijacked with complainers QQing about how they hate the company. And still, people complain that it's not good enough.

The fact that within hours of the Grand Crusader going live a guild has managed to sucessfully clear it and get the tribute to insanity achievment aside, the fact that Blizzard has been in the forums, heard the complaints, and resolved them, should earn some respect. They made a mistake (one that honestly, was not an easy one to have found through internal and PTR testing since the people there were not lible to call it and come back). They fixed it. And they did so while keeping the community in the loop.

I say Good Job Blizz. I appreciate your attention to the issues. The fact that end game content gets this kind of attention does lean towards the "Blizzard caters to high-end raiding guilds" feeling that people are starting to feel, but hey, it's working now. Thanks Blizz :)

---

Q u o t e:
Ok, WOW.

Four pages of QQ for a broken-floor glitch. A glitch which within a DAY was found, tracked down, a fix written for, and hotfixed into live servers. A glitch which Customer Service can now resolve for folk who were stuck due to it. A fix which had Blue posts along the way as the looked in to it, and fixed it. And the Blues posted even though the thread was hijacked with complainers QQing about how they hate the company. And still, people complain that it's not good enough.

The fact that within hours of the Grand Crusader going live a guild has managed to sucessfully clear it and get the tribute to insanity achievment aside, the fact that Blizzard has been in the forums, heard the complaints, and resolved them, should earn some respect. They made a mistake (one that honestly, was not an easy one to have found through internal and PTR testing since the people there were not lible to call it and come back). They fixed it. And they did so while keeping the community in the loop.

I say Good Job Blizz. I appreciate your attention to the issues. The fact that end game content gets this kind of attention does lean towards the "Blizzard caters to high-end raiding guilds" feeling that people are starting to feel, but hey, it's working now. Thanks Blizz :)

---

Refer to my post above, its not fixed if you have a bugged instance. Respawning the NPC does not fix the issue.

---

Q u o t e:
Ok, WOW.

Four pages of QQ for a broken-floor glitch. A glitch which within a DAY was found, tracked down, a fix written for, and hotfixed into live servers. A glitch which Customer Service can now resolve for folk who were stuck due to it. A fix which had Blue posts along the way as the looked in to it, and fixed it. And the Blues posted even though the thread was hijacked with complainers QQing about how they hate the company. And still, people complain that it's not good enough.

The fact that within hours of the Grand Crusader going live a guild has managed to sucessfully clear it and get the tribute to insanity achievment aside, the fact that Blizzard has been in the forums, heard the complaints, and resolved them, should earn some respect. They made a mistake (one that honestly, was not an easy one to have found through internal and PTR testing since the people there were not lible to call it and come back). They fixed it. And they did so while keeping the community in the loop.

I say Good Job Blizz. I appreciate your attention to the issues. The fact that end game content gets this kind of attention does lean towards the "Blizzard caters to high-end raiding guilds" feeling that people are starting to feel, but hey, it's working now. Thanks Blizz :)

---

Agreed. Stop crying already people, it's not the end of the world (of Warcraft). When dealing with a game as massive and complex as this bugs are guaranteed to happen no matter how much testing they do - the important thing is how they deal with it, and in this case Blizzard is actually doing a good job of addressing this.