Current published snapshot
16,607 responses checked across 93,652 known entity and spell-tooltip URLs; 77,045 still need source work. These counts include unavailable responses and records that may need another check. Listings, calculators, professions, supporting references and artwork have separate audits.
- Client join build: 1.60.1.70235.
- Latest entity or tooltip response: .
- Current source refresh began: .
- 18 related lists are explicitly truncated; 1 large list does not report a total.
- 243 encrypted client sections remain unavailable.
- The published relationship and provenance integrity audit passed.
The known source queue still has work. This is coverage of sources we know about, not a percentage of all facts in the game.
Where the facts come from
Installed Forever game files provide readable client tables, names, spells, items, maps and artwork. Matching hotfixes and server-answer caches are applied only when their build and structure validate. An older cache keeps its original build label. Encrypted or missing records stay unavailable.
Current Wowhead Forever pages add public game facts, including loot, vendors, trainers, quests, recipes and relationships. Pages must identify the Forever environment and the requested entity. Comments, player submissions and authored guides are excluded from this import, as are Classic fallback records.
How current records update older ones
Verified current public fields take priority over older stored values. A field the page does not supply retains its sourced Forever client fallback. An explicitly complete empty list can clear older entries; a missing list is not treated as empty. Changed names require a verified entity identity.
Source URLs, retrieval times, content hashes and recorded versions remain attached to the data. Conflicts retain both values and their evidence. The client build used to join a public record is recorded separately from that record’s source version. A retrieval date tells you when we read a page, not when the game last changed.
What unknown means
Missing prices, stock, quantities, levels or requirements do not become zero. Explicit free prices and genuine zero values remain valid. A drop percentage is retained only when supplied; sample counts are not treated as the number of items in a loot table. Unresolved spell expressions and difficulty-selection rules remain unresolved.
A truncated list proves that some rows are hidden. A large list without a reported total leaves completeness unverified. Neither another NPC’s inventory nor a reciprocal link proves that a seller or loot list is complete. Source scripts are inspected as text and never executed to guess missing facts or recovery routes.
How a release is checked
Collection saves resumable batches. Changed batches rebuild the catalogs and independently audit entity identities, source proof and reciprocal relationships. Quantities, prices and percentages are checked without filling unknown values. Rebuilding stable inputs must produce the same output.
Public releases use an immutable audited snapshot and pass application checks. The deployed coverage and representative pages are then verified against that release. A release can contain useful, verified data while collection is still incomplete; its remaining gaps are published with it.
Read about WowSeer, or browse the database. Even checking every known URL cannot guarantee that every server fact has been discovered or made public.