Skip to content

Technical guide

EssentialsX alternative for Folia servers

EssentialsLite as an essentials suite for Folia, what its Folia claim does and does not prove, and a checklist before you swap it in.

Products and contents

If you run EssentialsX on Folia and want a replacement, the first question is whether the command suite touches world state from the thread that owns it. Folia splits the world into regions, each with its own thread. A command that teleports a player or reads a chunk from the wrong region can fail in ways that a single-threaded server never shows.

EssentialsLite is an essentials suite for Bukkit-family servers. Its store listing advertises Folia support, and its descriptor declares it too. A declaration is not a test. Verify it on your own server before you move production players.

What EssentialsLite includes

The repository describes the plugin as covering:

  • Around one hundred commands and eighty-five permissions.
  • Teleports, homes, kits and warps.
  • Menus, Redis support and RTP (random teleport) zones.
  • Command, permission, menu, Redis and RTP-zone configuration files.

The repository lists Bukkit and Spigot as the platforms. It states no Minecraft version range. Paper and Folia are not listed as tested platforms, so treat the Folia claim as unproven until you test it.

What the Folia claim does not prove

  • It does not show that every command schedules work on the correct region.
  • It does not show that teleports across region borders are safe.
  • It does not show that RTP zones load chunks correctly on Folia.
  • It does not show that reload and shutdown paths are clean.

For the scheduling rules, read the Folia compatibility guide.

Checklist before you swap

  1. Back up the plugin folder and your data files.
  2. Run EssentialsLite on a Folia test server with a copy of your world.
  3. Test teleports across region borders. Walk a player across a boundary and teleport between distant points.
  4. Test RTP. Run it several times in an area that spans regions. Check for stalls and for players landing in unloaded or unexpected spots.
  5. Test homes, warps and kits with a normal player account and a staff account.
  6. List the commands and permission nodes your staff use. Confirm each one exists in the new permission file.
  7. If you use Redis, confirm the Redis config and check behaviour when Redis is unreachable.
  8. Reload the plugin and restart the server. Watch the console for errors on both steps.

Migration notes

  • Map your existing kits, homes and warps into the new files by hand. Do not assume the format carries over.
  • Compare command aliases. A player who types /home should reach the same command.
  • Keep the old plugin jar until the new setup has run for a full cycle with real players.

When to keep EssentialsX

Keep EssentialsX if you depend on a feature this guide does not cover, or if you have not tested the Folia behaviour above. A swap that breaks teleports or kits costs more than the plugin change saves.

For related checks, see the EssentialsLite product page.

Frequently asked questions

Is EssentialsLite verified on Folia?

No. Its listing advertises Folia support and its descriptor declares it. Verify it on your own server before you move production players.

Does a Folia declaration prove the commands are safe?

No. A declaration is not a test. Check the commands that touch world state on your build.

When should I keep EssentialsX?

Read the section on that topic before you switch. It describes the cases where the guide recommends keeping it.