Idea continued from; #61
You might also consider having the option to have two defaults in your info config, "gamedefault" "moddefault", and "default" just goes backwards compatible with "moddefault". That way authors can include the default from the game in there, and you can have a UI button to set game default or set mod default. UI buttons at the end of each field could help with that.
If default and mod match, then you can just remove the button for one of them or make it one larger button "reset".
If one is already at the default, fade out the relevant button, E.G. if I set mod default on one, mod default is greyed out. If I set game default, that button fades out and mod default comes back.
<config>
<var gamedefault="2" moddefault="8" name="{SolarPanel_HitPoints}" value="8">Solar Panel: Hit Points</var>
<var gamedefault="0" moddefault="0" name="{SolarPanel_SystemPoints}" value="0">Solar Panel: System Points</var>
<var gamedefault="false" moddefault="true" name="{SolarPanel_DisableBuildTest}" value="true">Solar Panel: Disable Build Test</var>
<var gamedefault="10" moddefault="10" name="{SolarPanel_HighPowerCapacity}" value="1000">Solar Panel: High Power Capacity</var>
<var gamedefault="5.0" moddefault="10.0" name="{SolarPanel_EnergyPerSecond}" value="20.0">Solar Panel: Energy per Second</var>
</config>
Idea continued from; #61
You might also consider having the option to have two defaults in your info config, "gamedefault" "moddefault", and "default" just goes backwards compatible with "moddefault". That way authors can include the default from the game in there, and you can have a UI button to set game default or set mod default. UI buttons at the end of each field could help with that.
If default and mod match, then you can just remove the button for one of them or make it one larger button "reset".
If one is already at the default, fade out the relevant button, E.G. if I set mod default on one, mod default is greyed out. If I set game default, that button fades out and mod default comes back.