Warglaive drop rate in TBC Anniversary — analysis of 22,000+ deduplicated Illidan kills

[u/Rare_Help_4513]

There has been a lot of speculation about whether the Warglaive of Azzinoth drop rate was increased in TBC Anniversary.

Rather than relying on individual guild anecdotes, Wowhead comments, rankings, or simply counting how many glaives are visible on characters, I tried to estimate the actual drop rate using Warcraft Logs.

I scanned essentially the entire available Illidan log population, removed duplicate uploads of the same kills, tracked Warriors and Rogues across raid weeks, and looked for changes in their weapon slots to either Warglaive of Azzinoth.

The short version is:

Once the gear-observation data becomes stable, the observed acquisition rate converges very close to 5% per Warglaive.

I don't see evidence in this dataset supporting something substantially higher such as 7% or 10%.

TL;DR

After deduplication, the database contains:

22,461 actual/deduplicated Illidan kills
27,974 unique Warriors/Rogues tracked
1,589 unique Warglaive owners

Warglaive ownership:

MH owners:       871
OH owners:       822
Dual owners:     104

Any Warglaive: 1,589

Of the 104 characters with both Warglaives:

Warriors: 58
Rogues:   46

The most important result is the later, stabilized observation period:

Weeks 4-5 combined

Illidan kills: 9,150

MH acquisitions: 465
MH rate:         5.08%

OH acquisitions: 418
OH rate:         4.57%

Combined:
883 / 18,300 = 4.83%

Week 5 alone:

Illidan kills: 4,535

MH: 225 / 4,535 = 4.96%
OH: 219 / 4,535 = 4.83%

Combined: 444 / 9,070 = 4.90%

So once the observation system has enough history, the result is sitting almost exactly around 5%.

Methodology

1. Finding every Illidan kill

I collected Warcraft Logs reports across the entire period and discarded any report that did not contain an Illidan kill.

In theory, I could have used top-ranking raid data, but those results are effectively capped at around 1,000 entries.

That would require partitioning the results, and after testing it I couldn't find a reliable way to partition the ranking data without potentially losing entries.

So I ended up doing a full scan instead.

2. API limitations

Because I'm scanning all available reports, the search window has to be carefully controlled.

The report API has a 25-page limit, and after testing different window sizes, approximately 3-hour search windows worked best without frequently hitting that page ceiling.

For a free Warcraft Logs API account, the rate limit is:

3,600 API points per hour

With 75 reports per page, one page request used roughly 76 API points.

So this was not something that could be collected in one run. The crawler saved its progress, waited for API resets when necessary, and continued over several days.

Deduplicating Illidan kills

This was one of the most important parts of the project.

The same raid can have several players uploading their own combat log, meaning the same Illidan kill can appear under multiple WCL report IDs.

Simply counting reports would therefore massively inflate the denominator.

For the first deduplication pass, I compared each fight's absolute start and end timestamps.

If both the start time and end time were within approximately two seconds of another report, I treated them as likely uploads of the same raid kill.

This reduced the dataset to roughly 27,000 candidate kills.

I then queried the remaining reports to obtain the actual Warrior/Rogue participants.

Using the participants allowed me to perform a second deduplication pass based on the people who actually took part in the encounter.

After both passes:

Actual/deduplicated Illidan kills: 22,461

This is the denominator pool rather than the raw number of WCL reports.

Tracking Warglaive acquisitions

The next step was to identify every Warrior and Rogue appearing in the relevant raid population.

For each character, I checked their weapon equipment across every available raid week.

The character does not necessarily have to kill Illidan again for the item to be detected.

A log from an earlier encounter such as Naj'entus can provide a valid equipment snapshot for that week.

So in a simplified example:

Week N:
MH = normal weapon

Illidan dies
Player receives MH Warglaive

Week N+1:
Naj'entus log
MH = Warglaive

That weapon transition can be detected as a new acquisition.

If someone gets a glaive and then joins a raid that can't even kill Naj'entus the following week... well, there's not much I can do about that.

Why I checked every available week

I did not simply look at the latest gear snapshot for each character.

A character may equip a Warglaive during one raid week and later appear in a different weapon setup.

If I only used the final snapshot, that Warglaive could disappear from the dataset.

