Direct answer

Leaf is Paper-derived and aims to support the Paper plugin ecosystem, but optional performance settings can change entity behavior and must be evaluated for your own server.

Recommended procedure

  1. Create an offline Paper backup covering all dimensions, player files, plugin databases and configs.
  2. Choose a Leaf build for the same Minecraft version, check its Java requirement and compare plugin compatibility.
  3. Start a staged copy with the Leaf JAR and mostly generated defaults, then review any new Leaf-specific configuration.

What to change

  1. Test joins, permissions, claims, farms, NPC visibility, inventories, world saves and server shutdown.
  2. Only enable async optimizations one by one after gathering baseline measurements. Preserve the old Paper JAR and unchanged backup.

How to verify the result

Compare a representative performance test and ensure every critical plugin works; if data is affected, restore the offline Paper backup rather than downgrading the upgraded world in place.

Version and compatibility notes

Paper plugin compatibility does not guarantee identical gameplay under each Leaf optimization. Avoid transferring old 1.21.1 sample values to a modern Leaf config without checking that branch.

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