As far as I have been able to determine, it isn't a specific add-on that causes this. It can happen with any add-on that has settings. This settings are automatically stored by the Add-on framework in Elder Scrolls Online in the savegame file on the playstation.

I have had to delete the savegame a few times. Each time, I started with a different add-on, set it up as I wanted it and then walked around a bit. If the error didn't show up, I logged out and back in and if I didn't get the error, I installed the next add-on I wanted to use and set it up. At some point, the error popped up again. As I installed the add-ons in a different order, there weren't any specific add-ons that always caused the error to occur. Some times, it happened with an add-on that in the previous install session didn't cause the error to show up (and I used the same settings every time).

A guild member mentioned to me that how he did it was this: after installing an add-on and setting it up, he logged out and closed the game and in the Playstation settings then upload the savegame to the cloud (auto sync for Elder Scrolls Online was off). Then starting the game again and installing the next add-on. Then close the game again and upload the savegame to the cloud. The moment the error popped up, he quit the game and downloaded the savegame from the cloud (the situation where the error didn't show up) and installed the next add-on from there. If that went fine without an error showing up, he uploaded the savegame again and so on. I haven't tried this myself yet. But it shows that it isn't a specific add-on that causes it.

Ingenon wrote: »

PS/

Ingenon wrote: »

PS/NA. I'm not having any issues. I sometimes use these addons:

1. Murf's Skyshards
2. Murf's Lorebooks
3. TSCPriceFetcher/TSC PriceDataLite

I’m using Murf’s Treasures, Votan’s Circular Minimap, and Harvest Map.

katanagirl1 wrote: »

Having worked in software development, I can tell you that if you have a problem with addons you can do a little detective work in the meantime to try to isolate which addons it might be. Usually you would turn off half of them and see if it goes away, then half the remaining ones, and so on.

I’m not sure how it could not be tied to a particular addon instead, but maybe it is the number of addons and the memory used instead that is the problem.

There are multiple posts of people having done this. In this thread and the other one. I've done it myself. Add-on by add-on. And getting different results each time. We have done what we can from the player end.

RoseTheSnowElf wrote: »

But every time I relog or swap toons they always go back to default. I have to redo them everyday.

This was a bug that slightly pre-dates console add-ons.It's (probably) unrelated, but makes add-ons even less effective, since those settings are also not getting saved like they should.

msetten wrote: »

I am not sure yet how it will go when the Save Error pops-up after installing an add-on update. Not sure if it is just a matter of downloading the previous save-game file or if if will be necessary to delete the add-on first. I'll let you know if every get into this situation (but I hope not)

I hope this is of some help to everyone who experiences the Save Error.

I've found that when an update starts giving the error it's because it's started using a problematic Lib file. You can't go back to a previous version once it's already been updated so all I've been able to do is delete it.

After a fair bit of testing, it looks like (for me at least) it's almost always a Lib that does it. I can leave the main addon installed and disabled without a problem but get the error until I remove the Lib; just disabling it doesn't work.

The main offender for me is LibChatMessage because so much uses it. LibRecipe for the Master List does it too and a couple of others from before I started paying attention.

I'm checking update notes for addons now and making sure they don't need extra files and so far so good!

lillybit wrote: »

msetten wrote: »

I am not sure yet how it will go when the Save Error pops-up after installing an add-on update. Not sure if it is just a matter of downloading the previous save-game file or if if will be necessary to delete the add-on first. I'll let you know if every get into this situation (but I hope not)

I hope this is of some help to everyone who experiences the Save Error.

I've found that when an update starts giving the error it's because it's started using a problematic Lib file. You can't go back to a previous version once it's already been updated so all I've been able to do is delete it.

After a fair bit of testing, it looks like (for me at least) it's almost always a Lib that does it. I can leave the main addon installed and disabled without a problem but get the error until I remove the Lib; just disabling it doesn't work.

The main offender for me is LibChatMessage because so much uses it. LibRecipe for the Master List does it too and a couple of others from before I started paying attention.

I'm checking update notes for addons now and making sure they don't need extra files and so far so good!

So if I get save error after update ,remove lib file that was updatet then reinstall lib file that would fix it?

msetten wrote: »

I have found a workaround for the Save Error problem. But it is going to take a lot of work. This is the process:

Ty msetten for the guide, its great. In about 1 week of testing, Ive used a similar process, except that I turned off PS Cloud autosave entirely, so I can vouch that the long method you described is the best. Sometimes by deactivating specific Add-Ons I know was causing the error, the issue may be resolved, but this is rare (and indicates the save file was not 'corrupted'). In most cases, the Save File was permanently affected by the Add-On(s) during testing, and it is better to delete the Save file on the PS5 and download the clean Save File from PS Cloud (ref "Save Error Occurred" pt 5). In my case without Cloud, I go through the routine of launch game, toggle Server Select, Game Startup, Accessibility, Adjust Screen Area, Adjust Brightness, EULA, skip Cinematic, Character Select and Login to retry with Add-Ons. lols.

I would like to add my method with triggering the auto save to aid in testing, in a quick and consistent manner.

Referring to "Installing Add-Ons", point 5 and 6, instead of waiting for an Auto Save, I manually trigger it in 3 seconds.

Force Triggering the Auto Save (Error Testing)
As the auto save happens at various events during the course of play (loading into a new instance), sometimes at random, the most consistent way to manually trigger this can be done in 3 seconds and 6 button presses - Options,X,X,O,X,O. The detailed steps are described below (long because of explanations).
1. After loading into any character (in the 3D environment), enter the Options Menu (screen shows the list of Video, Audio, Gameplay, etc).
2. Enter any sub-Option menu (e.g. Video, Audio, Gameplay etc). No settings need to be changed, you may if you wish.
3. Exit to Option Menu. An auto-save is forced triggered every time you back out of any sub-Option menu, indicated by the spinning Ouroboros symbol on the top right of your screen. The first time you Exit, the symbol should appear and disappear, this is normal and indicates an Auto-Save.
4. Repeat the entering and exiting of any sub-Option Menu a 2ND time (this can be the same or different sub-Option menu, makes no difference)
5a. Upon Exiting the 2ND time, if you again see the same spinning Ouroboros symbol appear and disappear - congratulations, the Auto-Save is successful, and your add-on selections are good-to-go. You should not encounter any more Auto Save Errors for the chosen set of active add-ons, and you may continue with them, or install another to try.
5b. Upon Exiting the 2ND time, if however the second time you enter and back out and are presented with the SAVE ERROR message, then unfortunately, your add-on load out has caused an Auto Save File error.
5c. Upon Exiting the 2ND time, if you DO NOT SEE any spinning Ouroboros symbol appear, nor any SAVE ERROR message, then you may have declined the Save Error prompt (you pressed O for "No" to "The auto save file failed to save correctly. Would you like to try again? If not, saving will be disabled"). No symbol is seen as you have chosen disable saving for the remainder of the instance across all menus, until you Close Game.

IMPORTANT Note 1: When shown the SAVE ERROR message, you enter a game state that ignores any changes to your Add-On and Options menus. Regardless of your reply (X) "Yes" or (O) "No", any change to Enable/Disable Add-Ons or change Option settings will not save between instances and will return to the last known state before SAVE ERROR. In most cases, it is better to choose (X) "Yes", as choosing (O) "No" prevents you from observing whether attempts to fix the error worked or not. With (O) "No", all subsequent error messages will be suppressed. By chosing (X) "Yes", you allow the game to keep giving feedback.

Referring to "Installing Add Ons", point 2.

This step is crucial, and I wholeheartedly concur with msetten - "In the character selection screen..."

IMPORTANT Note 2: Always attempt to Enable/Disable/Install Add-Ons ONLY from the Select Character menu. This is especially true when troubleshooting specific add-ons after SAVE ERROR occurred without closing the game. This is because any Enable/Disable/Install done in the 3D in-game environment may not change the Add-Ons - they may still be in a persistent previous state, ignoring all user inputs. Often I have found the troublesome Add-On to still remain Enabled (even after choosing Disable). Whatever seen on-screen is text refresh without actual changes made. Moreover, performing Enable/Disable/Install in the 3D in-game environment, when successful, applies the change only to the LOADED CHARACTER (unfilled Check Mark in Manage Add-Ons). If while testing you toggled to another character by mistake, this adds another layer of confusion.
I repeat - Enable/Disable/Install Add-Ons ONLY from the Select Character menu.

IMPORTANT Note 3: (Applies to PS5 users with multiple ESO Accounts). Ensure you first Accept the Add-On EULA on EVERY ACCOUNT first, before installing any Add-Ons. This means entering every PS account's Add-On EULA, Accept, immediately back out to ESO start screen (to force an Auto-Save), Close Game, and Switch Accounts. Having any alt account without the Add-On EULA in an "Accept" state may cause Add-Ons to immediately and partially/fully uninstall when you first encounter the Add-On EULA (and prompting install of the same add-on multiple times). If this is you, I suggest to Uninstall ALL Add-Ons and Variables via your main account, delete ALL ESO Save Files across every PS Account on the same PS5 console, and go through accepting the main EULA, Add-On EULA again, for every ESO Account, one by one. If done correctly, you only need to install each unique Add-On ONE TIME, via your main ESO account and they will be detected across all PS Accounts / ESO Accounts on the same PS5 console. All install/uninstall/re-install actions should be performed only via the main account. Yes, this sucks, but I speak from experience (I play on more than just 2 accounts - don't ask how many - its embarrassing)

