Per the title, I’ve been losing my mind for the past day over this. Got a sub again for the first time in about a year, decided I wanted to unlock the Vulpera after remembering that I had done most of the Vol’Dun storylines on at least one Horde character. I find the character in question (this one), and realize I actually had Secrets in the Sands already, and I’m over level 50. That’s all that’s needed when rep isn’t a requirement.
Excited, I head to Orgrimmar to the Embassy where I see Ji Firepaw…and no quest marker. Tried messing around with Chromie time, dropping random quests, nothing. Just won’t show up. I switch to what was then a lvl 49 or so toon (Battousaí) and play the hour+ needed to finish what I had left of the storylines on that one. Get the achievement, go to Org, same issue. What the hell is going on here?
I have not. This is the only Horde race I’m eligible to unlock. I don’t have the achievements for the others yet. As for the Alliance, those are already unlocked.
There is a thing right now where you can only start the allied race quests once you hit 60. It is being looked in to to see if it is intended or if the devs need to work on setting it back to 50. There really isn’t anything you can do but wait and see.
Ugh, you gotta be kidding me. That’s what I was afraid of as the thought had crossed my mind earlier. I’m also afraid to find out how long it’d take me to get those last 7 levels/how i should go about it since I barely even played it in SL. Appreciate the comment because this does seem like the most plausible thing thus far.
Also had to switch to this toon because I deleted the same comment on my other one because it wasn’t replying to you and then it wouldn’t let me make my actual post because it thought it was a double post despite the deletion. Real smooth Blizz.
Having the same issue that OP described, running a level 60 toon and I’ve got the necessary achievement but there’s no quest at Ji Firepaw. Not currently on any other allied race quests. If the problem is they changed it to level 60 then I’d probably be able to do it but maybe because I’m an evoker it’s not working?
I’ve tried filing a bug report to direct support and it came back as an automated message suggesting further research of the issue on wowhead and in this forum specifically. There’s (as of last time I checked) two other topics made after mine with the same issue. Please check my thread through my activity page. I’ve listed the steps I’ve tried to resolve the issue so far.
With Dragonflight the leveling range moved from 1-50 to 1-60 so a bunch of quests that used to require that you are 50 moved to 60. That does seem to be intended for the most part, as it is part of the leveling experience, including Chromie Time.
It does seem there are some extraneous quests that may also have been raised to the cap that might not be entirely intended. That is some of what we are making inquiries about.
If the Vulpera questline to invite them into the Horde changed to level 60 intentionally, a bunch of things need to be updated to reflect that. We also need to look at the other Allied Race questlines to see if the Legion 45 and BFA 50 requirement is still correct, if not, the in-game displays also need to be updated.
We’re checking with the Developers to see what’s what.
For you, the issue might be that your qualifying character is a Dracthyr. They may not be eligible for the quest at this time. We’re checking into that too.
Hopeful to see the developers followup on this before the event ends. I’m on a lvl 60 and also don’t have any quests popping up in the alliance embassy, despite being eligible for 3 (banners and wowhead confirm).
After much undo additional work due to this nonsense, I can confirm that it was indeed a matter of the requirements secretly being raised to 60. I’d like to think this is unintentional as non of the mobs you have to fight for any of the subsequent quests are scaled up to 60 with you and remain at 50, but who the hell knows.
Glad this super frustrating chapter is over, and I’m thankful someone on your end was able to chime in after my ticket had been ignored/written off with a lame autoresponse.
