Sitting here in Gilneas and really didn’t want to waste my evening not being able to play a new character. Battle for the city of Gilneas keeps kicking me back to the bridge every 10 minutes or so. The prince doesn’t even make it to Sylvanas.
Any way to just get my character moved to Stormwind or something?
It sounds like the quest event is resetting. Have you tried completely logging out for a few minutes, Owlcapown? That might allow you to switch shards to an event that is functioning correctly.
If you continue to have an issue you’d want to put in ticket using the “Stuck on a Quest” option. We wouldn’t simply move you to Stormwind, as could potentially break the character.
I personally have disabled/ removed all add ons, exited all the way out of the game and closed the launcher, and dropped the quest and picked it up again.
Currently there is about 7 of us stuck here.
I just want out of the zone.
Nothing works and it seems to be an ongoing issue.
But for how long? As Vrak mentioned, you’ll want to give the scenario some time to reset. Jumping back in immediately probably isn’t helping. I would also second his suggestion about checking out the group finder to see if you could find a different shard where it isn’t bugged.
That is sometimes enough. Check the group finder out for options, and if that doesn’t pan out, see if you can get everyone else to leave it be for a half hour or so.
Or it may just put you on a new shard in that time, regardless.
I also just realized that I wholly imagined Vrak suggesting that, for some reason. Placebo credit! I think it was the “switch shards” thing.
This is something you’d drop in the in-game suggestion box, or probably even the Dungeons, Raids, and Scenarios forum. Developers don’t take suggestions or feedback from this forum, alas.
But if the 30 minute wait doesn’t help, you might just want to throw in the towel for the night and try again tomorrow. It’s possible that it’ll have worked itself out before your ticket is addressed.
I couldn’t really put a definitive bead on it, since it is technically a scenario within a quest. My gut just told me the former, but both probably work just the same.
Bugs like this can’t be vanquished at the snap of a finger. No bug truly can. Especially when it, I’m sorry to say it like this, happens to a comparatively minuscule handful of players. It’s a lot harder to track down an issue that doesn’t broadly affect the entire game and its players, and even harder to find and implement a fix for it that doesn’t break it for those that have no issues whatsoever.
But also as stated, suggestions for things that you think they should implement in order to effect these need to be directed through the proper channels.
It also isn’t hurting everyone, which is the crux of my point. Only a small handful of people. That makes it substantially harder to track down…
And that’s on top of a dynamic priority list for bugs, as it is. Bugs that provide issues that are visibly affecting a vast majority of players are often placed in the list ahead of things that are considered minor, by comparison, and have been there for a while.
Well, I thought I’d give it another go. I talked to the royal chemist and get ported to a group of 4 players who are having the same issue. Looks like I’ll have to wait on a GM to respond to my ticket. There goes my evening.
So that’s about 30 or so players I saw have this happen to them in an hour or two. I wouldn’t call that a small number of people.