Some source-backed game content may remain in English.

WoW Forever drop rates and data explained

Read source labels, map markers and drop samples without turning missing information into certainty.

Using the reference

Reviewed · Ragetusk Editorial · Edge Case

How this guide was made

Original interpretation of the catalog’s provenance and sampling rules. The probability calculation is explicitly hypothetical. Public-source facts, source-reported observations and Ragetusk’s planning advice are kept separate; no independent in-game drop experiment is claimed.

A client record is not a successful farm

An item extracted from the beta client establishes a record and its reported fields. It does not establish that a player can currently obtain it. A named source, observed drop, quest reward or vendor report adds a different kind of evidence. Check those fields before planning a trip. When acquisition is not reported, keep the item as a research lead rather than a guaranteed target.

Read the denominator before trusting a percentage

AHledger’s observations are collected from recorded loot windows. A dungeon-wide sample can contain several creatures and bosses; it cannot be reassigned to one named boss merely because that boss appears in the same dungeon. Ragetusk shows a percentage only when a reviewed source supplies both the rate and usable sample context. Unknown is not 0%, and an item’s presence in a loot table does not establish a rate.

Why five runs are not a promise

Hypothetical example: if a drop had a verified, independent 20% chance on every kill, the chance of seeing at least one in five kills would be 1 − (1 − 0.20)^5 = 67.232%. There would still be a 32.768% chance of none. This does not include who wins a shared drop. Without a reliable per-kill probability and the independence assumption, the calculation should not be used for a real Forever item.

  • A fixed number of runs cannot guarantee a random item.
  • Observed loot windows and completed boss kills are not interchangeable sample counts.
  • A group receiving a drop is different from your character receiving it.

Read map points in their own frame

A zone-map point, an entrance description and a marker on an illustrated dungeon floor answer different questions. Illustration percentages belong to that image, not the game’s world-coordinate grid. A point without an identified objective role should not be relabeled as the exact location of a quest item. Use the legend and source note before following a pin.

Know which update reached your plan

The website and iPhone use a shared catalog; the iPhone downloads valid updates on launch or refresh and keeps an offline fallback. Database discovery and editorial review are separate. Discovery can add an item or quest fact without supplying a complete walkthrough. A failed source fetch leaves the last working catalog in place. The talent planner currently uses the reviewed 1.60.1.70425 export with official October 15 corrections; a legal saved allocation is not proof of its in-game performance.

Send a correction another person can check

Send the page URL, the incorrect field, your proposed correction and a public source or the game build where you observed it to contact@edgecase.works. For a map issue, include the zone or dungeon floor; for loot, identify the creature and whether the number counts kills or loot windows. Do not send account credentials. The editorial page explains how sources and automated imports are handled.

Related reading

Sources: Ragetusk editorial and data standards · AHledger — open data, scan methods and attribution · AHledger — player-observed Forever loot (incomplete beta sample) · Talent trees and statistics from WoW Forever (CC BY 4.0) · Blizzard — October 15 Forever beta development notes

Advertisement