*.sav files messing up everything?

[Aloys]

Lately I've found that the save files tend to mess up stuff that shouldn't belong to them. Latest issue: after pulling my hair out for a couple solid hours over some texture animation problem, it turns out the solution was to delete the .sav file for this Age and that's it! Are animations settings saved in there?? Why??
I remember someone had a similar problem not too long ago that was solved the same way... can't remember what it was. (maybe it was a texture animation issue too, thinking of it..)
Do we know exactly what is saved in those files, why, and more important do we have a way to avoid saving anything in there?

[Tsar Hoikas]

Anything based on plSynchedObject has its state saved in them.

Add the class type to the plSynchedObject's SDL Exclude List....

[Nadnerb]

The current sound emitters will have their state saved like this as well, which is probably where you saw this issue before.

[Aloys]

I guess there's no easy & lazy method; to exclude all of the Age from the sav file or something similar? I have no idea how to add anything in the SDL files.

[D'Lanor]

The SDL files contain only a fraction of all that is saved into the age state. I don't think there is anything an age builder can do. I am sure that was a programmers note from Hoikas.

This would not be a big problem if we could properly delete explorer ages (set them volatile) like we do with personal ages when we push back books in the shelf. An idea for a new ULM feature perhaps?

You cannot expect from users that they manually delete sav files from their vaults each time we update our ages. And then I do not even want to think about the vault in the online version.

[Tsar Hoikas]

The SDL files contain only a fraction of all that is saved into the age state. I don't think there is anything an age builder can do. I am sure that was a programmers note from Hoikas.

That was a note to the current PyPRP devs mostly. I think Paradox or someone has implemented what I described in AlcScript since then, so it might be worth a shot to check the SVN (recommended only if you feel like picking through the changed code). I dunno though.