ToME: the Tales of Maj'Eyal

Simple app i made in NSIS to backup automatically your saves as they are modified.

- Use it as a launcher, works also if the game is already running. It automatically quits with the game.
- You can rename the launcher anything you like. The ini file must be called {same as exe}.ini or tomebkp.ini (gamebkp.ini for the generic version), both are valid, former have priority and is created with that name if no ini.
- Backup number zero is always the replicate of the actual saves.
- To know the date and time of each backups, look at the 'date modified' column in windows explorer.
- It works nicely with default config if you put it in the game folder.
- Works for most games that uses a separate folder to store its savegames, just edit the ini.

There's almost no differences between the tome and generic builds, in the generic build all "tome" strings being "game" and it have a transparent icon, thats it.

Edit:
0.2 - First working version
0.3 - Possibility to set options in a ini file.
0.4 - Added an option to set a minimum time between backups. Several small bug and stability fixes.
0.4.1 - Bug fixes: Ini file rewriten with default values at each launch (fixed). Could not quit and enter the game rapidly (fixed). Other adjustments.
0.4.2 - Bug fixes: Problems if some bkp files were locked (fixed). Small bug with the time comparison under certain conditions (fixed).

Why not just donate a little and get the infinite lives version?

Simple debug mode would do the same thing as explorer.

That said, save backups are useful for considerably more than savescumming, especially in a beta game. I've had at least one (very promising) character that was completely borked by its save file getting screwed up -- having a backup would probably have let me recover the bugger. Save file backup's just a useful feature for a potentially unstable game.

Just uptated my tool to v0.4.2.
It mainly fixes the problem if some bkp files/folders were locked, they were even issues when windows explorer was open to a bkp dir.
Fixed by using the api function SHFileOperation instead of the basic nsis instructions, changing the algorythm a bit and adding a warning prompt that let the user correct the situation, if nessessary.

How do I use this?