You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of the config.json contains a lot of duplicate information from default-config.json, and because of that, it does not update certain information, such as titles and tooltips, when the default config is updated. It also does not support multiple profiles. I suggest that the format of the config file be completely changed so that it only contains information as to what value each config option is set to. Information such as the type each option is, its settings, the title, and tooltip, would instead only be read from the default config file.
The new format for the config would be an array of profile objects, each containing key-value pairs for all options in the mod config, like so:
@GlobalSettings is the Global Settings described in my other issue. The “UseGlobalSettings” option determines if a profile will use the Global Settings or its own, while the other options are the mod config options defined in the default config. The prefix is simply to make it unlikely that an actual profile of the same name does not already exist. If a legacy config file is detected, it is parsed and then its settings copied over to the Global Settings.
On Xbox profiles are ignored and only the Global Settings will appear.
The text was updated successfully, but these errors were encountered:
The current implementation of the config.json contains a lot of duplicate information from default-config.json, and because of that, it does not update certain information, such as titles and tooltips, when the default config is updated. It also does not support multiple profiles. I suggest that the format of the config file be completely changed so that it only contains information as to what value each config option is set to. Information such as the type each option is, its settings, the title, and tooltip, would instead only be read from the default config file.
The new format for the config would be an array of profile objects, each containing key-value pairs for all options in the mod config, like so:
@GlobalSettings
is the Global Settings described in my other issue. The “UseGlobalSettings” option determines if a profile will use the Global Settings or its own, while the other options are the mod config options defined in the default config. The prefix is simply to make it unlikely that an actual profile of the same name does not already exist. If a legacy config file is detected, it is parsed and then its settings copied over to the Global Settings.On Xbox profiles are ignored and only the Global Settings will appear.
The text was updated successfully, but these errors were encountered: