-
-
Notifications
You must be signed in to change notification settings - Fork 27
Description
I want to overhaul the settings system.
First order of business is using a key-value system. TOML, JSON, XML, YAML, etc. This will future-proof any settings being added / removed and make different versions compatible with each-other without loosing any settings. As a nice bonus it will this make the settings human-readable.
The code will see a massive cleanup from this.
As mentioned above, by not overriding keys we don't use in the save file, we keep compatibility and settings for all versions after this change. It's also a lot less likely to get corrupted or break.
I'd also use this opportunity to fix any and all save and load issues we're having.
I'm fully willing to break settings from any previous version before this change. The cost is very minor for the end user (it takes less than a minute to redo one's settings). And we'll finally get rid of all the overly-complicated settings code.