feature/save_and_loaaaaaad #32

Implemented and reworked the Save structure based on our first use cases and some pointers from the chat.

General:

Split the save system into two parts: Settings and User Data.
- Settings are for local stuff like window size, sound settings and so on.
- User Data is for game saves that will later be synced via the Steam Cloud (already set up via the folder structure).
Added Versioning to the save data that isn't hooked up for now but will be helpful when migrating in the future
simplified the save structure to a simply "id - string payload" matching to make it easier to maintain and debug
found a way to use Guids for saving: I'm adding a Metadata entry to the top node of each saveable prefab scene and add it to a group called "Saveable". Then in the containing scene, I run a tool node that iterates over all instances in this group and auto-generates the ID where necessary. Needs to be updated manually, but works fine so far.

Use cases implemented and synced via save (triggers on scene transition / restart):

Known issues:

The first run (when there is no save file yet) sometimes still triggers some ominous error messages. Could not repro last time I checked, but I cannot say for sure if it's gone for good.
There is still some cleaning up (todos) to do in the InteractionArea script, but that's something for another PR
Also there are still things we need to sync like player position, last scene loaded, dialogues played etc, but these will be added in the next batch
Also there are some known bugs with the current state of the dialogue system as a whole (looping, random triggers etc.) which will also be addressed in a different PR

7.4 KiB

12 KiB

8.5 KiB

Nur eine kleinigkeit

     [Export] private int _id = -1; // TODO: remove
     private Material[] _backupMaterials;
     private int _interactionCounter;