Lontahv wrote:SDLs should be the first thing to be updated and should be auto-refreshed every time the ULM starts. The reason for this is to strive toward more dynamic ages. Maybe not
always at startup but there should at least be a "update all age states" button.
You wouldn't want to update the SDL separately from the rest of the Age data. The two are made to function together.
So, I think a few vault-tools would be VERY useful because then the author could have programmed into his version of the age
I agree, but modifying the vault's SDL nodes is really only useful for cheats, or testing different states.
sav-flush commands to run on the first download of the age
On first download of an Age, there wouldn't be anything to flush. SAV files are created when you visit an Age, after the instance has been assigned a GUID. There should never be a need to flush them on the client-end, either. The only real problems that crop up are with the complex types that are stored in there and are changed during development. Useful for development, yes, but wholly unnecessary for the end-user.
It really depends on what you're trying to accomplish, Kato. If you want to PM me with your idea (since it appears you don't want to disclose it publically), I can discuss with you some possible options for doing it that would be most appropriate.