AZEROTH SURVIVORSCOMPANION · INDEPENDENT TOOLS
Home/Azeroth Survivors data sources
AZEROTH SURVIVORS · COMPANION

Azeroth Survivors data sources

Trace current client facts, menu evidence and separate historical references.

How are these data sources used?

Azeroth Survivors data sources cover 355 talent nodes, 1,121 rank-effect records and 498 unupgraded equipment records from the original client. Field labels distinguish static definitions from menu observations and the limited Warrior run. Check that label before treating a displayed effect as current or an outcome as tested.

Current coverage includes nine class openings and 103 spell identities, 355 talent structures and 1,121 rank descriptions, 498 base equipment records, 564 source associations and twelve zones with sixty bosses. The source boundary is attached to individual fields. Historical spell numbers and unverified special effects stay labelled rather than becoming current facts simply because the surrounding page has a newer date.

Reference client v0.131.0 (e7d9dd47), checked 31 Oct 2026. Primary-checked fields are labeled; historical v0.125.0 values stay separate. See Sources & method for coverage.

Client, historical and control-plane data sources

Public calculator catalog ↗

Talent names/ranks/positions/constraints; skill mechanics; gear stats and documented drop associations; run items and race facts.

  • Original artifact hash is a source claim, not independently reproduced.
  • Page display version and embedded data provenance disagree.
  • Source reports incomplete prerequisite/refund playtesting.
  • No game package or WASM downloaded; no original-game menu or combat test performed.
  • No competitor images, UI code, editorial builds, recommendations or translations included in public GAME.
secondary-structured-facts · 2026-10-31

Zone directory factual entries ↗

12 zone names/order/final bosses and arrival times; first eight documented unlocks.

  • Directory attributes initial catalog to October 20, 2026; later unlock conditions explicitly unconfirmed.
  • Boss lists are cross-referenced from gear drop associations, not independently verified timelines.
secondary-catalog-facts · 2026-10-31

Aethus original game entry ↗

Original play/download/community entrance only.

  • Original current talent, item and cost rules were not inspected in-game.
primary-entry · 2026-10-31

Original browser launcher ↗

Host guard; browser/GPU errors; local save rescue; browser runtime setup.

  • Code branch existence is not a device-tested repair result.
primary-public-client-text · 2026-10-31

Original save file bridge ↗

Original Options/Saves file bridge; sealed account text.

  • No decrypted schema, merging support, or cross-version import validation.
primary-public-client-text · 2026-10-31

Original browser addon loader ↗

ZIP/.toc discovery, supported ZIP compression and same-name replacement.

  • Structure support does not establish addon API or game-version compatibility.
primary-public-client-text · 2026-10-31

Original 0.131.0 public client: static metadata ↗

Current version/build; 27 trees, 355 talents/1121 rank effects plus prerequisites/exclusions; 498 base equipment stat records and564 drop associations; 12 zones/60 bosses; upgrade price/stage-cap rules;39 named run-item records and explicitly scoped constant effects. Reproducible static extraction scripts retain function/table provenance locally.

  • Original WASM was parsed as bytes, never executed.
  • Reviewed formatter arithmetic is transcribed in extraction scripts, not original code execution.
  • Combat application, random drop outcomes, star-bonus effects and actual purchase transactions have not all been verified.
  • Run-item/spell dynamic numerical effects and individual legendary remakes retain separate verification limits.
primary-public-client-static-data · 2026-10-31

Menu sample data sources

The following named selections were captured in the original client on 2026-10-31. Talent samples corroborate their visible rank, requirement or effect fields; equipment samples corroborate the selected piece and displayed source. These observations are not combat tests or random-drop experiments. The shared limitation is stated once here instead of repeated under every selection.

SelectionOriginal entry
warrior talents enView original client ↗
warrior level2 dynamic valuesView original client ↗
paladin first talentView original client ↗
hunter first talentView original client ↗
priest first talentView original client ↗
mage first talentView original client ↗
druid first talentView original client ↗
warlock legion gate currentView original client ↗
warlock pact currentView original client ↗
recruits helm detailView original client ↗
warrior common shoulderView original client ↗
warrior common chestView original client ↗
warrior common waistView original client ↗
warrior common legsView original client ↗
warrior common feetView original client ↗
warrior common wristView original client ↗
warrior common handsView original client ↗
warrior common main handView original client ↗
warrior dreadnaught helmView original client ↗
warrior sulfurasView original client ↗
mage uncommon headView original client ↗
character enView original client ↗
late zone unlocksView original client ↗

Sources & method

Azeroth Survivors Companion

Azeroth Survivors data sources · questions

Which client version is documented?

The checked reference is original client 0.131.0, build e7d9dd47. Static definitions, menu observations and the short Warrior run have different scopes. An accepted plan is not a tested clear or a damage benchmark.

Are these builds a tested power ranking?

No. Build articles are editable editorial starting ideas. Check the required opener, point stage and actual equipment; no completed-run or DPS ranking is claimed.

Are source claims and independent checks the same?

No. Records distinguish original static definitions, observed menus, limited gameplay and historical secondary material. The methodology page explains field-level coverage and unknowns.

What happens to a version 0.125.0 draft?

The old record remains separate. Review a copy against current rules before saving. A route that no longer satisfies prerequisites is refused; the original can still be exported.

Does a calculated price prove the upgrade is unlocked?

No. Ownership, the class’s Heroic unlock and affordability are separate checks. Unknown set counts stay unknown, and the quote panel never silently overwrites your manual budget.

Does using this companion require an account?

No account is required. These companion tools run in your browser; drafts and progress are kept in this browser profile. Export a copy before clearing browser storage or changing devices.

Access, storage and evidence limits
  • Free and unlimited use · 0 USD
  • No sign-up
  • Browser storage
  • JSON / PNG exports

Browser storage limits apply. PNG exports include the site title; there is no paid watermark-removal option. These are companion features, not original-game save recovery.