Fractured Spark of Omens is a vital crafting resource in World of Warcraft: The War Within, so completing the “Omens Unified” quest (which rewards you with two) is essential. Here’s what you need to know about how to start and complete this quest.
How to start the Omens Unified quest in WoW: The War Within
You’ll start the Omens Unified quest in The War Within by speaking with Custodian Khubon, the Catalyst Steward, in the Forgegrounds of Dornogal on the Isle of Dorn (coordinates 50 and 54).
Unlike standard WoW quests, which are mostly marked with a plain yellow exclamation point, this is considered an important quest; the quest marker above the Custodian’s head is a purple inverted triangle. So, if you don’t use a coordinates add-on to help you navigate Khaz Algar, look for the man with the purple inverted triangle above his head.
How to complete the Omens Unified quest in WoW: The War Within
To complete the Omens Unified quest, you need to obtain one Fractured Spark of Omens. You can collect one by completing Faerin’s Call of the Wordlsoul quest each week. This rewards you with a weekly cache which cache contains a Fractured Spark of Omens. Once you have another Fractured Spark of Omens, you can turn it in and complete this quest.
Fix the ‘Unable to complete the Omens Unified quest’ issue
Some WoW players have been reporting an issue where they picked up this War Within quest before obtaining another Fractured Spark of Omen and then couldn’t complete it. Although it’s not ideal, the best option to fix this issue is to get a Fractured Spark of Omens before picking up this quest. That way, you can complete it as soon as you accept it.
If you’ve already accepted the Omens Unified quest, abandon it. Once you’ve done that, obtain a Fractured Spark of Omens, and then pick up the quest again and complete it instantly. Doing this resolves the issue of being unable to complete the Omens Unified quest. I had this issue, which was beyond frustrating, but abandoning the quest and getting a Fractured Spark of Omens before accepting the quest again fixed the issue for me.