My observations with the SAVE ERROR
This can occur a number of ways, most commonly -
1. having installed and activated incompatible add-on(s) that conflict with each other, and launching the game.
2. having installed and activated multiple compatible add-ons, which cumulatively breached the memory limit (I suspect the ?? MB / 100MB usage displayed on screen is mis-reported, with the actual load being higher), and launching the game.
- the SAVE ERROR does not trigger from the presence of installed but disabled add-ons. You may have as many of them installed as you want, but disabled, and this is useful for testing add-on combinations. I have not needed to re-install add-ons unless they got auto-uninstalled by some unknown reason (happened 2 times so far after switching PS accounts).
- the SAVE ERROR does not trigger from the presence of Libraries (Lib files). When testing add-ons, my baseline 'good' state is with ALL required/non-required libraries installed AND Enabled, NONE or ONE Add-On installed AND Enabled, manually trigger the Auto Save, and there is no SAVE ERROR. You may test this yourself.

Suggestions to Avoid the SAVE ERROR
- Avoid Enabling too many Add-Ons: Even when Add-Ons are compatible with each other, there exists some 'soft limit' that I assume is related to the Memory usage. I suspect the ?? MB / 100MB usage displayed on the Add-On menu is mis-reported, with the actual Enabled load being much higher (and reaching 100 MB), or the stated 100 MB limit is wrong (and is much lower maybe at 15 MB). From experience, I've been able to Enable between 7 - 11 add-ons without triggering the SAVE ERROR, depending on the add-ons - some require more memory than others. My current thoughts (for U46, until a future update) are that we should approach Add-Ons similarly as we approach Weapon-Gear load-outs - Enable the ones for the current content you are doing, and change them when you do different content. I have put up a separate thread to share tested ERROR-FREE load-outs for Crafting & Trading, Overland questing, New Character Dolmen farming, Dungeon running, Trials running, etc.
- Avoid Enabling incompatible Add-Ons together. These are commonly add-ons attempting to perform similar tasks via similar UI menus / Windows. I have identified these as incompatible:
Update Aug 2: Conflict and UI Error resolved for Map of Many Riches v2.3.8, Destinations v30.02, Lorebooks v96.
1. Map of Many Riches v2.3.0 CONFLICTS WITH Destinations v30.0.0 and Lorebooks v96 - i.e. you may Enable either (Map of Many Riches) or (Destinations and/or Lorebooks), but not all 3 together. UI Error 47605720.
- Avoid Enabling Add-Ons with UI Errors
1. NumbersOnDummyOnly v2025.05.29: UI Error 6BC800B0
2. Antiquities Trader v1.0.5: UI Error CC20C92
3. Undaunted Daily v1.7.9: UI Error 93F07153
- Avoid Enabling Add-Ons that do not perform their stated function (adds bloat to PS5 Memory)
1. Block Item Usage v1.1: all options do not work
2. Points of Color v2.55: map pins are blocky squares
3. Whispers Beyond v1.0.2: text is too small to be read, no options to increase font size.
4. Awesome Guild Store v1.7.4: all 11 toggle options do not work, references 11 libraries.
5. Destinations v30.0.0: some map pins are blocky squares, or semi / 100% transparent (invisible but able to hover over map to see tool-tip) (all map pins display correctly as of v30.02).

