Direct answer

Because Folia changes both Paper internals and regional execution, treat an update as a plugin compatibility event as well as a Minecraft version change.

Recommended procedure

  1. Check the Folia download changelog and compare target Minecraft versions and Java requirements.
  2. Create a complete backup while the old server is stopped. Save the exact old Folia JAR and plugin versions.
  3. Update a staging copy first. Observe startup warnings and plugin scheduler/thread exceptions.

What to change

  1. Replace the staged JAR, start with the correct Java version and test player joins, teleportation, region-based operations and saves.
  2. Update Folia-compatible plugins only where supported. Keep a rollback copy; do not open an upgraded world in an older server without a known-good backup.

How to verify the result

After a clean restart, verify persisted player inventories and representative workloads. Roll back using the offline backup if data or plugin compatibility fails.

Version and compatibility notes

Folia builds can change disabled commands and scheduler behavior. Review the exact target build; generic Paper update advice does not certify Folia plugin compatibility.

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