Vol’jin does not appear when I jump down to the Maw for the Campaign quest Maw Manifested. I’ve tried disabling all addons, resetting my Cache/WTF folders, abandoning the quest and getting it again, etc. It’s just a “speak to” quest, so I’d really appreciate it if I could just skip to the next step ASAP since this is holding me back from furthering my campaign and renown. Thanks!
Submitted this from the wrong toon – I’m experiencing this issue on Lyridawn on Tichondrius server.
This quest is broken. I have the same problem. My understanding is that Vol’Jin is not actually in the Maw yet. The problem is that when you are in Nazmir/Zandalar, and there are a lot of players in the room, they cover up Vol’Jin, so you can’t see that he is actually in the same room with you (and NOT in the Maw yet). The quest tells you to go to see Vol’jin in the Maw, but he is not actually there yet. So you have now left Nazmir/Zandalar, and you have no way to get back to talk to Vol’jin to continue the campaign.
This boat that is supposed to take Alliance back to Zandalar is also broken:
Thank you so much for explaining this in detail. You’re right, I had to speak to Vol’jin in Nazmir before jumping into the Maw which was not clear at all. How frustrating the boat isn’t working either!
I figured out that if you activate the low level war campaign in Boralus, this is how you activate the NPC to get the boat ride to Nazmir:
Now that I was able to get back to Nazmir through Boralus, I was able to find the death gate again, which is just NE of the Hearth of the Forest in Ardenweald, beside a big tree in the middle of one of the rivers. You might be able to use that to get back to Nazmir as well. It would be nice if they adjusted the quest to highlight this on the map.
I was told by tech support to abandon the quest and then pick it back up. I abandoned the Maw Manifested quest and now cannot get it back and can’t get to Zanzibar. I am stuck and can go no further in the campaign until this is fixed. As the other comments on this quest line are from January, it seems blizzard does not care and are not going to fix this bug.