Edits: corrected typos and phrasing for clarity
Edit Aug 2: updated for Map of Many Riches v2.3.8, Destinations v30.02, Lorebooks v96.

The really frustrating thing about this is there isn't a master list of things to avoid and it's different for everyone. It was mentioned above that Lib files are never a problem; it seems to almost always be them for me. LibChatMessage causes it for me every time, even with everything else disabled or uninstalled

Perhaps there is another option, restore from cloud save if file is corrupted and then turn off cloud updates. Has anyone tried this?

katanagirl1 wrote: »

Perhaps there is another option, restore from cloud save if file is corrupted and then turn off cloud updates. Has anyone tried this?

I'm doing exactly that with positive results. The initial setup takes a bit, but all of my addons are firing on all cylinders. Though I did make it a point to avoid crossover addons (ie.. I installed Murf's Treasures but not MoMR since they both point out t-maps and surveys, and CleanLeadsUI but not LeadReminder since they both touch on Scrying leads).

I've been doing much the same as others; running long changing sequences of add-ons. Eventually you will always trigger the cannot "autosave". I can pretty much say that there is a hard limit to the number of configurable add-ons dependent on how configurable items they have within them.

For example I had a set of the add-ons installed successfully then triggered the failure. Removed the last add-on and returned to a stable state. Then removed the Artaeum Group Tool; still stable. Installed 3 more configurable add-ons before I encountered the failure. The AGT is highly configurable and it appears that there is limited "configurable space" once I removed it more add-ons with less "configurable weight" could install.

