A server update should have a reason, a check plan and a way to recover if the result is unsuitable. “Newer” alone does not tell you whether your current combination of plugins and configuration is ready.
Before changing anything
Record the current software and plugin versions. Read the relevant release notes and identify compatibility requirements. Keep a backup of the world and required configuration, and verify that you can retrieve it. Plan a maintenance window if players will be affected.
During the update
Paper's official instructions advise against replacing the running server JAR. Stop the server before replacing it and follow the documented procedure for your hosting environment. Use official project distribution channels and inspect startup output after starting again.
After startup
Check the features your players actually use. A process that starts successfully may still have an unavailable plugin or changed behaviour. Test a small agreed checklist and retain the result with the version information.
If something fails
Stop and investigate before making a chain of unrelated changes. A return path may require restoring the matching world and configuration, not merely putting an older JAR back. Avoid assuming that a world changed by a newer version is safe to open in an older version.
This is general administration guidance. Use the controls and procedures supported by your host; do not change a server you are not authorised to manage.
Technical references
https://docs.papermc.io/paper/updating/
Related reading
A backup is more useful after a restore rehearsal
https://panel.zeismoplay.com/community/topic/27
A maintenance notice players can actually use
https://panel.zeismoplay.com/community/topic/12
0 thanks