Ardenweald: necessary Research
yoshimo opened this issue ยท 3 comments
We have 3 quests where the availability is not entirely obvious and breadcrumbs and potentially other factors are involved:
- Trouble in the Banks (https://www.wowhead.com/quest=57651)
Has comments likeUnable to start this quest. ALL other quests in zone are complete however.
Guys to get the Breadcrumb for "Well, Tell the Lady", you gotta start at Foreman Thorodir at location 46,29. You do all these quests with him and Fluttercatch at 47, 24, then you get the breadcrumb for "Well, Tell the Lady" (https://www.wowhead.com/quest=59656/well-tell-the-lady#)
- The Grove of Creation (https://www.wowhead.com/quest=57660/the-grove-of-creation)
Probably invalidated by and breadcrumb forTrouble in the Banks (https://www.wowhead.com/quest=57651)
malcherus 2 days ago (Patch 9.0.2)I had Trouble in the Banks in my quest log. Once I abandoned it, The Grove of Creation became available.
- Wild Hunt Offensive (https://shadowlands.wowhead.com/quest=60840/)
Not always there, maybe bugged, maybe requirements have to be found. WH said
Doesn't seem to trigger reliably. My warlock was the only person in my party to get the 'bonus' objective. No one else could even see it on the map, much less get it to trigger in their quest log to complete it.
I was level 57, they were all 58 at the time.
and
I only have 3 test cases, but it seems that if it is the first character on the account to go thru the Wild Hunt, it doesn't trigger, but if doing a subsequent character (and not doing Threads of Fate leveling) it will trigger this quest. Anyone have another explanation for why it happens sometimes if on main story quest line and never for TOF.
I personally came into the area with level 60 on the wildhunt campaign part and didn't get it on my shaman.
- Some quests in Ardenweald are tagged "classic" which is clearly the wrong expansion
- Also it seems that a lot of quests are missing their conditions for the night fae covenant.
The expansion that is displayed is solely based on Blizzard API. I have seen that quests return 0 by default, but upon revisiting the quest, Blizzard will have cached it and now return the proper value. However, there are some that always return 0. Perhaps this feature should be removed since Blizzard's API is flaky (from a user perspective).
I have done no real work on any covenant other than Venthyr. Eventually I will get to them all, but it will be quicker for others to contribute in the time being.