Direct answer

Treat a Purpur update like a Paper update plus extra Purpur-specific configuration review; never assume old plugins or custom world behavior will work unchanged.

Recommended procedure

  1. Record current Minecraft/Purpur build, Java version, plugins and purpur.yml customizations.
  2. Back up all worlds, plugin data and configuration and verify the archive can be restored.
  3. Read the Purpur/Paper changes between your current and target builds, including Java and plugin compatibility.

What to change

  1. Download the desired Purpur version from its official site and stop the running server.
  2. Replace the JAR or update the start script with its exact name, then boot and monitor logs/latest.log.
  3. Test important plugins, permissions, trading/redstone/farms and player joins before reopening fully.

How to verify the result

Check /version, plugin health and normal player activity. If a problem appears, restore the full matched backup rather than only swapping the JAR across incompatible world versions.

Version and compatibility notes

Avoid downgrading a world after opening it in a newer Minecraft release. For Paper 26.1+ Java 25 is required; do not assume the requirement is identical for all old Purpur branches.

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