File Integrity Check
After each save, NanoSave checks the file for corruption. If it finds a problem and a backup exists, it tries to restore the backup.
You can use a Game Creator Trigger to react to a corrupted save, for example by showing a warning to the player. The damaged file stays in the save folder so it can be sent for investigation.
Dynamic Metadata
NanoSave metadata fields are string properties under Game Creator 2 Settings > General. You can connect them to Global Variables and change the metadata at save time.
NanoSave Lite
NanoSave Lite works like Game Creator 2's JSON save system, but uses Gzip compression to reduce file size.
It does not include metadata, backup saves, integrity checks, or automatic screenshots. Use it when you want a small and simple save system.
Encryption and Copy Protection
NanoSave supports no encryption and XOR encryption from Game Creator 2.
Enable Copy Protection binds a save to the hardware where it was created. A player cannot move that save to another computer or device. Hardware changes such as a new drive or motherboard can also make the save invalid, so use this option only when that tradeoff is acceptable.