I have my artifact weapon equipped and I can’t interact with the Seed of Ages in the druid’s legion class hall. I tried disabling addons, reloading, different artifacts. Nothing works and blizzard support auto-closed my ticket. Anyone know of a fix?
I have the same problem
Same.
With Legion becoming easier to solo, I wanted to unlock some new appearances so went to the Order Hall and no ability to interact.
Was earning the older skins removed and I just missed the memo? I could believe it.
Wowhead says the Seed of Ages quest is obsolete and removed, probably b/c the whole artifact system was gutted out. The skins should still be obtainable by doing what you originally had to do to obtain them (campaign progress/obtaining the usable item), just more of a pain to track progress on the color variants for sure.
I have another druid and Seed of Ages works with him. The differences between the two is the faction, I didn’t do all the Legion quests nor did the Mage Tower with him.
I was able to interact with it and then the next day I couldn’t. After about a week it somehow resolved itself. I’m guessing something changed on the backend with blizzard.
Nothing here even deactivating all addons
The problem still persists
Make sure you’re not on some phased quest that’s messing with your order hall progression.
1 Like
I only have Dragonflight missions and 1 battle pet mission
(post deleted by author)
Just got a response from support as I was having this issue.
Turns out having the Underlight Angler equipped in your fishing journal causes the Seed of Ages to not work.
Not sure if its the same for everyone, but hopefully this helps someone else having this issue 
(Big thanks to Klingoura for their patience and assistance in resolving this issue!)
7 Likes
I do have it equipped. I’m going to test it as soon as I arrive home.
Unequipping the the Underlight Angler from the fishing journal resolved the problem. Thanks
2 Likes
Unequipping the underlight angler solved it, I can now use the Seed again. Thanks Iolanthe!
Thank you so much! I was having trouble with this issue and your response fixed my problem!