Direct answer

Update plugins while the server is stopped, or stage replacements for the next full restart. Save a tested backup first, and avoid live JAR replacement or /reload.

Recommended procedure

  1. Record the current Paper and Minecraft versions, plugin name/version, configuration and associated data. Read the plugin’s changelog for breaking changes and migration instructions.
  2. Back up plugins/, relevant databases, configuration and worlds. Keep a copy of the exact prior JAR so rollback can restore matching code and data.
  3. Review required and optional dependency versions. Coordinate linked plugins or APIs before replacing a dependent JAR.
  4. For Paper’s documented plugin update workflow, place the new JAR in plugins/update/; Paper applies it on restart. Alternatively stop the server and replace the correct plugin JAR manually. Do not leave two versions installed.
  5. Restart once, review logs/latest.log for load errors or config migrations, then test permissions, commands, database integrations and the plugin’s core behavior.

Why this matters

Changes to data schemas or configuration formats may make a simple JAR rollback insufficient. Isolated tests and full backups prevent accidental data loss when reverting an update.

How to verify the result

  • Check /plugins on Paper to confirm the plugin is enabled, then test a feature as a non-OP player.
  • Verify database writes, scheduled tasks and cross-plugin integration where applicable.
  • If problems arise, stop the server and follow the author’s rollback instructions; restore matching files and database backup if formats changed.

Version and compatibility notes

Important

The plugins/update/ workflow is documented for Paper; proxy servers and other platforms have different update procedures. Do not use Bukkit/Paper instructions unchanged for Velocity.

Official references

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000