Works around a World of Warcraft: Forever beta bug: the client writes addon saved variables at logout but does not read them back at login, so every addon starts empty each session. This addon puts them back.
Windows only (it uses a directory junction). Delete it the day Blizzard fixes the client; nothing else depends on it.
How it works
A saved-variables file is ordinary Lua that assigns globals. This addon's name starts with ! so it loads before every other addon, and its TOC lists your addons' saved files through SV, a junction into WTF\Account\<your account>\SavedVariables. The client runs those files as addon code, the globals exist again, and each addon then loads and finds its data exactly as if the client had read it. Blizzard's own saved files are never listed.
Install
- Unzip so that
!ForeverSVBridge\!ForeverSVBridge.tocsits insideInterface\AddOns\!ForeverSVBridge\. - Log in once and log out, so the client has written your saved files.
- Double-click
setup.batinside the addon folder. It finds your account folder, creates theSVjunction, and lists every third-party saved file in the TOC. If you have several account folders it asks which one. /reload. One chat line at login says what was bridged.
Re-run setup.bat after installing a new addon, once that addon has saved at least once (one logout).
What it touches
Only its own folder: the SV junction, the managed section at the bottom of its TOC, and Manifest.lua. It never writes into WTF. Removing the addon folder removes the junction with it; the saved files themselves are untouched.
Source and issues: https://github.com/KonigTX/ForeverSVBridge

