Skip to main content
AzeriteUOPlayer Wiki
Implemented — awaiting full validation

Completing a run requires killing every mandatory boss in the dungeon, in addition to reaching 100% on Enemy Forces. The Azerite Dungeon has three named bosses.

Jailwarden Kharzul (first miniboss)

A melee-heavy encounter built around two named mechanics worth learning by name rather than by number, since the exact numbers are still being tuned:

  • Chain Lash — a telegraphed ranged attack. It’s avoidable if you react to the telegraph.
  • Shackle — a timed mechanic that, if failed, deals damage and briefly immobilizes whoever failed it, and can summon an add. Handling Shackle correctly matters more at higher Keystone levels, where the add wave compounds with an already-longer fight.

Golem Prime (second miniboss)

A heavier melee/area encounter with multiple telegraphed abilities (a melee slam, an area pulse, and a ground-targeted mark) plus turrets that spawn once the Golem drops below half health. Turret count scales with your party size. Treat the turrets as a priority target once they appear — they hit harder as a group than the boss’s own abilities at that point in the fight.

Zar’Thul (final boss)

The dungeon’s final encounter. Zar’Thul is intended as a longer, multi-phase fight rather than a single damage race — exact phase mechanics are still being finalized and aren’t documented here yet because they haven’t been confirmed stable.

The honest state of difficulty right now

Internal testing has identified early-Keystone difficulty (roughly levels 1–2) as feeling noticeably harder than intended, for reasons that are mostly about specific monster behavior rather than the Keystone scaling formula itself — a particular trash monster’s control-effect proc and one add-spawning mechanic lacking a hard cap are the two biggest known contributors. A retune is planned but not yet confirmed live. If low-Keystone runs feel disproportionately brutal compared to what you’d expect, that matches what we already know — please still report it, with specifics, so we can confirm the fix actually landed.