Previously it was not guaranteed to be safe to just quit the app with Ctrl C as it might be possible to time it to kill the app while it was attempting to write out the config or playerlist files (resulting in corruption), but there was also no clean way to shutdown the app.
Such an occurrence of corruption should be extremely unlikely, but probably still possible. A discord thread reported their playerlist and settings files being corrupted. I'm not 100% sure if it was because of the reason mentioned above (as I would have expected at most one of these files to be corrupted), but it's still a good indication we should be more careful about this.
I've just made a small change which uses the atomic-write-file crate to guarantee the files are either successfully written out in their entirety or not overwritten at all, so they should never be able to end up in an inconsistent state.
Previously it was not guaranteed to be safe to just quit the app with
Ctrl Cas it might be possible to time it to kill the app while it was attempting to write out the config or playerlist files (resulting in corruption), but there was also no clean way to shutdown the app.Such an occurrence of corruption should be extremely unlikely, but probably still possible. A discord thread reported their playerlist and settings files being corrupted. I'm not 100% sure if it was because of the reason mentioned above (as I would have expected at most one of these files to be corrupted), but it's still a good indication we should be more careful about this.
I've just made a small change which uses the atomic-write-file crate to guarantee the files are either successfully written out in their entirety or not overwritten at all, so they should never be able to end up in an inconsistent state.