π½Configuration
Settings

Storage β The save system being used
Title β The title of the save slot (e.g., "Prologue").
Save Slot Location β Describes where in the game the save was created (e.g., "Unknown Location").
Save Slot Progression β Displays the player's progress percentage (e.g., "0%").
Save Slot Total Playtime β Shows total time spent in the save file (e.g., "0h 0m").
Character Level β The player's level at the time of saving (e.g., "Level 1").
Folder Prefix β The prefix used for saved file names (e.g., "NANOSAVE").
Backup Save File β Whether a backup of the save file is created.
Take Screenshot β If enabled, captures a screenshot when saving.
Screenshot Resolution β Determines the quality of the saved screenshot (e.g., "Quarter" resolution).
Layer Mask β Specifies which layers are included in the save screenshot (e.g., "Default, TransparentFX, Water, UI").
Backup
When the "Backup Save File" option is enabled, NanoSave automatically creates a backup of the save slot before overwriting it.
Screenshot Save Slot Preview
NanoSave automatically captures a screenshot of the game when the "Take Screenshot" option is enabled in the settings.
If you want to exclude the game UI from the screenshot, remove it from the Layer Mask settings and ensure your UI elements are assigned to the appropriate layers.
It's recommended to keep the Screenshot Resolution on the lower side to prevent performance drops. Higher resolutions may cause noticeable frame rate issues.
File Integrity Check
After each save, NanoSave performs a file integrity check to detect corruption. If a save file is found to be corrupted, NanoSave will attempt to restore the backup if one is available.
You can set up a Game Creator Trigger to detect corrupted save files and implement custom visual scripting logic, for example, warning the player that their last progress wasn't saved and that the current session may be affected.
The corrupted save file will still be available in the save slot folder, allowing players to send their corrupted saves for analysis to help identify potential issues.
Dynamic Metadata
NanoSave's metadata options, found under Game Creator 2 Settings > General, are string properties. This allows you to dynamically update metadata when saving the game by using Global Variables.
NanoSave Lite
NanoSave Lite is a streamlined version of the save system that works similarly to Game Creator 2βs default JSON save system but with Gzip compression, reducing save file sizes.
To keep it lightweight, NanoSave Lite does not include metadata, backup saves, file integrity checks, or automatic screenshot capture. This makes it a suitable choice for small projects that donβt require dedicated save slots and prioritize minimal storage usage.
Encryption
NanoSave currently supports Game Creator 2's no encryption and XOR encryption only.
Copy Protection
When the "Enable Copy Protection" option is enabled, NanoSave will bind save files to the current hardware configuration of the device. This feature is designed to prevent save file tampering and transfer of progress between systems.
Use with Caution Copy Protection should be used with care. While it enhances security, it also comes with limitations that can affect player experience:
Device Locking: Save files are locked to the specific hardware they were created on. Players will not be able to transfer their saves to another computer or device.
Hardware Changes: Any significant change in hardware, such as replacing a hard drive, upgrading the motherboard, or moving the save file to a new device, may trigger the copy protection. When this happens, the save file will be considered invalid and rejected by NanoSave.
Last updated