30 outa millions is small. Tell them to post in the bug forums the more attention it gets the better, also tell them to put in a suggestion to skip the final scenario blizzard will listen if enough people suggest it they cant ignore the issue till wow ends.
2 Likes
You don’t need to be on that character when a GM responds. Surely this bug isn’t stopping you playing other characters?
1 Like
30 out of who knows how many new Worgen characters. It won’t be millions, as millions are not making Worgens.
Well, I want to play my rogue. Plus, there’s nothing let to do on my other chars that is not time gated. ( rep etc )
Logged in this morning to give it another try. Prince makes it to the patchwork monster and kicked back to the bridge.
Time till my ticket gets looked at went from 3 hrs 52 min last night is now over 14 hrs.
That time is the estimated time of the ticket based on the queue time of last number of tickets handled. It’s not a count-down timer.
Have you filed a bug report with this information? More information for QA on where and when the bug happens will help them locate the issue.
1 Like
My point was you’d figure there would be a sense of urgency on Blizzard’s part to fix this ASAP, as the character literally can’t do anything.
1 Like
It may require specialist intervention in order to fix it for your character.
2 Likes
Yep known issue. A quote from GM who replied to me.
“I did some digging to see what I could find for you. You are right, from what I’m finding, many people have problems finishing this quest,”
The GM finished the quest for me so I could continue. Woot!
6 Likes
Sweet! Great outcome, happy leveling 
5 Likes
Just for clarification, resolving issues that cause roadblocks like this tend to be a priority. With that said, not all situations are always so clearly defined. Some bugs are extremely complicated where they don’t happen consistently, making it nearly impossible to reproduce and thus find a resolution for.
There were a number of bugs around the events that happened in the Worgen starting area. Where an event would simply stop working. That was mostly resolved by implementing a number of bug fixes, one of which was a default reset timer that would force the event to reset if it got stuck. This mostly works, but that doesn’t prevent other bugs to pop up.
The only way we’ll be able to resolve the issue is if our QA staff can figure out what is causing it and that tends to require information. Folks submitting bug reports with as much detail on what is happening as they can. The In-Game Bug Report system also has the added benefit of noting your character, character state, and location of the character at the time of submission.
I’m sorry for what frustration this may have caused you, Owlcapown.
5 Likes
Sorry, I didn’t mean fix it bug wise. I meant fix it ticket wise. Currently the only option for a “stuck” character is to port you to a graveyard or have the game auto kill you. Neither of those were helpful options. You can’t even submit a ticket with the title stuck character. I think there should be an option for characters that literally can’t do anything, like in my case, and have the ticket set to a high priority.
That is for a literally-stuck character, though. Cannot actually move, falling through the world, etc. Not for being stalled in quest progression. There’s a separate ticket category for that, which I do believe is higher priority. And which was probably assumed as the category you used, since you didn’t specify, and only said you had a ticket in.
https://us.battle.net/support/en/help/product/wow/197/472/channels
The way that the support system is currently set up is that there are pre-determined categories that a game master is able to assist players with, and players have to choose from them to get help. Tickets aren’t open-ended because they’re already filled out with the necessary information before you even get to describe your specific problem.
If there is no clearly-defined path to choose from, or if you have to get extremely creative with your ticket submission, chances are very high that you aren’t going to get the help you’re looking for.
3 Likes
Stuck on quest, where you can level or quest elsewhere is one thing… I was literally stuck in Gilneas. I could not leave, quest, or level. Seems like two very different things to me.
Generally speaking, our Devs aren’t in the habit of simply skipping quests that might be causing an issue. They focus on fixing the issue itself so that it doens’t cause that kind of road block.
That normally works, but this situation is complicated… there have been several fixes implemented over the years but issues still pop up.
Even if we had situations in which we would want to jump a quest the “Stuck” system really isn’t intuitive enough to help in that situation as it wouldn’t necessarily be able to detect which quest, or what part of the quest and overall how to fix it.
Those tickets already tend to be considered priority. Unfortunately, that doesn’t always allow us to get to it immediately. Our Support staff does try to get to it as quickly as they can though. Sorry for the frustration this has caused you.
1 Like
Thanks for the clarification on that. I had no idea how each ticket category worked.
I appreciate it.
2 Likes
It’s one year later and it’s still bugged. I sent in a ticket thinking that yet again, a GM will move my character past the quest like they did twice in the past (and these past tickets are on file). Instead I get a reply saying that the GMs can’t give hints, cheats, etc., and therefore refuse to move my character, instead I have to delete ALL of my AddOns and rename certain folders with the world “Old” in it.
They wouldn’t have told you to delete them if they told you to just rename the folders. All you have to do is the rename.
3 Likes
A Game Master isn’t going to review your entire ticket history before contacting you. That would take way too much time and the majority of the situations would be entirely irrelevant to any new issues.
Keep in mind that in most situations our staff is going to try and run you through some basic troubleshooting steps. The quest has a known issue where it may get in a state where folks cannot complete it, but unfortunately, no surefire fixes have been found.
If you have tried abandoning the quest and running through the event again, submit a ticket using Stuck on Quest. Tell them you have retried The Battle for Gilneas City multiple times and you are unable to progress.
3 Likes
I pressed the “Still have an Issue” button on the ticket and stated that I have tried everything that has been suggested, even taking the quest again and the issue still remains.
2 Likes
Here I am, in June of 2020, and this quest is still broke for my level 19 Kittenator. I put in a ticket and the response I got was “check the forums”. So how the heck does a Worgen get past this point?
- go slow during the event. don’t run ahead of the NPCs
- use only single-target attacks. don’t kill faster than the role-playing aspect of the event.
It is especially important now with the experience buff. If you try to go faster than the event is meant for, it will fail and you will have to restart it.
1 Like