Azeroth Survivors addons

Azeroth Survivors addons should come from the addon author’s release instructions for the correct game. The local checker’s guide explains 4 results: TOC found, no TOC, unsupported archive and unreadable archive. Use that result to check packaging before installation; readable structure does not certify compatibility or safe execution.

Two different addon meanings

An interface extension for Aethus’s original is different from the AzerothSurvivor remake installed inside WoW. Read the project author’s description before choosing instructions.

Source 2 · Source 3

What a package check proves

The original browser loader identifies addon folders through .toc files and supports specific ZIP methods. Its published code also handles wrapped folders and same-name replacement. A local precheck can report structure; it cannot establish runtime compatibility or safe behavior.

Source 1

Keep the original instructions

Use the addon author’s current release and installation notes. Before replacing an existing package, keep a copy of settings where the author documents them. Do not execute an unknown script merely because an archive passed a structure check.

Sources

A practical case to work through

Read the steps and decision points

Read a ZIP result as a packaging result

The local check reads directory/TOC structure. It does not execute Lua, install the addon or certify runtime compatibility.

Result	Useful next step	What it does not prove
TOC structure found	Read the author’s release and installation instructions.	That the addon works with this game version.
No .toc found	Check that you chose the intended addon package.	That renaming an unrelated file to .toc will make it an addon.
Unsupported archive	Obtain a supported ZIP from the author.	That changing a .rar or .7z extension converts its format.
Could not read archive	Keep the original; obtain an intact package and retry.	That your installed files or game save were changed.

ExampleAddon/
  ExampleAddon.toc
  main.lua

Illustrative directory only, not a download or a required author filename. The real TOC and release instructions determine the files to use.

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.

A package passes, but the feature still does not appear

Imagine the local ZIP checker finds a TOC file but the expected interface feature is absent in the game. The successful result only confirms the structure the checker inspected. For example, a folder containing its addon TOC is a packaging question; whether the chosen release uses the current game API is a separate compatibility question. Identify the original game, addon author, selected release and exact install instructions first.

Keep the previous package and documented settings before replacing them. Review the author’s current layout and any wrapped-folder instructions instead of executing an unfamiliar script to force a result. Record whether the package was rejected, loaded without the feature, or produced a visible error. The browser precheck does not upload, execute or install the archive. It cannot certify safety, runtime behavior or support for every addon merely because the folder structure is readable.

Azeroth Survivors addons · questions

Which two meanings of Azeroth Survivors addon matter?

An interface extension for Aethus’s original is different from the AzerothSurvivor remake installed inside WoW. Read the project author’s description before choosing instructions.

Does a valid ZIP prove that an addon works?

The original browser loader identifies addon folders through .toc files and supports specific ZIP methods. Its published code also handles wrapped folders and same-name replacement.

Which installation instructions should I follow?

Use the addon author’s current release and installation notes. Before replacing an existing package, keep a copy of settings where the author documents them.

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.

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.

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.

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.