How many times have you crashed while editing a script, and lost unsaved changes? If it has happened even once, then you will love this. And it is fully automated, no settings, no fuss.
Open scripts are auto-saved locally every 60 seconds. In event of a viewer crash, scripts are presented to you at login, and you may optionally select one or more to recover; they will be placed in the Lost and Found folder of your inventory.
Backups are only saved if the script has been modified. Backups are removed when a script is successfully saved back to inventory, or the script window is closed.
Occasionally you may find that backups get stuck for some reason. The following dialogue will appear, and frequently it will appear for all alts (as the viewer doesn't know who “owned” the script)
The first solution is to “restore” and then simply expunge the unwanted ones from your lost+found however if this does not work and the dialogue continues to appear afterwards then manually removing the backups (possibly as an admin) is required.
The files are stored in the temporary file directory for your operating system and are named with an extension *.lslbackup
On Windows: The GetTempPath function checks for the existence of environment variables in the following order and uses the first path found: The path specified by the TMP environment variable. The path specified by the TEMP environment variable. The path specified by the USERPROFILE environment variable. The Windows directory. The simplest way to check/verify is by examining the environment variables
On both Mac and Linux: FS uses the TMPDIR environment variable
char *env = getenv("TMPDIR");
removing all files matching '*.lslbackup' in the above directories will stop any further nagging.