Originally Posted by Psiioniic
I think that depends on how add-on authors implemented it. I'd say most common way is per account/character, but might be different for some add-ons.
You can look at the individual saved variables lua files to be sure before accidentially overwriting them (and also backup all of them before).
account wide looks often like this (when it was created via ZO_SavedVars:NewAccountWide):
Code:
... =
{
["Default"] =
{
["@AccountName"] =
{
["$AccountWide"] =
{
instead of the @AccountName, there could be also an $InstallationWide here instead. Or no mention of the account name, then it's also installation wide. |
Hey Psiioniic, thanks for replying! So I followed what you said and browsed through some of my main add on saved variables, and the lua files are as formatted as you quoted with the "@AccountName". So I'm not familiar with coding at all and I'm trying to understand what you said. Does accountwide ... '@AccountName" mean that the addon will hold all saved variable settings for both my accounts in the lua files? And that, even when I swap from one account to the other, the data and settings will be saved per account? So that, ideally, when I log into account 1, make changes to addon A's saved variables, log out and into account 2, make changes to addon A's saved variables, then log back into account 1, addon A's saved variables specifically for account 1 are still there and the same for account 2's?
Also, if it's installation wide, does that mean that once I log out and log into another account, all the saved variable settings for the previous account will be overwritten when I log into the second one, and vice versa?
Thanks if you can help clarify this a little more for me. I appreciate your patience and your response!