Lore › Tirisfal Glades › Ulag the Cleaver
The Lore
Ulag the CleaverTirisfal Glades

Quest · Tirisfal Glades · Level 10

Ulag the Cleaver

Read in English Deutsch Español Français Italiano Português (Brasil) Русский Українська 简体中文

The story

Beneath a mausoleum north of Brill, Ulag the Cleaver awaits a trial for young Forsaken. Deathguard Dillinger sends you to free the captive and meet him in combat.

After the Scourge swept across Lordaeron, the Forsaken captured an unusual undead warrior who named himself Ulag the Cleaver. His mind stayed clear, but the Lich King still held his spirit in psychic thrall. Beneath a mausoleum north of Brill, the Forsaken bound him with a magical seal. They hoped to learn how the Scourge chained a mind and to break its hold over Ulag.

The Forsaken could not free Ulag from the Lich King's command. Now Deathguard Dillinger sets the captive as a combat trial for rising Forsaken warriors. Disturb the skull stone outside the crypt, and the wards break, freeing Ulag from his prison. A warrior must face him with an axe. Death will release him at last.

Quest text

When the Scourge swept through Tirisfal Glades, we captured one to study. He had a free mind, and called himself Ulag the Cleaver. But, although his will was free, he was still enthralled by the Lich King.

We hoped to find a way to break the king's control over Ulag, but we failed. Now, finally, it is time to free him.

Free him, and kill him.

Activate the skull stone trigger near the mausoleum to the north. This will lift the magical seal that binds him.

Then... Be ready, friend.

Progress

Your task is yet undone, friend. It is not wise for a warrior to show fear...

Completion

Show the words

Well done, friend. Ulag was no minor agent of the Scourge. You have shown the Deathguards, and hence the Dark Lady, that you are a warrior of skill and resolve, and are worthy of further instruction.

On the same road

Hear it in game

Recordings of this page come in these downloads:

Look it up

Press ▶ on a row, or Play all

0:00

Report a problem with this line

What's wrong?