Direct answer

Purpur builds on the Paper ecosystem and provides extra optional gameplay configuration. Most Paper workflows transfer, but forks can differ in defaults and plugin assumptions.

Recommended procedure

  1. Inventory your Minecraft version, Paper build, Java runtime, startup command and all plugins.
  2. Make and test a complete backup of worlds and plugins before changing server software.
  3. Find a Purpur build targeting the same Minecraft version to minimize migration variables.

What to change

  1. Stop Paper and replace its JAR with the compatible Purpur JAR, updating only the startup filename if necessary.
  2. Start Purpur, inspect generated purpur.yml, and leave nonessential changes at their generated defaults initially.
  3. Test protection, permissions, worlds, farms and any packet-sensitive plugins with a restricted test group.

How to verify the result

Confirm /version reports Purpur; compare player joins, errors and MSPT against the original Paper baseline and retain backups for rollback.

Version and compatibility notes

Do not treat Purpur as a performance upgrade guaranteed to boost TPS. Avoid simultaneous Minecraft version upgrades and software switches when debugging. Folia’s thread model is a different migration problem.

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