Moving to ReplayCoreLoader
1. Stop the server. Back up the current ReplayCore JAR and the whole plugins/ReplayCore/ folder.
2. Move the old ReplayCore JAR, and any pending ReplayCore update JAR, out of plugins/.
3. Keep plugins/ReplayCore/ as it is. Add ReplayCoreLoader.jar from Downloads and start the server.
If the console reports a duplicate ReplayCore plugin, stop the server and move the extra JAR out of plugins/.
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 supported 1.13+ versions through Minecraft 26.2, official PacketEvents 2.13.0+ must already be in the server plugins folder. Servers on 26.3 need 2.14.0+. Install it before you swap the ReplayCore JAR. Paper and Spigot 1.8.8–1.12.2 do not need PacketEvents. Download PacketEvents from Modrinth (https://modrinth.com/plugin/packetevents) or GitHub releases (https://github.com/retrooper/packetevents/releases).
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 supported 1.13+ servers through Minecraft 26.2, confirm official PacketEvents 2.13.0+ is in plugins/. Servers on 26.3 need 2.14.0+. Paper and Spigot 1.8.8–1.12.2 do not need PacketEvents.
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.