How we read this

The one rule

We never publish a number that did not come from the game's own files, or from the game's own formula over those files and marked as computed. No fan-site data, no player data, no guessed values. If the client does not contain a fact, the page says so rather than filling the gap.

Pull the build

We pull each build from the publisher's own servers, table by table, and hash every table so a re-read is verifiable. We never scrape another fan site, and we never read a value off a screenshot or a patch note.

Diff every table

Each build is compared against the one before it, keyed on the entity's own stable id, not on a row number that shifts between builds. Engine noise that no player can see is counted apart from a change a player can feel, so a verdict of buffed or nerfed means what it says.

Publish every record, changed or not

Every entity a player can obtain or use gets its own page, stamped with the build it was read from and the date it was read. Rows the client marks unused or unreleased get no page until the game shows them to players. A row whose page would be thin, with no numbers and no relations, gets a page that search engines are told not to index.

What we do not claim

Drop rates, drop locations, vendor prices and loot chances live on the game's servers, not in the client, so we do not state them. Where a page would be expected to, it says plainly that the game files do not contain that fact.