Yes, it is.
But afaik the directive ## DisableSavedVariablesAutoSaving: in the manifest of your addon only applies to the "small data written without a reloadui/loading screen due to zone change/logout".
With small data I mean the "important SavedVariable" changes which were introduced later on (with Murkmire I think) so that very important data can be written directly to the SV without having to wait for the logout or reloadui or zone change.
Normal SV will always update on logout and reloadui. I'm not quire sure if the zone change is the same as reloadui in this case but I think the SV are always written at this time as well.
From the wiki (
https://wiki.esoui.com/Addon_manifes...esAutoSaving):
Code:
DisableSavedVariablesAutoSaving
Starting with the Murkmire Update (100025) the game periodically writes the saved variables for each loaded add-on to disk. It will attempt to write data during regular gameplay, as long as the resulting file is not bigger than 50kB and the write can be done within 4ms. Otherwise it will wait for the next loading screen. It will always wait at least two seconds between writing data to disk and 15 minutes before saving the same file again. When the DisableSavedVariablesAutoSaving is set to "1", it won't consider the saved variables of this add-on for autosaving.
To make data save with this auto save function of ZOs I think you also need to use the function "RequestAddOnSavedVariablesPrioritySave" in your addon so it will "register for data to save" (restrictions: <=50kb and saved within 4ms, like changing a very important setting from 0 to 1 or similar).