Update the server JAR
Replace releases with clean shutdown, version checks, and a usable backup.
Before updating
Check the official customer release notes, Minecraft version, Java, and plugin support. Test the new JAR on staging. Keep the previous JAR and a matching world/config backup. Review zstd compatibility before planning a return to Paper.
/version checks published cloud releases for the running Minecraft version. Custom or unpublished JARs may be unrecognized. Failed network checks do not replace the server; this is not automatic updating.
Replace the file
- Arrange a maintenance window and stop ongoing world-changing activity.
- Enter
stopand wait until Java exits completely. - Back up worlds, configuration, plugin data, and related databases consistently.
- Move the old JAR out of the startup filename and replace it with the official new file. Match the launcher filename.
- Keep worlds, configuration, license files, and private saved bridge credentials.
- Start again. Check startup errors, plugins, connections,
nusa status, and core gameplay.
Missing Nusa keys take defaults without rewriting older files. Add settings you want to control explicitly after reviewing the release. YAML changes need a full restart.
Roll back if needed
Stop the new server first. Determine whether the old software can read data already written. If world or plugin formats changed, restore the complete pre-update backup rather than mixing files from different times.
Minecraft downgrades can lose or damage data. Replacing a JAR alone is not a safe downgrade procedure. Test a restore separately before reopening player access.