ForWhomTheFlowersWeep
Refugee
Currently, in order for a mod to add a new game option to the game, it appears that mod must provide custom code in addition to XML-based modifications. This request is to allow for a mod to add a game option purely through XML-based modification.
I think making this operation more accessible in this way would result in more mods which are easier to use and adjust to various play styles game-to-game, as the leap from XML-based modding to modding with custom code is a significant one, and making that leap also tends to run afoul of EAC.
From a player perspective, the new/continue screen would show additional options provided by mods. In my opinion the simplest way to keep the addition of such options clean and easy to understand would be to add a "tab" specifically for mod-provided settings (if any are defined) alongside the "general", "basic", and "advanced" tabs.
From a modder perspective, they would need to "define" the option in some way (title, values, etc) and have a way to access its value for the current save within other XML files. Defining the option should result in it showing in the new/continue game UI, and being saved/loaded by the game. Part of the modder-provided definition should be a "default" value to use if a save is loaded which was created without the option present.
As an example, say I have a mod which increases skill points awarded per level. On "new game" creation, I would be presented with a game option to set that to "1", "2", etc. If I select "2", on each level up I would receive two skill points. Having this be a game option rather than hard-coded into the mod would allow me to have different settings for a quicker game with friends (where we might accelerate progression), or a longer solo game with the default 1-per-level, without having to add/remove the mod when switching between those games.
I think making this operation more accessible in this way would result in more mods which are easier to use and adjust to various play styles game-to-game, as the leap from XML-based modding to modding with custom code is a significant one, and making that leap also tends to run afoul of EAC.
From a player perspective, the new/continue screen would show additional options provided by mods. In my opinion the simplest way to keep the addition of such options clean and easy to understand would be to add a "tab" specifically for mod-provided settings (if any are defined) alongside the "general", "basic", and "advanced" tabs.
From a modder perspective, they would need to "define" the option in some way (title, values, etc) and have a way to access its value for the current save within other XML files. Defining the option should result in it showing in the new/continue game UI, and being saved/loaded by the game. Part of the modder-provided definition should be a "default" value to use if a save is loaded which was created without the option present.
As an example, say I have a mod which increases skill points awarded per level. On "new game" creation, I would be presented with a game option to set that to "1", "2", etc. If I select "2", on each level up I would receive two skill points. Having this be a game option rather than hard-coded into the mod would allow me to have different settings for a quicker game with friends (where we might accelerate progression), or a longer solo game with the default 1-per-level, without having to add/remove the mod when switching between those games.