Separating User Settings out of vegastrike.config
Posted: Wed Jan 09, 2008 4:00 pm
The problem:
Currently, when the user runs setup.exe, customizations such screen resolution and sound preferences are stored into vegastrike.config.
But mod-related settings are also stored into vegastrike.config.
This creates a problem with svn updates: Every time mod developers change some mod-related parameters into vegastrike.config, users get a conflicted file in svn. To get the mod-related settings they have to delete the file and then svn-update, which wipes out their personal settings, forcing them to run setup.exe again.
Proposed Solution:
Have a "user_settings.config" file, where user settings are stored separately from mod-related settings.
EDIT:
Possible snafu: Backward compatibility...
One way to solve it could be to put one more parameter in vegastrike.config having the path to the new user_settings.config file.
If the parameter isn't there, it means that the user settings are still contained in vegastrike.config.
Currently, when the user runs setup.exe, customizations such screen resolution and sound preferences are stored into vegastrike.config.
But mod-related settings are also stored into vegastrike.config.
This creates a problem with svn updates: Every time mod developers change some mod-related parameters into vegastrike.config, users get a conflicted file in svn. To get the mod-related settings they have to delete the file and then svn-update, which wipes out their personal settings, forcing them to run setup.exe again.
Proposed Solution:
Have a "user_settings.config" file, where user settings are stored separately from mod-related settings.
EDIT:
Possible snafu: Backward compatibility...
One way to solve it could be to put one more parameter in vegastrike.config having the path to the new user_settings.config file.
If the parameter isn't there, it means that the user settings are still contained in vegastrike.config.