user config (name, screen resolution) and server config (rooms, ports, pins, last room, last ship) are both located in the user.config file, but we want to be able to update the server config without messing with the user config (e.g. resetting screen res each update).
Options
currently getdown does not track user.config - a tracked server.config (or equivalent) could be used for the server options while leaving user options untouched. This adds moderate complexity and would require some code changes.
remove all server config - but this would reduce UX by requiring users to do manual config.
re-track user.config - the simplest option, but reduces UX by requiring users to reset some settings each update
Problem
user config (name, screen resolution) and server config (rooms, ports, pins, last room, last ship) are both located in the user.config file, but we want to be able to update the server config without messing with the user config (e.g. resetting screen res each update).
Options