-
Notifications
You must be signed in to change notification settings - Fork 3
Config Migration
Vanish++ automatically migrates your configuration when you update to a new version. You never need to delete and recreate your config files.
On startup, the plugin reads the config-version key in config.yml. If it is lower than the current version, a smart-merge migration runs:
- Your existing custom values are read and preserved
- New keys introduced in the new version are added with their defaults
- Removed or renamed keys are handled gracefully
- The
config-versionis updated to the new value
messages.yml is automatically migrated on every startup. The plugin compares your file against the built-in defaults and writes any missing keys back to disk with their default values. Your existing customizations are never overwritten.
This means:
- Upgrading to a new version never leaves a key undefined — new messages added in the update appear immediately with sensible defaults.
- You can safely edit any existing value; only missing keys are added.
- No manual diff or copy-paste required when updating.
scoreboards.yml and config.yml follow the same pattern — missing keys are filled from defaults and existing values are preserved.
After a migration, a report is shown in-chat to staff with vanishpp.see on their next login, listing what changed. The report can be permanently dismissed with /vack.
Although migration is designed to be safe, it is good practice to back up your plugins/Vanishpp/ folder before updating on production servers.