You won't lose any Wykkyd settings with 1.4. That's done. The only way you could possibly lose any settings from my addons due to a game patch in the future is if they completely remove the ability to save data via addon.txt file configured SavedVariable globals. I no longer use the built-in ZO_SavedVar functionality and thus my addons are no longer subject to their patch-day shenanigans.

It wasn't a circular dependency. It's different now, but event then (and now), it was a dynamic dependency... if you will:

Pre-Rewrite:

Outfitter, and the other addons that depended on Framework, did not actually load itself. It asked Framework to load it. So, Outfitter's code would enter Game Client memory but wouldn't spin up. Framework would watch all ON_ADDON_LOADED events and start up all addons that had registered with it. This included Outfitter. So, Outfitter by itself would just sit there and never do anything. With Framework installed, Outfitter would start up via Framework's load process. Confused yet?

Additionally Framework's Macro system would look for the Outfitter globals to exist. If they existed, it would enable the Gear & Skill systems in Macros. If not, it would leave them disabled. The Gear & Skill system enabling would simply issue callbacks to Outfitter's global whenever a relevant Macro was processed (only if the Outfitter global was available to process them).


Post-Rewrite:

Framework's dependency system and features are all gone now.
Framework is now an addon suite, including 5 other addons.
Those 5 other addons encompass most of the functionality of the USER FEATURES of the original Framework.

Outfitter still relies on the control & api functions that the original Framework provided. In fact, all of my addons do. However, that now lives on as LibWykkydFactory which is now embedded as a 6500 line of code single .lua file inside each addon.

LibWykkydFactory loads itself into memory once per MAJOR version number, using the highest MINOR version that all enabled addons embed.

All dependent addons embed their own copy. And they still do not directly register themselves with the game. They call REGISTER_WYKKYD_FACTORY_2, a global method. That registration with LibWykkydFactory inserts a TON of functionality into the registered addon. It also makes LibWykkydFactory handle the ON_ADDON_LOAD event on behalf of the addon, just like the old Framework used to do.


More Importantly, for saved variables

All of my addons USED to use the API-provided ZO_SavedVar controls for pushing data in and out of saved .lua files.

That ZO_SavedVar process hooks your character's specific saved settings beneath your @account name as a key. The original flaw was that if the social system in game was bugged, errored out or simply disabled... your account registered as an empty string, "", to all API calls, including ZO_SavedVar. So whenever that hiccupped, it was as if you lost your saved variables.

More recently ZOS implemented a "fix" to circumvent this "error" in the future. That fix effectively "wiped out" your settings again. In truth your settings still existed, albeit the default method of retrieving them couldn't find them, because ZO_SavedVar wasn't doing the same thing it had in the past.

There has always been an alternative to this. And that is that when constructing an addon you have to provide a .txt file which tells the game how to load your addon. Part of that file can be a parameter called ## SavedVariable (off the top of my head, syntax could be off). And in that line you give it a variable name. THAT did NOT go through ZO_SavedVar and was not filtered by account or character name/id. Think of it as "purely global saved data for that entire addon".

I basically, with my rewrite, manually re-created the character-name filtering of saved data inside those globals. So now your saved information for all Wykkyd addons is still, when appropriate, segregated to each individual character. However there's no @account filtering what-so-ever, so it can never again be bugged by those kind of patch changes.


As for you losing saves on PTS... that was probably A old versions of the addon, or B occurred before the re-write, or C lost saves due to the re-write (the process created all new addons, so those who upgraded did lose all previous settings).


...and there's your TMI-dump for the day.

I all ways copy my all important files for backup monday morn and wed morn before possiable updates on both LIVE and PTS .... TY TY Wykkyd for the detailed explaination, thats invaluable if i have problem this round. Keep up the good work.

You shouldn't have to do anything at all. Mine simply kept working.