Upgrade CoreDSC

Before replacing the JAR

1. Stop Paper cleanly.
2. Back up plugins/CoreDSC/, including the SQLite database.
3. Read the release notes and migration notes.
4. Replace the JAR.
5. Start Paper and watch the configuration-migration output.

CoreDSC 2.5.2 uses schema version 4 in maintained YAML files. Missing defaults are added through a migration process that creates timestamped backups and writes files atomically.

Migration rules

• Unknown future schema versions are blocked rather than downgraded.
• Unknown keys are preserved and reported.
• A failed reload restores the previous active configuration and module set when possible.
• An old license.yml is no longer active configuration. A valid old bStats preference is imported into telemetry.yml; a previous opt-out is not re-enabled.

After the upgrade

Run:

/coredsc doctor
/coredsc status

Then test chat, linking and every enabled synchronization module. Keep the backup until the server has completed at least one clean restart.