Direct answer

A Paper server may start on Folia while plugins quietly violate region thread ownership. The migration decision needs real plugin compatibility tests and a rollback plan, not just a JAR replacement.

Recommended procedure

  1. Stop Paper and make a restorable backup including worlds, plugin data and configuration.
  2. Audit each plugin for Folia support, especially tasks involving entities, inventories, teleports, NPCs and global timers.
  3. Clone the server, replace only the JAR in staging, verify Java compatibility and start Folia while collecting logs.

What to change

  1. Test distant independent areas and one crowded hotspot, plus joins, economy, homes, portals and shutdown.
  2. If a plugin causes ownership errors, update or remove it rather than forcing compatibility flags. Keep production on Paper until every critical function passes.

How to verify the result

Run a simulated production session, perform a clean stop and reload the saved world. If any essential workflow fails, restore the Paper backup and original JAR.

Version and compatibility notes

folia-supported: true is only a plugin declaration; PaperMC explicitly warns that it is not proof of thread-safe design. Folia also changes behavior of some commands and global assumptions.

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