save-system

To save game state across Unity scene transitions, implement an ISaveable contract on stateful MonoBehaviours and use a central SaveManager to aggregate and serialize component data to disk. This preserves player progress reliably between scene loads.

Save file versioning in Unity is handled by storing version metadata within a JSON dictionary wrapper. This allows the save system to identify older save formats and safely migrate them to current data structures during the restore process.

Yes, the Unity save system supports multiple save slots and autosaves by managing structured JSON save files. The central SaveManager orchestrates reading and writing these individual slots to persist distinct player progress.

To serialize complex game state in Unity, the save system uses Newtonsoft.Json for the dictionary wrapper and JsonUtility for per-component structs. This combination captures and restores state entries aggregated from ISaveable MonoBehaviours.

Yes, Newtonsoft.Json is required as a dependency to serialize the dictionary wrapper for game state persistence. JsonUtility handles individual component structs, while Newtonsoft manages the overarching aggregated save data structure.

Yes, you can persist global Unity objects separately from scene-specific progress using scene-aware keys. The save system serializes per-scene progress independently while maintaining global state across scene loads.