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.
So, I think a few vault-tools would be VERY useful because then the author could have programmed into his version 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.sav-flush commands to run on the first download of the age
Users browsing this forum: No registered users and 1 guest