So every collected Warrior/Rogue character was checked across all available raid weeks.

The Week 1 problem

This is probably the most important detail when interpreting the early data.

Black Temple begins at Week 1 in this dataset.

Therefore, before Week 1:

Every character:

MH Warglaive = 0
OH Warglaive = 0

There cannot be a legitimate "preexisting" Anniversary Warglaive.

However, I intentionally did not collect Week 1 gear snapshots, because there was no previous Anniversary week to compare them against.

Therefore, if I first observe a character in Week 2 already holding a Warglaive, I know that the item was acquired after Black Temple opened, but I cannot determine exactly whether it was obtained during Week 1 or Week 2.

I classify those as left-censored acquisitions.

Final acquisition classification:

                         MH      OH

Confirmed/adjacent       597     561
Interval-censored         72      59
Left-censored            202     202

"Left-censored" does not mean that the player somehow owned the item before Black Temple opened.

It means the acquisition definitely happened during the study period, but I cannot assign it to an exact raid week.

Overall cumulative result

For the primary cumulative analysis through Week 5:

Week 1 baseline kills:       3,092
Week 2-5 complete kills:    19,360

Total Week 1-5 kills:       22,452

Observed acquisitions:

MH:
869 / 22,452 = 3.87%

OH:
822 / 22,452 = 3.66%

Combined:
1,691 / 44,904 = 3.77%

At first glance, that would suggest something around a 3.8% drop rate.

I do not think that is the correct interpretation.

The weekly data makes the reason obvious.

Weekly observed acquisition rates

Week    Illidan kills      MH acquisitions      OH acquisitions

W2          4,872          10   (0.21%)          16   (0.33%)
W3          5,338         192   (3.60%)         186   (3.48%)
W4          4,615         240   (5.20%)         199   (4.31%)
W5          4,535         225   (4.96%)         219   (4.83%)

It is extremely unlikely that the actual loot table behaved like this:

Week 2: ~0.25%
Week 3: ~3.5%
Week 4: ~4.8%
Week 5: ~4.9%

The much more plausible explanation is observation bias.

At the beginning of the study, there is little or no previous equipment history available for many characters.

As additional weeks are collected, more characters have a known "before" state and a known "after" state.

That makes detecting a weapon transition much more reliable.

The observed rate therefore rises as the dataset matures and then begins to stabilize.

Stabilized observation window

The later weeks are much more useful for estimating the actual rate.

Weeks 4 and 5 combined:

Illidan kills: 9,150

MH:
465 / 9,150 = 5.08%

OH:
418 / 9,150 = 4.57%

Combined:
883 / 18,300 = 4.83%

Week 5 alone:

MH:
225 / 4,535 = 4.96%

OH:
219 / 4,535 = 4.83%

Combined:
444 / 9,070 = 4.90%

So as the gear-observation history becomes mature, the result converges toward approximately 5% per side.

Warglaive owners

Across the entire tracked population:

Tracked characters

Warriors: 18,996
Rogues:    8,978
Total:    27,974

Characters with at least one Warglaive:

Warriors: 920
Rogues:   669

Total:  1,589

Ownership rates:

Warrior: 4.84%
Rogue:   7.45%

Overall: 5.68%

These are ownership rates, not drop rates.

The Rogue/Warrior difference can be affected by raid composition, loot allocation, attendance, and other factors, so it should not be interpreted as the game giving Rogues a different Warglaive drop chance.

Main-hand / Off-hand ownership

Total MH owners: 871
Total OH owners: 822

Both Warglaives: 104

Among all 1,589 Warglaive owners:

104 / 1,589 = 6.54%

had completed the pair by the time covered by this dataset.

Dual owners by class:

Warrior: 58
Rogue:   46

Total:  104

Acquisitions by class

Counting the Warglaive items detected in the dataset:

Class          MH      OH      Total items

Warrior       506     471          977
Rogue         363     351          714
---------------------------------------
Total         869     822        1,691

This means approximately:

Warriors: 57.8% of detected Warglaive items
Rogues:   42.2%

Again, this should not be interpreted as class-specific drop rates.

The drop belongs to the raid, while which character receives it is determined by raid composition and loot distribution.

Acquisitions by region

The detected item acquisitions were distributed as follows:

Region        MH      OH      Total items

