Two-Handed Weapon Specialization

Paladin · Retribution · opens at 15 points spent · 3 ranks

Two-Handed Weapon Specialization works differently in World of Warcraft: Forever than it does in Classic Era.

Changed in the latest patch (Blizzard's 2 November changes). See the patch notes

Two-Handed Weapon Specialization ranks in Forever

  1. Rank 1 Increases the Physical and Holy damage you deal by 2%, and reduces all threat you generate by 7% while a two-handed melee weapon is equipped.
  2. Rank 2 Increases the Physical and Holy damage you deal by 4%, and reduces all threat you generate by 14% while a two-handed melee weapon is equipped.
  3. Rank 3 Increases the Physical and Holy damage you deal by 6%, and reduces all threat you generate by 20% while a two-handed melee weapon is equipped.

What Two-Handed Weapon Specialization does in Classic Era

Forever changed this talent. The Classic Era wording is kept here rank for rank so the two can be read side by side.

  1. Rank 1 Increases the damage you deal with two-handed melee weapons by 2%.
  2. Rank 2 Increases the damage you deal with two-handed melee weapons by 4%.
  3. Rank 3 Increases the damage you deal with two-handed melee weapons by 6%.

Where Two-Handed Weapon Specialization sits in the Retribution tree

Two-Handed Weapon Specialization is a Retribution talent for Paladin. You need 15 points in Retribution before the row it sits on opens.

How often people take Two-Handed Weapon Specialization

44 of the 207 public Paladin builds saved here (21%) put at least one point in Two-Handed Weapon Specialization. Counted across the 1500 most viewed and voted public builds on this site. These are builds players made for themselves before the game is playable, so read them as what people are trying, not as advice.

Builds that take Two-Handed Weapon Specialization

7 of the public Paladin builds written up here spend points on Two-Handed Weapon Specialization.

Where this came from

Changed in Forever.

  • Forever client build 1.60.1.70790
  • the WoW: Forever client's hotfix cache, 6 November 2026 (DBCache.bin, build 70790)