How upgrades work
ReplayCore is delivered as a single JAR, so upgrading is a file swap: replace the ReplayCore JAR in plugins/ with the new version and restart. Preserve the entire plugins/ReplayCore/ data folder, including config.yml and ReplayCore's private per-install state.
On Paper, Purpur and Folia, official PacketEvents 2.13.0+ must already be in the server plugins folder or recording stays idle after the restart. If you are upgrading from a ReplayCore release that bundled PacketEvents, install the official plugin from Modrinth (https://modrinth.com/plugin/packetevents) or GitHub releases (https://github.com/retrooper/packetevents/releases) before you swap the ReplayCore JAR. Spigot 1.8.8 does not need this step.
Recommended upgrade steps
1. Read the changelog for the target version to check for any configuration or behaviour changes.
2. Back up the entire plugins/ReplayCore/ directory, including config.yml, the private identity and configuration credential, the registered binding, and the last-known-good managed configuration.
3. On Paper, Purpur and Folia, confirm official PacketEvents 2.13.0+ is in plugins/. Install it first if this server does not already have it.
4. Replace the ReplayCore JAR with the new version and restart the server during a low-traffic window.
5. Confirm the startup log shows the expected version and that recording resumes.
Existing replay data is not affected by an upgrade; replays recorded on an earlier version remain playable.
Rolling back
If an upgrade causes a problem, restore that same server's backed-up plugins/ReplayCore/ directory and swap the ReplayCore JAR back to the previous version, then restart. If recording does not resume, confirm the licence key, server name and private state are intact; never restore another live server's identity files.