Suggestion: Generic GameState that saves into JSON (or similar)

[Maaack]

Currently, the GameLevelLog tracks progress in the config file. This does not follow convention on where that data would typically be stored, as it mixes application configuration settings with game state.

Instead, we could try creating a generic GameState (or even more generic AppState) that stores a dictionary of data and manages the saving/loading behind the scenes. There's a lot of documentation available on how to save and load game state to and from files.

https://docs.godotengine.org/en/stable/tutorials/io/saving_games.html

Eventually, it could have multiple levels, like UserGameState, PCGameState, WorldGameState depending on the level of persistence desired.

GameLevelLog, GameLog, AppLog could then be updated to read from the GameState instead of Config.

[Maaack]

I think adding this could really help avoid devs (specifically, me) from getting into a bad practice of saving game state data in the config file instead, just because it is available.

[Maaack]

I have a working system from my last game jam that saves state into a Resource object, and then saves with ResourceSaver. It was simple and worked great for the jam, and may be better than trying to use JSON. There is a vulnerability that the resource files can hold executable code, but I'm not sure how that is a concern here. ( https://forum.godotengine.org/t/how-to-load-and-save-things-with-godot-a-complete-tutorial-about-serialization/44515#but-i-heard-from-someone-that-resources-are-insecure-13 )

I began porting it over, but stalled when trying to generalize it for the template. I'll try again in the near future.