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
I thought that when the plugin shuts down it saved the config, but it seems like this is a myth?
When I tried to reproduce this I could not.
I changed the config when the server was not running and loaded it: the loaded config had the values.
I changed the config while the server was running and restarted the server: the config file was not overwrriten and properly loaded the values set in it.
When I check the current code, the config is NOT saved on shutdown, and there are only three cases when it is saved:
when the config does not exist on startup, it is recreated from defaults (standard saveDefaultConfig)
when /ph config set <key> command is used
when /ph config set <key> <value> command is used.
Checking the code in 5.2.3 with JD (around the time of the original Issue), there is also no code forcing a save on shutdown.
So nothing seems to have changed since 3.x
crashdemons
changed the title
Implement 'dirty' check on config to prevent overwriting file changes on disable (or similar fix)
Report: modified config file being overwritten on server restart (not reproducible)
Feb 7, 2021
This would ease use and reduce issues like meiskam#16
The text was updated successfully, but these errors were encountered: