DeerFolia

Use DeerFolia

Use DeerFolia as the server core in your startup command. It is not a plugin. Do not put its jar in plugins/. Do not load its configuration in a Paper or Purpur process.

You can operate DeerFolia without reading Java source code or Paperweight patch code. Check plugin compatibility before you migrate.

Choose a task

What you want to do	Start here
Install or switch cores for the first time	Installation and first start
Find configuration files and restart rules	Configuration overview
Change DeerFolia settings	DeerFolia configuration
Limit entities such as zombified piglins and villagers	Entity throttling
Review optimizations and their effects	Features and optimizations
Diagnose startup, plugin, farm, or sync problems	Troubleshooting

Back up before migration

Back up the following files before you switch server cores:

• every world directory;
• server.properties, eula.txt, and configuration directories;
• plugin data, databases, and scheduled jobs;
• the current server jar and startup scripts.

Start with a copy of the production server. Check plugin loading, player login, teleportation, chunk loading, and common machines. Move the core to production only after these checks pass.

Check whether DeerFolia fits

Folia can run separate player regions in parallel. This can help when players use separate areas. It may not help when players stay in one small area.

Many Paper plugins need explicit Folia support. Check the compatibility statement for each plugin before you migrate.

DeerFolia can change update timing for dense entity areas, villager POI checks, pathfinding, and AFK network synchronization. Use the default settings as a starting point. Test each change on a copy of the server.