New settings / Default changed

[Superd22]

Scenario :
User is using MCM with Mod1.
Mod1 contains two settings : S1 & S2.
By default, Mod1 sets S1 to 10 and S2 to true.
User changed S1 to 11 and S2 to false.

Mod1 updates,
Default S1 is now 20 because the dev tweaked the U.I
A new config S3 is now present.

1/ If the mod doesn't use StaticSaveConfig but SaveConfig instead, custom settings by the user will be lost.
2/ In any case, the user needs to be informed S3 is new and S1 was changed by the dev.

This would necessitate keeping track of the current values we have when MCM is run.
Which can be done (fairly) easily by creating a config array which MCM_API_SettingsPage could populate with setting Names/Values when it's done.

[andrewgu]

Not sure I fully understand the idea. You're saying that we should give the mod developer a way to send updated settings to the player through the config menu?

[Superd22]

Okay, more concrete example (brain fried with midterms i'm afraid) :

I have a mod displaying perks. in V1.0 as a developer i chose to display 8 perks per row because it was fitting design-wise.
In V1.1 I added a background to the perk row and changed the number to 7 because if fitted better.

MCM should allow me to display the facts that :
1/ There's a new option available (background on/off)
2/ Even IF the user already set the setting to 7 because they liked to see less perks, they probably should re-consider because the default value changed from 8 to 7, so if they really like less they might wanna go for 6 with that new version.

[andrewgu]

Pushing this to a 2.0 feature, at least until the state of the art on handling INI's advances a bit more. Going to leave this issue open though.