purpur.yml Explained

purpur.yml is where Purpur exposes many of its extra behavior controls. That makes it powerful for custom SMPs, but risky for admins who only want "more FPS/TPS."

#What Makes It Different

Purpur builds on Paper and focuses on configurability. Some settings can replace small plugins or change entity behavior. Other settings exist for gameplay customization and may have little to do with performance.

| Setting type | Admin mindset | | --- | --- | | Gameplay behavior | Announce and document | | Entity behavior | Test farms, mobs, and combat | | Quality of life | Compare against plugin alternatives | | Performance-related | Profile before and after |

#Do Not Treat Every Toggle as Optimization

If a setting changes how a mob behaves, how a block works, or how a player interacts with the world, it is a gameplay decision. It may improve performance, but it can also surprise players.

Before editing, ask:

1. What problem am I solving?
2. Which profile or report points here?
3. Which players or farms are affected?
4. How do I test the side effect?
5. What is the rollback value?

#Migration Notes

When moving from Paper to Purpur:

1. Back up worlds and configs.
2. Confirm plugin compatibility.
3. Start once to generate configs.
4. Compare behavior in a staging copy.
5. Document Purpur-specific changes separately.

Do not migrate and tune at the same time. First prove the server boots and behaves normally, then optimize.

#Good Documentation

Use admin notes like:

File: purpur.yml
Setting:
Reason:
Expected benefit:
Gameplay risk:
Test result:
Rollback:

Continue with the Purpur optimization guide for workflow and the Paper optimization guide for the foundation.