I’d like to know the reason behind making the mod settings from config.json only editable at the start of the game?

I’m using it as a mod data cache now, so it’s all good, but I’d like an attribute for each setting that says when the setting is editable by the player:

1. Not at all (e.g. persistent state container — hidden in UI)
2. New game (current solution)
3. Load game
4. Runtime

Higher number implies all above, I.e. if a setting is editable at runtime, it can also be changed when setting up a new game.

In the first canary build the settings were also editable when loading a game.
But by just clicking the edit button there, all settings were set to default again, without the mod knowing the current values.
Dev's decided not to fix but remove the option of editing at load time.

I agree with an attribute for player editable, I am also planning to use it as a mod data cache.

Thanks.

Implementation could ofc also be realized by attribute flags, in some combination, doesn’t have to be an int/enum.