How we read this

Everything here is a restatement of data shipped in the World of Warcraft game client, pulled from Blizzard's own servers, with the exact build it came from attached. No fan site is ever a source.

Where the data comes from

Blizzard's patch server advertises every build, and the client's database tables sit on Blizzard's public CDN in CASC archives. We pull those tables ourselves and parse them against a pinned version of the community WoWDBDefs column definitions, so the same build always names its columns the same way. We never scrape Wowhead, Icy Veins, or any other site, and we never copy their data.

How a value gets to a page

Every displayed value carries its build, its table, and its row. A change is shown as:

  1. The build is pulled from the CDN and each table's raw file is hashed and recorded.
  2. Rows are normalized, joined into entities, and the exact values are written verbatim.
  3. The build is diffed against the previous one, field by field, values shown side by side.
  4. A build's page records its BuildConfig, CDNConfig, the pinned definitions commit, and per-table row counts and hashes. See the newest one: build 1.15.9.69722.

How we check ourselves

The build is hermetic and re-hashes every committed file, so the site can only render data that matches its recorded provenance. As independent corroboration we also cross-check a sample of rows, field for field, against wago.tools, a separate parser of the same Blizzard files run by the community. Two independent implementations agreeing is the evidence claim; re-reading our own output is not. That check caught a real parsing bug during our pilot, where a library mis-decoded a signed value; we would rather find that than publish it.

What we deliberately do not do

Baseline synced Sep 16, 2026. Found something wrong? See corrections.