Back to Uldaman
Vanilla reference: from the 1.12 world data, not yet confirmed in Forever.
Search for clues as to the current disposition of Talvash's necklace within Uldaman. The slain paladin he mentioned was the person who has it last.
A competitor of mine started a rumor that my necklace cursed the paladin. Needless to say, no one wants to buy cursed items from a jeweler.
adventurer, I'll make you a deal - find the gems and I'll reassemble the necklace, so long as you'll advertise that I do NOT make cursed items!
Try looking for clues in Uldaman; maybe see if the paladin's body is down there, since he's the one who we know had it last! When you find the gems you should use this; it'll allow you to contact me here in Ironforge.
Completion
Remains of a paladin: Reading the journal reveals that after much effort, the paladin had identified the location of all three missing gems:
The Shadowforge dwarves hid the ruby in their barricaded area as they battled the Troggs for control of Uldaman.
The troggs stashed the topaz in an urn located near some unusual inhabitants of Uldaman - Alliance dwarves!
Finally, the trogg elder himself took the sapphire as his own.
Rewards
2550 XP
Start:
Starts from the item
Talvash's Phial of Scrying
End:

- Start 56.9, 21.7
Alliance only
Back to Uldaman is a level 42 quest in Uldaman, World of Warcraft Forever: open from level 37, Alliance only. Talvash del Kissel asks you to search for clues as to the current disposition of Talvash's necklace within Uldaman. The slain paladin he mentioned was the person who has it last. Talvash del Kissel is in Dun Morogh. Rewards 2,550 XP. It is step 3 of 6 in its quest series. Quest data is from the vanilla 1.12 reference, not yet confirmed in Forever.
Quest chain:
| Part | Name | Level | Req. |
|---|---|---|---|
| 1 | The Shattered Necklace | 41 | 37 |
| 2 | Lore for a Price | 41 | 37 |
| 3 | Back to Uldaman | 42 | 37 |
| 4 | Find the Gems | 43 | 37 |
| 5 | Restoring the Necklace | 44 | 37 |
| 6 | Restoring the Necklace | 44 | 37 |
No comments yet.
Log in to post a comment