Onyxia quest inb stormwind bugged?

[MacBlimp]

Anybody else having problems with this quest (the great masquerade) not working properly? It just seems to stop when Windsor reveals Lady Prestor's true nature, then fails after about ten minutes of nothing happening :sad:

[Calli]

Well prior to the Realm Maintenance that brought us Patch 1.11, Windsor wouldn't even show up at Stormwind. After spending several hours waiting, a GM finally replied with "abandon quest and try taking it again". After trying this and going back and forth from Burning Steppes to Stormwind about three times, a GM replied with "this is a known issue, it should be fixed after Real Maintenance".

Realm maintenance rolls around and yes, Windsor now shows up at Stormwind and allows you begin the Great Masquerade quest. But as you've discovered, once Onyxia is unmasked, she's not interested in doing anything like summoning her Warders and killing Windsor. No, she stands there looking stupid. After trying it solo, grouped and in a raid at least 10 times since the patch, this pretty much happens every time.

Of course, if you fail the Masquerade, you can only restart it by tagging along with someone else who has the Stormwind Rendezvous quest, because you completed that already, therefore you can't go back and get it again from Marshal Maxwell in Burning Steppes. So you're pretty screwed unless you can find someone else with the quest.

According to the latest robot reply I got from a GM, this is "working as intended".

[Randomeyes]

Title says it all really.

Definite bug, frustrating for those on the chain

[moopy]

Of course, if you fail the Masquerade, you can only restart it by tagging along with someone else who has the Stormwind Rendezvous quest, because you completed that already, therefore you can't go back and get it again from Marshal Maxwell in Burning Steppes. So you're pretty screwed unless you can find someone else with the quest.


Actually, this isn't true. I know this because I recently attuned one of my alts for Onyxia, but lagged out while folllowing Windsor and failed, and had to repeat.

I went back the next day and waited outside of SW, on the road. Windsor's on a 10 min respawn timer. Despite the fact that I had no quest for him in the logs any more, he greeted me by name when he arrived; we did the quest. I even gathered up some lowbies who were curious as to what the little procession was about, and why a little dorf hunter was swaggering about with an NPC.

Prior to the patch, it was indeed repeatable, if you just waited on the road in front of SW for about 10 mins and had faith. I can see that it would be quite annoying if they broke this in the new patch. While it's frustrating for people who want to get attuned in a hurry, your best bet is probably to hope that Blizz get their finger out, and fix it during this week's maintenance.

[Calli]

Agreed. Waste of time repeating a bugged quest, I've given up until at least Wednesday and I'll see what happens then. If works for my Druid I just have to get it done with my Rogue, then.

[MacBlimp]

Tried to wait by the gate today to see if he respawned, and he did after a few minutes. Didn't bother to try the quest again though. Witing to see if there's a fix around first.

[Calli]

So just to recap, it was bugged, and the GM said it would be fixed in the following week's Realm Maintenance. Except it was still bugged. So we ticket it and the GMs tell us it'll be fixed in THIS week's Realm Maintenance.

Guess what? Still bugged.