Falcury wrote: ↑May 25th, 2019, 12:09 amI think that the reason I liked it turned off by default, is that it protects against unexpected behavior if you accidentally fiddle with the settings (which is maybe rather easy to do in the menu interface).
If I understand your parenthesized phrase correctly, you're saying perhaps CFG modification needs similar protection. Maybe menu entries that are set to non-default values could have a different color, to stand out from the rest. It's what I'm doing on the 'EXE screens' of my level editors, with blue text.
Falcury wrote: ↑May 25th, 2019, 12:09 amMaybe writing settings to the ini file directly is something we should add.
I don't think I understand why two separate options (INI and CFG) exist; why the menu doesn't modify the INI file. But I'm guessing, based on your comment, it's simply complicated to parse the INI file, which I can imagine. On top of that, I think there's a third config option for mods? I think only you (Falcury), and perhaps David, get how that one works; I don't see many people using that...
Either way, as I wrote, I think use_custom_options is far too easy to overlook when you're trying to make changes further down the INI file, and then don't get why things aren't being impacted by changes you make. Protection against accidental fiddling is well-intended, but maybe unnecessary. After all, the user consciously decided to open, modify and save the INI file...