To test this further I continued from my last stable point and only installed add-ons that had no configurable state. These all installed without triggering the failure. One that appeared to have no configuration did trigger the failure but when I uninstalled it but left a lib it required the failure persisted until I removed it as well. I suspect the lib had hardcoded configuration within it.

So it appears there is a maximum amount of configuration the autosave can handle and this is not a memory issue.

@Bodolphin @raystormusa

If the error is related to Max Configuration, you'd think Fancy Action Bar, CrutchAlerts and Lazy Writ Crafter would be the add-ons causing the most problems. Those have a huge number of configurable options. I'm more intrigued by the Memory Usage, although more options = more memory, of course. I installed Artaeum Group Tool once, but don't have it on right now. I remember it having a lot, but not how it compares to Fancy and Crutch.

In the release notes for HarvestMap, Shinni42 says:

Remark on memory usage:
ESO sets a hard limit on memory/RAM usage. All your active addons together may not exceed 100 megabyte of memory.
HarvestMap requires 7 mb of memory.

This is why I started tracking how much memory each add-on, and their associated libraries, takes up.
I don't see any way to get the "run memory" vs the "install memory" on playstation, at least. (I know there are real developer names for those, I just don't know what they are.)

So only working with Install Memory, and I'm way below any limit I've seen, including the 15M one I believe @raystormusa mentioned.

And HarvestMap is listed on the Bethesda page as taking up 528.1 KB, nowhere near the 7M they mention in the notes. So I'm assuming that's the run memory. I wish the rest of the developers gave a range for what theirs is.

Every setup I've tested is under 10M installed, and I'm getting the error at around 3.5M.

allochthons wrote: »

I don't see any way to get the "run memory" vs the "install memory" on playstation, at least.

I am seeing the same problem. On my Add-On menu screen, it reads 11.7MB/100MB and this number does not change no matter what is Enabled/Disabled. Its simply the total Installed memory. I have no idea what the actual "Enabled" utilization is for my Add-Ons.

It has also occurred to me that a smart add-on developer could be minimising autosave elements by only saving those that are changed from a default. Any add-on that offers reset defaults could be doing this as it must be storing the default in code.

(reposted from this thread )

Market Tracker v2.1.2 seems to be a consistent cause of the Save Error.

Steps to replicate error (PS5):
1. Restore a clean Save File from PS cloud, or delete local Save File and restart game.
2. Accept Add-On EULA, Enable only Market Tracker v2.1.2 and all required dependencies (Market Tracker Data Loader, LibText), and nothing else.
3. Load any character.
4. Force-trigger Auto Save by Enter-Exit two times via any sub-Options page (Video, Audio, etc), or if force-trigger fails (false save success), wait a few seconds for the Save Error to appear.

Solution:
1. Disable this Add-On to avoid it, or
2. Enable this Add-On, but upon getting the Save Error message, choose (O) No to stop attempts to Auto Save and continue playing without saves. (game is still functional, with settings fixed as per the last error-free save. Difference in that new settings will not be saved).