ForeverSVFix

ForeverSVFix is a temporary workaround for a World of Warcraft: Forever beta bug where addon SavedVariables are written correctly but are not restored by the client's normal SavedVariables loader.

It restores those existing SavedVariables using the same load ordering the addon expects. It does not create a new save format or replace an addon's settings system.

You do not need Python when using a release build.

Download the latest version from the Releases page.

Linux users should normally use the AppImage.

1. Close World of Warcraft completely.
2. Start ForeverSVFix.
3. If asked, select your WoW Forever _classic_beta_ folder and account.
4. Choose 1. Apply / Refresh ForeverSVFix.
5. Choose 2. Check installation.

A healthy installation should report:

Installation:         OK
Active installation checks: OK
No repair needed.

Then close ForeverSVFix and start WoW normally.

If the AppImage does not start when double-clicked, mark it as executable:

chmod +x ForeverSVFix-Linux-x86_64.AppImage
./ForeverSVFix-Linux-x86_64.AppImage

A raw Linux standalone binary is also provided as a fallback.

The normal menu is:

1. Apply / Refresh ForeverSVFix
2. Check installation
3. Settings
4. Check for updates
5. Uninstall ForeverSVFix
6. Exit

Use Apply / Refresh after installing, updating, or removing addons. It rescans the current addon installation, reapplies anything needed, and cleans up ForeverSVFix runtime files that are no longer required.

Windows / CurseForge: Addon updates may replace ForeverSVFix's directory links. If addon settings suddenly stop restoring after an update, close WoW and run Apply / Refresh again. Since v1.0.3, ForeverSVFix should detect and rebuild these links automatically.

When installing a new addon, WoW must first create that addon's SavedVariables file. Enable the addon, enter the game once, optionally change one of its settings, then exit WoW completely and run Apply / Refresh.

A typical workflow is:

First installation:
Close WoW -> start ForeverSVFix -> Apply / Refresh -> Check installation
-> close ForeverSVFix -> start WoW

After an addon change:
Close WoW -> start ForeverSVFix -> Apply / Refresh -> Check installation
-> close ForeverSVFix -> start WoW

Something seems wrong:
Close WoW -> start ForeverSVFix -> Check installation

Uninstall:
Close WoW -> start ForeverSVFix -> Uninstall ForeverSVFix

Uninstalling ForeverSVFix removes the changes it created but does not delete your normal WoW SavedVariables or safety backups.

ForeverSVFix now handles SavedVariables persistence only for EllesmereUI, the same as it does for other affected addons.

EllesmereUI-specific Forever compatibility, including Profiles & Presets unlocking and Action Bar fixes, lives in the standalone EllesmereUI Forever Fix addon.

Recommended setup for EllesmereUI users while the Blizzard SavedVariables bug remains:

EllesmereUI
+ EllesmereUI Forever Fix
+ ForeverSVFix

When upgrading from ForeverSVFix 1.0.3 or earlier, run Apply / Refresh. If the old built-in ForeverSVFixEllesmereUI.lua shim is detected, ForeverSVFix asks before removing it and backs up the legacy files first.

The standalone addon is not downloaded or installed by ForeverSVFix.

Current release: v1.0.4

The workaround has been validated in-game on WoW Forever under Linux/Wine for:

• account-wide SavedVariables;
• per-character SavedVariables;
• addons using both types at the same time;
• settings persistence across /reload, relogging, and full client restarts;
• large addon installations with automatic discovery, refresh, and cleanup.

Testing has included RareScanner, Auctionator, direct diagnostic SavedVariables, and a large mixed addon installation.

Windows builds use directory symlinks where available and fall back to an NTFS directory junction when needed.

The standalone binaries are not code-signed, so Windows SmartScreen or macOS Gatekeeper may display a warning.

By default, WoW loads an addon's normal files first and restores SavedVariables after the last file in the TOC. Addons can explicitly request the opposite behavior with ## LoadSavedVariablesFirst: 1. On the Forever beta, that restore stage is currently broken even though WoW still writes the SavedVariables files correctly.

ForeverSVFix links the addon's live SavedVariables directory into the addon and adds the appropriate SavedVariables restore file to the TOC. By default it loads after the addon's normal files. If the addon declares ## LoadSavedVariablesFirst: 1, ForeverSVFix restores the data before those files instead.

For example:

WTF/Account/<account>/SavedVariables/RareScanner.lua

is made available through:

Interface/AddOns/RareScanner/ForeverSVFixData/RareScanner.lua

The existing SavedVariables file is then executed through WoW's addon-file loader at the appropriate point in the addon's loading sequence.

Per-character SavedVariables use a small generated load-on-demand helper that selects only the current character. If ForeverSVFix cannot identify the character safely, it refuses to restore that data rather than risk loading another character's settings.

ForeverSVFix does not rewrite the contents of your SavedVariables files.

ForeverSVFix checks the public GitHub Releases API for newer versions when you start it.

Automatic checks are cached for 15 minutes. No update is downloaded or installed automatically.

You can also choose 4. Check for updates from the main menu.

The update check sends only a normal HTTPS request to GitHub. ForeverSVFix does not send WoW paths, account names, addon lists, SavedVariables, or telemetry.

All SavedVariables functionality works without internet access.

Because ForeverSVFix does not stay running in the background, update notifications are shown the next time you open it.

Running forever_sv_fix.py directly requires Python 3.10+.

Start the normal interactive menu with:

python3 forever_sv_fix.py

Advanced command-line operations remain available:

python3 forever_sv_fix.py --wow "/path/to/_classic_beta_" scan
python3 forever_sv_fix.py --wow "/path/to/_classic_beta_" install
python3 forever_sv_fix.py --wow "/path/to/_classic_beta_" repair
# If a legacy v1.0.3 EllesmereUI shim exists in noninteractive mode:
python3 forever_sv_fix.py --wow "/path/to/_classic_beta_" repair --migrate-legacy-ellesmere
python3 forever_sv_fix.py --wow "/path/to/_classic_beta_" doctor
python3 forever_sv_fix.py --wow "/path/to/_classic_beta_" status
python3 forever_sv_fix.py --wow "/path/to/_classic_beta_" uninstall
python3 forever_sv_fix.py check-update

If more than one WoW account exists, add --account "ACCOUNT#1".

Before each Apply / Refresh, ForeverSVFix creates a safety backup under:

WTF/ForeverSVFix/backups/

A new numbered backup folder is created each time Apply / Refresh runs, so these can accumulate over time.

The backups are only there as a safety measure. After uninstalling ForeverSVFix, if WoW and your addon settings are working normally, you can safely delete:

WTF/ForeverSVFix/backups/

Current limitations:

• newly installed addons may need to enter the game once before they can be detected;
• addon updates can replace ForeverSVFix patches, requiring Apply / Refresh;
• an addon can still be incompatible with WoW Forever for reasons unrelated to SavedVariables;
• ambiguous per-character folder matches are deliberately skipped;
• Windows and macOS still need native in-game validation.

ForeverSVFix is intended only as a temporary workaround and should no longer be needed once Blizzard fixes the Forever SavedVariables loader.

AI tools were used during development to assist with coding, review, testing support, and documentation.

Development decisions, iteration, and in-game validation were performed manually by the project author.

Copyright © 2026 Simon Ahnfeldt Nielsen.

You may use, modify, fork, and publish modified versions of ForeverSVFix, provided modified releases clearly identify themselves as unofficial and retain credit to Simon Ahnfeldt Nielsen as the original author.

Unchanged official releases may not be mirrored or re-uploaded elsewhere without permission. Linking to the official repository or releases is allowed.

See LICENSE for the full terms.