Sigil of Trollbane is the sixth step in the long Trol'kalar quest chain.

Objectives Edit

Kill Prince Galen Trollbane and bring the Sigil of Trollbane to Zengu in Hammerfall.

Description Edit

The final of the sigils needed to unlock the tomb of Thoras Trollbane is held by his son personally. He resides deep within Stromgarde, in a chapel in the militia-held districts. Prince Galen is well protected and no slouch of a warrior himself, so this task could prove most difficult.

Progress Edit

You've returned, <name>. Is the line of Ignaeus Trollbane broken?

Completion Edit

Quite a day this is, <class>. The blood of Trollbane will no longer haunt my people, and the sigils needed to take Trol'kalar are in our possession. Soon, very soon, we will strike against the hated trolls of Zul'Gurub.

Rewards Edit

You will receive: 55Silver

Gains Edit

Notes Edit

  • Galen can be found in the chapel, well inside the Stromgarde milita sector of the keep.
  • This is the hardest quest in the chain, as Galen is level 44. He is not, however, particularly difficult outside from that- any character in the low 40s should be able to solo him without difficulty.
  • Try to avoid killing the nearbye alliance vendor, as this will mark you for PvP. He is non-hostile in any case.
  • It is advisable to kill all or most of the guards outside the chapel before pulling Galen out.
  • A hearthstone to escape is a good idea if you don't want to have to fight your way through all the guards twice (four times if you count the final quest in the chain as well).

Quest progressionEdit

  1. Horde 15 [37] Trollbane
  2. Horde 15 [37] Sigil of Strom
  3. Horde 15 [40] The Broken Sigil
  4. Horde 15 [40] Sigil of Thoradin
  5. Horde 15 [41] Sigil of Arathor
  6. Horde 15 [42] Sigil of Trollbane
  7. Horde 15 [42] Trol'kalar
  8. Horde 15 [42] Trol'kalar

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.