Nearly every Voyagers of Nera configuration ticket comes down to the same thing. The server writes its own config files, and it does so at moments that overwrite your edits.
The rule
The server reads its settings at startup and writes them back at shutdown. So:
- Stop the server.
- Edit the file.
- Start the server.
Editing while the server is running always loses your work, with no error.
The first boot creates the files
On a brand new server there are no config files until the server has run once. Uploading a prepared file before the first start means it is replaced by defaults.
The correct order on a new server is:
- Start the server once and let it fully load.
- Stop it.
- Edit the files in
BoatGame/Saved/PersistedData/CustomConfig/. - Start it again.
Which file holds what
CustomHostUserSettings.ini, the server name, password, player count and autosave timer.CustomGameUserSettings.ini, the gameplay multipliers and toggles.
A setting in the wrong file is ignored, which looks exactly like a setting being reverted.
Check the change took
The server name is the fastest test. If it is back to the default, the file was overwritten. If the name changed but a gameplay value did not, the value is in the wrong file or spelled differently in your version.
Back up before you experiment
- Stop the server so the world is fully written.
- In Files, download the
CustomConfigfolder and the save folder.
Those two together restore a working server exactly as it was.
The server will not start after an edit
Read the panel console. A malformed line is reported there. Restore your backup, or delete the config file and let the server write a fresh default one on the next start, then edit it properly with the server stopped.
Losing progress on a restart
The world is written on the autosave timer and on a clean shutdown. Use the panel's Stop and wait for the server to report it is offline. If you lose progress regularly, shorten the autosave timer in CustomHostUserSettings.ini.





