AI-generated fantasy illustration · not gameplay or official game art.
AZEROTH SURVIVORS · COMPANION

Azeroth Survivors not working

Identify the version and failure stage before changing settings.

Loading…

Sources

Know what your plan is built on.

If Azeroth Survivors is not working, select one of 4 environments: browser, Windows, addon or reconstruction. Match the exact symptom to receive relevant checks; a busy host, a graphics failure and missing progress require different actions. Optional ZIP inspection reports folder and .toc structure without installing the addon.

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.

Show sources →
9

Source-labeled data

Choices and stated effects are compared; no DPS, clear chance or drop-rate prediction is calculated.

Azeroth Survivors not working · reference

Read the workflow and current factual reference

Project and version

Confirm the original creator entrance and client version. The WoW addon and an independent rebuild are different projects; a fix for either is not automatically a fix for the original. Keep the exact page or package source with the version.

First failing stage

Record whether the problem occurs before loading, while selecting a character, after starting a run or after enabling a package. A black loading screen and an input problem during a running game require different next checks.

Browser and graphics

Keep the actual browser name, version and graphics error text. Compare one controlled change at a time. A narrow desktop viewport is useful for layout testing but does not reproduce a phone graphics driver or memory limit.

Input and viewport

Separate a clipped panel from an unresponsive control. Note orientation, zoom, pointer or touch input and the first control that fails. A screenshot should include the affected control without exposing a personal save or account token.

Addon package structure

The local ZIP checker inspects a file list and manifest shape. It does not execute the addon or establish that the package is safe or compatible. A successful structural check therefore remains separate from enabling the package in the original client.

A useful reproduction

Write the smallest sequence that produces the issue, the result you expected and what actually happened. Include the current route and version. Repeating an identical failed action without changing the recorded conditions adds little diagnostic value.

Keep a useful error record before changing storage

Select the actual client and symptom above. These three distinctions prevent unrelated fixes from being mixed together.

Visible problemFirst distinctionUseful next action
429 / too many peopleHost-side limit, not proof of a broken save.Wait/retry later or follow the creator-linked client route.
WebGPU / no adapterDevice/browser graphics path, not the same as a busy host.Keep diagnostics and the exact device/browser details.
Progress appears missingProfile/origin and save identity, not automatically file corruption.Return to the previous entry/profile and keep a backup before importing.
Game entry:
Game version/build:
Platform and browser:
Exact visible message:
Step that failed:
Backup kept before changes: yes / no

Copy and fill locally if needed. This note is not automatically sent; omit complete saves, private invitations and account credentials.

See a missing-TOC result
Companion ZIP check reporting no TOC in a synthetic example archive
Actual English interface with a synthetic ZIP intentionally missing a TOC. This packaging example does not test a real addon or certify compatibility.

Version and evidence boundary

The current reference uses original client 0.131.0, build e7d9dd47. Static definitions and selected menu comparisons establish the named fields. They do not establish a combat benchmark, a guaranteed random drop or a successful purchase. Historical 0.125.0 information appears only inside an identified historical reference.

Show sources · Sources & method

Azeroth Survivors not working · questions

What should I record before diagnosing a startup failure?

Record the project and client version, device and browser, and exact error. Missing WebGPU, no usable adapter, device loss, a busy server and an invalid addon ZIP are different failure stages.

Can this site install an addon into the game?

No. Its local ZIP checker examines archive structure and TOC entries. It does not run the addon, install it or establish compatibility with a client version.

Can a planner export recover my game save?

A companion JSON file restores this site’s plan or progress record. It cannot restore an original-game character. Use the original game’s own save controls for game backups.

Does the companion test every phone for game compatibility?

No. Responsive companion controls and the original game’s graphics or touch support are different checks. A narrow desktop viewport is not a physical-phone game test.

Where do I play the original Azeroth Survivors?

Use the creator’s entry at wow.aethus.pl. This independent companion provides planning tools and guides; it is not the game client.

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.