Azeroth Survivors community save editors: online Shilen vs Godot (2026)

Azeroth Survivors save editor, game backup or build planner?

Start with the file you want to change. The original game exports progress as a .sav. A community save editor reads that progress and writes a modified game file. Our planner instead records a proposed talent route, selected spells and planning notes in companion JSON. Renaming the JSON to .sav does not convert it into a character, and a planner import does not award equipment, talent experience or cleared zones in the game.

An untouched backup is a third object. It preserves the state you may need to recover, rather than the changes you hope to make. Keep it separately from an editor’s output and from any progress already present at the destination. The existing save guide covers the original export and storage questions; this page compares the community editing tools and their documented compatibility boundaries.

Source 2 · Source 3 · Source 4

What Shilen’s current main documentation describes

The reviewed yssadora repository README identifies an unofficial browser editor with local processing. Its v1.5.3 notes describe talent editing across nine classes, an armory of 498 equipment entries, twelve-zone progression controls and an experimental perk-reset feature. These are the author’s feature descriptions. Matching a familiar class or item count does not establish that every record matches your present game build.

The version notes contain useful conditions. They describe handling a third talent specialization while preserving inactive builds, and disabling zone controls when the imported class lacks initialized progression records. That is different from promising to create every missing record safely. The original talent editor’s creator is credited as unknown; Shilen is credited for the armory, zone manager and integrations. We have read the documentation, not audited every browser operation or imported an edited file into the game. For those missing zone records, the v 1.5.3 README suggests playing that class in the game and exporting a fresh save first. That is the author’s next step, not a verified fix for 0.135.1.

Shilen’s author describes the editor as free, and the linked page states that no account is required. Its local-processing claim concerns editing the selected save in your browser; it is not a completed network audit. The served page also loads external fonts, and part of the core script is obfuscated. Download the untouched backup rather than relying on the open tab to preserve it.

Source 3 · Source 7

A request and an open pull request are not a released update

There is a concrete reason to check the project state before expecting star editing. On October 28, alterational opened issue 1 asking about tier-set stars, Marks and achievements. On October 31, iTzCrutchie opened pull request 2 proposing one-to-five-star controls for individual equipment. The contributor says the change was tested with the downloaded v0.131.0 client. That is a contributor’s report about that client, not a test performed by this site.

At this review the pull request was open and the API recorded it as not merged. Its proposed v1.5.4 wording must therefore stay separate from the main README’s v1.5.3. Do not assume that a screenshot or a feature description from that proposal is already on the main editor page. Neither the issue nor the proposed change proves compatibility with v0.135.1. A future merge or release can change this status, so follow the linked project record rather than an undated feature list.

Source 5 · Source 6 · Source 3

The archived desktop editor has a different dependency

The archived oppahansi/azssaveeditor workflow first asks for your own game executable; its adjacent Data/patch.MPQ supplies icons. The author then documents loading an exported .sav or characters.txt and writing a sealed .sav, with a .bak on overwrite. These details describe the author’s 0.104.0-tested setup. They explain why a save alone is not the same input as this desktop route; they do not establish support for a later game build.

The repository is archived, and its latest tested game version is explicitly v0.104.0. The author’s conditional explanation about reading newer game files is not a blanket promise that later versions work. If you cannot match the executable, editor and documented game version, leave that combination unverified. The Godot author also states that the tool bypasses the game’s tamper check and asks users not to share edited saves without the game developer’s approval. Those are author-stated technical and sharing limits, not a safety assessment or permission verified by this site.

Source 4

Import acceptance and lasting progress are separate results

Shilen’s README discusses one player’s comparison in which the same modified save retained progress in Chrome and the downloaded game but reverted after a run in Firefox. The author says the underlying cause remains unconfirmed. That is not evidence that every Firefox installation fails, that every Chrome build works, or that v1.5.3 fixes browser-game persistence.

The distinction matters even when a file opens without an error. Reading or exporting a file in an editor is one result; the game accepting it is another; the game retaining the intended state after later play is another. The author warns that importing replaces the full game save, including Codex discoveries, rather than merging newer progress. Preserve the destination’s original state as well as the source export. Do not clear site data merely to investigate an edited save.

Source 3 · Source 2

Choose the task, then check each import stage

For an unchanged move or recovery, follow the original save workflow; for a talent plan, use this companion. To investigate browser-based editing with an exported .sav, read Shilen’s documented workflow. To investigate a desktop route using your own game files, read the archived Godot requirements and its 0.104.0 boundary. If you require verified 0.135.1 support or released star controls, these records do not establish it.

This site does not receive or edit your .sav.

• Record the exact project address, editor state, game version and one intended change before selecting a file.
• Keep a fresh, untouched source export and separately preserve the destination’s existing progress. An import replaces the save; it is not a merge.
• Keep modified output under a different name. Treat editor output, game acceptance and progress retained after play as three separate results, as the author’s checklist describes.
• If import fails, alters unrelated progress or later reverts, stop repeated imports and retain your originals. Report the first failing step and versions, not a public upload of private saves.

Source 3 · Source 4 · Source 2

Keep the version labels attached to the right object

Three numbers on this page describe three different things: editor v1.5.3, the contributor’s reported game v0.131.0 test, and the archived editor’s game v0.104.0 test boundary. Our separate original-menu observation was v0.135.1, while the companion calculators retain a checked v0.131.0 data snapshot. None of these numbers upgrades another object automatically.

Use the comparison as a dated map of public documentation. It is not a ranking of which editor is safest or most capable, a guarantee that altered progression will load, or an invitation to share edited characters in a multiplayer session. If the relevant project has changed, inspect its current README and release or pull-request state before applying an older guide.

Source 3 · Source 4 · Source 6 · Source 1