Minecraft anticheat guide
Folia Anticheat Support for Threaded Minecraft Servers
Why Folia support requires entity, region, global, and async ownership discipline, and how FairPlay positions Folia-aware anticheat internals.
Folia is not just a checkbox
Threaded Minecraft servers require careful ownership boundaries. Entity/player mutation belongs to the entity scheduler, block and chunk operations belong to region context, server-global actions belong to global context, and file or network work belongs async. A plugin that ignores this can load but still be unsafe.
Folia uses region and entity schedulers for server work. Before installing an anticheat, check the plugin requirements and test your exact Folia and dependency versions on a staging server.
What server owners should test
Test your exact Folia build, PacketEvents version, external hooks, combat checks, scaffold checks, punishment commands, teleport/setback paths, and dashboard/admin workflows. Folia compatibility is a runtime behavior property, not only a plugin.yml field.
Folia server owners often search for Folia anticheat, Paper anticheat, Spigot anticheat, PacketEvents anticheat, and Minecraft anti-cheat plugin. FairPlay pages should answer those topics directly.
FAQ
What should I check before using FairPlay on Folia?
Check the plugin requirements, PacketEvents setup, and your exact Folia build, then exercise the server workflows you rely on in staging.
Can a packet anticheat run on Folia?
Yes, if detection is separated from Bukkit world/entity mutation and enforcement is scheduled on the correct entity or region owner.