Mage Hall Guide loads instead of Broken Shore Guide

[ebrum2010]

Yesterday I was working on one of the steps of the Broken Shore guide, but today when I logged in it kept redirecting me to the Mage Hall Guide. I had the same issue yesterday with two different guides but I can't remember for the life of me now which ones they were because it eventually stopped doing it.

[ZG Support 1]

What happens when you load the Broken Shore Campaign guide from the guide selection window?

[ebrum2010]

Same thing. I can't get it to load from anywhere. I can't do anymore of the Mage Hall guide until I unlock the next part which takes a couple days. I'm trying to do the quests I have in Broken Shore and I'm having to do them without the guide.

[ZG Support 1]

Try resetting your guides by exiting the game, going to your WoW/WTF/Account/<accountname>/SavedVaraibles folder, and delete the Zygor files in there. After that see if you can load the broken shore guide.

[ebrum2010]

It worked in letting me load the guide from step one, but after I skipped the completed steps it went straight to the Mage Hall guide again.

Edit: I don't know if it matters, but when it sends me to the Mage Hall guide, it sends me back to step 1 in it despite me having finished a lot of it. I'm waiting for a Mage Hall upgrade thing to finish to be able to get the next quest in the chain, otherwise I'd just have finished it by now but judging by how it sends me to step one, I don't think finishing it will fix it.

[ZG Support 1]

Is it Alliance or Horde guide that's giving you a problem?

[ebrum2010]

I'm on Horde.

[ZG Support 1]

We'll check into it more and see if we can find a label jump or something that is causing it to go back to that guide.

[ebrum2010]

After I got to the part in the Mage Hall guide where it says I have to finish the broken shore campaign before continuing, it let me switch back to the other guide. I'm not sure if this means the bug is fixed or it just persists until this point.

[ZG Support 1]

That should be it being fixed I believe. I know it was being worked on and we've been releasing a lot of updates lately to fix all of the things that went wrong since 7.3.5 so it was probably fixed in yesterday's update.