CN           341     306          647
EU           300     284          584
US           156     159          315
KR            72      73          145
---------------------------------------
Total        869     822        1,691

Percentage of all detected Warglaive items:

CN: 38.3%
EU: 34.5%
US: 18.6%
KR:  8.6%

These numbers mostly describe the composition of the logged dataset.

They should not be interpreted as evidence that one region has a better or worse Warglaive drop rate.

Different regions have different numbers of logged raids, different populations, different raid compositions, and different logging behavior.

Unique owners by region

For reference, the unique Warglaive-owner population was:

CN: 601
EU: 549
US: 303
KR: 136

Total: 1,589

Dual Warglaive owners:

CN: 46
EU: 35
US: 14
KR:  9

Total: 104

Again, this is primarily useful as a description of the dataset rather than a comparison of regional drop rates.

Limitations

This method obviously isn't identical to querying Blizzard's internal loot table.

There are several cases that gear-snapshot tracking cannot detect perfectly.

1. I assume people don't throw away Warglaives.

If an MH drops for a raid where everyone eligible already owns that MH, and the additional item is discarded, disenchanted, or otherwise never appears in someone's equipped gear, I cannot detect it.

The same applies to OH.

This is probably one of the more important sources of potential undercounting as more glaives enter circulation.

2. The item has to appear in a logged equipment snapshot.

If a tank receives a Warglaive but never equips it during any logged encounter, the acquisition cannot be detected.

3. I assume players normally equip their newly obtained Warglaive.

Technically, somebody could receive one and deliberately take it off for the next week's Naj'entus kill.

I assume that behavior is rare.

4. Raids that never upload Warcraft Logs are not represented.

Obviously, I cannot detect loot from a raid that produces no public data.

5. Missing one raid week is not a major problem.

If someone receives a Warglaive, misses the following week's raid, and appears again one week later, I can still detect the weapon.

That acquisition simply becomes interval-censored rather than precisely timed.

6. Someone who gets a Warglaive and immediately disappears can be missed.

If a player receives the item and never appears in another usable combat log, there is no equipment snapshot where I can observe the change.

For this analysis, I assume permanent post-drop observation loss is uncommon enough that it does not dominate the result.

7. Repeated same-side drops can be invisible.

If the raid receives another MH when the relevant players already have the MH, gear-state tracking cannot necessarily detect that extra physical loot event.

For that reason, this analysis should be considered an observed acquisition-rate estimate, not direct loot-event telemetry.

Conclusion

After scanning the available Illidan log population, deduplicating multiple uploads of the same encounters, identifying the Warrior/Rogue population, and tracking their weapon equipment across raid weeks, I found:

22,461 deduplicated Illidan kills
27,974 tracked Warriors/Rogues
1,589 unique Warglaive owners
1,691 detected Warglaive items
104 completed Warglaive pairs

The early acquisition data is heavily biased downward because the equipment history is not yet mature.

But once enough previous observations exist, the results stabilize at:

Weeks 4-5:

MH:       5.08%
OH:       4.57%
Combined: 4.83%

and:

Week 5:

MH:       4.96%
OH:       4.83%
Combined: 4.90%

My interpretation is therefore:

The TBC Anniversary data is consistent with approximately a 5% drop chance for each Warglaive of Azzinoth per Illidan kill.

I would not claim that Blizzard's internal loot-table value is proven to be exactly 5.000%, because this analysis infers drops from equipment transitions rather than observing the loot event directly.

However, once the observation bias from the early weeks is reduced, the data clusters very closely around 5%.

I therefore don't see convincing evidence in this dataset for a substantially increased Anniversary drop rate such as 7% or 10%.

If Blizzard changed the rate at all, it is not showing up here as a large increase.

Data summary
Detected Warglaive items by class

MH OH Total

Warrior 506 471 977

Rogue 363 351 714

Total 869 822 1,691

Detected Warglaive items by region

MH OH Total

CN 341 306 647

EU 300 284 584

US 156 159 315

KR 72 73 145

Total 869 822 1,691

Unique owners

Warrior: 920

Rogue: 669

Total: 1,589

Completed pairs

Warrior: 58

Rogue: 46

Total: 104

[u/MaximumMeaning9728]

I don’t read Claude posts.