What does data verification mean?
Azeroth Survivors data verification checks individual fields: 355 talent structures, 1,121 rank effects and 498 base equipment records are traced to original-client definitions and formatters. Menu samples and the short Warrior run are recorded separately. Use the coverage notes to distinguish a checked constant, a formula and an untested gameplay outcome.
Identity verification
Identity verification reads the original native token and its current displayed name together. This matters when a label changes without a new identity. Pact of the Nathrezim keeps the site’s legacy annihilan identifier so an old link still identifies the same talent. That label correction is not evidence that its effect changed between game versions.
Numerical data verification
Numerical data verification keeps base operands, rank conversion and display rounding distinct. The current Recruit’s Helm menu shows0.7% critical strike where the secondary snapshot rounded to1%. Sulfuras has a38.64% underlying damage modifier that its menu displays as39%. These differences are not automatically patch balance changes. A displayed run-card damage value can also include active character conditions.
Rule and route verification
Rule verification follows the current prerequisite and exclusion branches. A row opening every five tree points does not bypass a required talent. A checked predecessor requires its full rank, and an alternative group can accept either completed branch. Route verification replays the allocation order, because removing an earlier point can leave a later step without its prerequisite even when the final total is unchanged.
Menu verification
Menu verification is a second view of selected fields, not a substitute for reading all definitions. Twelve equipment selections and seven talent selections were compared with the current extraction. The normal Warrior run established visible six-slot progress, but it did not earn a boss drop or purchase a star upgrade. Those unperformed transactions remain outside the verification scope.
Historical data verification
Historical data verification protects the original draft before checking a copy. The0.125.0 snapshot stays separate from current0.131.0 data. A migrated route must pass current ordered rules before saving as a current record. A failure does not erase the original. A quote likewise does not establish that the player owns the piece, completed both Heroic source zones or has enough Marks.
Correction verification
Correction verification needs a reproducible claim: the page, client version, class, selected field and expected versus observed result. Attach the smallest relevant source or menu observation. Do not include a private save, token or account detail merely to report a wrong number. The local correction report is a downloadable record; it is not an email delivery receipt.
Opening-ability data verification
The typed opening-ability fields identify24 talent nodes:18 grant nodes and6 replacement nodes. A grant preserves the default opening spell and adds its named ability. A replacement removes the default and selects its replacement. This distinction is evaluated at the current route checkpoint and must fit the six planned skill slots. A sentence saying that a talent changes the opening is not enough to decide which operation it performs.
What remains unknown?
- Dynamic spell damage is not a fixed baseline; no DPS simulator is claimed.
- Twenty-four special legendary constructors and some proc details retain their explicit limits.
- Two rings and two trinkets are site planning capacities, not verified original slot limits.
- Original reuse rights, public operator contacts and production indexing are not proven by technical data verification.