Hey there -
Already reported this ingame, but I figure a forum post is likely to get more visibility on this issue. It appears as though the Forever beta isn’t reading in savedvariables tables from file. This is most readily apparent with the Issue Reporter button, whose position gets reset to the center of the screen every time the game’s restarted. It’s particularly noticeable if you run any mods, as any configuration you do won’t persist between sessions.
Worth noting that this occurs for me even with zero mods installed, the Interface and WTF folders wiped, and on both Windows and Linux. The Retail/Midnight version of the game works just fine by comparison, so I suspect this is a beta oversight.
Has anyone else experienced this, and/or found a way around it?
12 Likes
I haven’t logged in yet today, but I know yesterday I would lose any of my UI changes if I didn’t log out. If you make changes and D/C at some point, they won’t save in my experience.
That’s a good thought, but unfortunately this seems to happen regardless of how I exit the game.
1 Like
I was just about to post the same issue. All addon settings reset every session. Every addon’s SavedVariables are correctly written to WTF\Account\<account>\SavedVariables\ when the UI reloads or the client exits, but the client never reads any of those files back when the UI loads. Every session therefore starts with blank settings and data for every addon (third-party and Blizzard’s own per-account/per-character files alike). Only the two top-level WTF\SavedVariables files (Blizzard_AddOnList.lua, Blizzard_Console.lua) are loaded.
Steps to reproduce
- Log in with any addon that has
## SavedVariables: in its TOC (e.g. Prat). Change a setting.
/reload (or log out fully and exit the client).- Open
WTF\Account\<account>\SavedVariables\<Addon>.lua — the changed setting is in the file.
- Log back in.
Expected: the setting is restored from the file.
Actual: the addon is back to defaults. On the next reload the file is overwritten with the fresh session’s (smaller) data; the previous data is left only in the .bak.
5 Likes
I can confirm this behavior that addons are not saving settings at log off.
My experience as well.
I had just gotten to a spot where I wanted to do addons, and noticed Baganator was reseting.
1 Like
Yep, noticing this across all addons I’ve installed in forever. At first I only noticed Platynator (which is highly annoying for it to reset to default), but minimap hides are coming back, etc. for other addons too.
Same issue for me. Also, the Bug Report button doesn’t remember its position, so it’s not just addons.
Can confirm this happens for me as well.
Noticed this with the Battle Map (Shift+M) in the default UI as well. Every time I’ve logged back in it’s moved back to the bottom right of the screen where it is when you first bring it up and has its opacity reset.
Not sure if it’s important, but this wasn’t happening to me earlier (last night), but is happening now.
Tried the launcher’s scan and repair function in the hopes it might help, and if anything it seems worse now. Yesterday, settings were only reset on exiting and restarting the client - now, even a /reload will reset mods and a number of vanilla UI settings.
1 Like
For me it happened last night, seemed fine earlier.
Deleted WTF folder and it seemed to save normally again after that. Broken again now.
This is the exact behaviour I am seeing too. I deleted most of the contents of WTF and then it started saving and working on reload, but when I do a client exit and then launch again, it loads nothing and the next logout/reload save overwrites the files with all the default state.
Same here on 1.60.1.69913, Windows 11.
- I reinstalled the whole Forever folder on 2026-09-18 and removed every addon. It still happens.
- Deleting WTF makes settings survive /reload, but only until the first full exit. After that no addon setting survives, not even a /reload, and the next save overwrites the files with defaults.
- The files in the top-level
WTF\SavedVariables\ do seem to load: Blizzard_Console.lua keeps its history across launches. So it looks limited to the files under WTF\Account\<account>\.
Retail on the same PC saves normally.
I cant even play the game right now. Come on Blizz, push an update!
1 Like
Yeah I’ve confirmed this with an addon of my own as well. It completely ignores the SavedVariables file and just loads the defaults from settings.
TO ALL WITH ADDONS NOT SAVING:
This is a known issue, that has to do with the WoW API. There is nothing anyone can do until Blizzard fixes the problem. We just have to be patient and wait for them to fix the problem with addons not saving.
EDIT: This is also why their own Addon: Bug/Issue Tracker also keeps resetting back to the lower centre of the screen.
1 Like
I have found a work around that worked for me this morning.
I backed up all Lua files in my saved variable folders pertaining specifically to addons (do not back up the blizzard lua files. I believe they are the ones causing the issue.) Just make a new folder on your desktop and copy the “addon”.lua files to the folder. (Make sure to do this when they have the correct settings you need obviously, dont back up wiped fresh ones). Then when the bug happens, log out and delete the entire contents of your saved variables folder. Then copy over your backed up addon.lua files (Do not bring in the old “blizz”.lua files) and your settings should be restored.
It is specifically in one of the the following “blizz”. lua files that is getting corrupted and causing the folder to not work.
Blizzard_CombatLog.lua
Blizzard_GamepadSmartNavigation.lua
Blizzard_PTRFeedback.lua
Blizzard_PTRFeedbackGlue.lua
Blizzard_SavedSets.lua
Blizzard_SharedMapDataProviders.lua
That is incorrect. Those files are not causing any issues.
When I logged in this morning. All my addon settings were reset. I imported my entire backed up saved variables folder (including the aforementioned files) and the issued was not resolved. I then deleted the entire contents of the folder and imported only the addon lua files. New blizzard lua files were created and the issue was resolved. All my existing addon settings were restored. It could just be anectdotal evidence, but its worth noting.
1 Like