[Resolved]

due to the “ground mounts not allowed here” bug.

Tried alt+f4 and relaunching. Tried logging into another character and got the same. Abandoning quest and retaking, disabling all add ons, ect. Nothing works, and I can’t complete the dungeon without being able to mount.

Any suggestions?

Get on a flying mount?

1 Like

Need to be in skyriding mode.

1 Like

Do like I do. Ignore that weekly because that dungeon is hot garbage.

1 Like

They all haver the error, flying and ground mounts.

I am.

TY for reply though.

Can you ride with someone else?

Need more info, where are you when you try to mount? Might seem like a dumb question but I’ve seen people get mad because they try to mount at the entrance and start raging about the place being bugged when it doesn’t work.

Also have you tried switching flight styles? Both types of flight work and switching might kickstart the ability.

Was just doing follower mode to blow it out.

On the ship during the boss fight when you have to in order to survive. I tried swapping styles and swapping back. Nothing seems to work.

I’m probably misremembering but I thought the weekly could only be done in heroic or higher.

Naw. I blow them out on follower all the time

i did it on follower dungeon mode last night

As for the error, that’s a noodle scratcher. Maybe bug report forum or GM ticket, but honestly not sure either of those would get you a fix, at least not on time, if at all

Nope, did it with a friend in a follower dungeon, in old school flight and flight form on my Druid.

Must be a new bug or possibly an addon malfunction?

Is it possible it’s related to the gear of whoever got quest? Guess I’m gonna have to confirm when I’m home.

There are 2 weeklies related to Dungeons.

One of offered by Biergoth.

There is another option to choose a dungeon as a weekly, that’s part of Call of the Worldsoul (which isn’t Dawnbreaker this week), this says it must be done on H+.

The one offered by Biergoth, I always do as a follower dungeon, have not done it this week yet.

Well, the bug resolved itself.

Apparently shutting down the client and waiting 15 mins before relaunching it fixed the issue.

/shrugs.

WoW gonna WoW I guess.

Thanks for the replies guys.

2 Likes