Dark Iron Dwarves

Support Customer Support
1
I've completed the quest and returned to Southwind Embassy to meet with Andiun to complete the quest. His question mark shows up on the map, an arrow also shows up on the map and when I approach the Embassy, a question mark show up on my mini map. However, when I enter the Embassy, he's not there. The question mark still shows up on my mini map, but he's not there.
2
Stay there at the Embassy, log out and back in.

Some people have reported that it's managed to force them to show up.

Can you also confirm that you have no quests in the area phasing you out of the default worldstate?
3
Nope, that didn't work. Only quest I'm doing right now. Any other suggestions?
4
Could try going other places he frequents, like the Keep. If you have some sort of quest phasing or area phasing, it might cause him to not be in the Embassy. Sometimes just finding people at different places will still let you turn in the quest.
5
He is sitting in his chair in the keep, but just welcomes me to Stormwind.
6
10/29/2018 11:51 AMPosted by Laydelarrek
He is sitting in his chair in the keep, but just welcomes me to Stormwind.


Well, that is just lazy of him. Maybe see if you have other old-world quests that you can finish off? Maybe you have another quest that involves Anduin so he is missing?
7
Which quest specifically did you complete and are trying to turn in?
8
Dark Iron Dwarves
9
Did you figure it out, Laydelarrek? It looks like you completed the "Dark Iron Dwarves" quest.
10
10/29/2018 12:28 PMPosted by Vrakthris
Did you figure it out, Laydelarrek? It looks like you completed the "Dark Iron Dwarves" quest.


Nope, just signed back in and he's not showing up. Tried the suggestions from the other folks, but no joy. Did I forget to bring something with me? Though I suspect that if I didn't, the question mark would be dull not bright yellow. Thoughts?
11
Vrak is seeing the quest as completed which would be why the ? is not showing up.

And in the armory, it's showing that you already unlocked the Dark Iron Dwarves too.

https://worldofwarcraft.com/en-us/character/aggramar/laydelarrek/achievements/reputation
12
Sorry, but I posted this question on the wrong toon. This is the correct one that's having the problem.
13
Looks like that's the same account. So you only ever have to unlock an allied race one time as the achievement is account-wide ;)

https://worldofwarcraft.com/en-us/character/aggramar/claultodox/achievements/reputation
14
https://worldofwarcraft.com/en-us/character/aggramar/Claultodox
15
I think you missed the significance of what Vrak just said.

You have already completed and turned in the "Dark Iron Dwarves" quest. That's it. That's the last quest in the unlock chain. Your armory even shows that you unlocked the DI racial mount. If you have the mount, you are done with the unlock.

There are no more quests to do or turn in. The only thing left to do is to roll up your first Dark Iron Dwarf.
16
Once the quest line to unlock an allied race is completed by any one of your characters, it cannot be done by any others. It sounds like you might have initially picked it up on a couple of characters, but once one of them completed it, it became unnecessary for the other.

You can just drop the quest ;)
17
10/29/2018 01:35 PMPosted by Perl
Looks like that's the same account. So you only ever have to unlock an allied race one time as the achievement is account-wide ;)

https://worldofwarcraft.com/en-us/character/aggramar/claultodox/achievements/reputation


So you are saying I didn't need to run the quest, as this toon, since I had completed it with the other. Why did it show up in the Embassy when I entered the room with this character? Claultodox.
18
Yall have been a great help, thanks. Just thought that since it showed up in the Embassy as my C character, I had to run it.
19
10/29/2018 01:41 PMPosted by Claultodox
So you are saying I didn't need to run the quest, as this toon, since I had completed it with the other. Why did it show up in the Embassy when I entered the room with this character?

Correct.

I'm not entirely certain why it may have popped up. It might be worth submitting a bug report so our QA team can take a look.