EssentialsX Explained: the Backbone of Every Minecraft Server
EssentialsX gives a Paper, Spigot or Purpur server the commands players simply expect to be there: /home, /tpa, /warp, /kit, /spawn, private messages through /msg and a broad set of moderation commands. The plugin ships as separate modules (EssentialsX, EssentialsXChat, EssentialsXSpawn, EssentialsXProtect and a few smaller ones), of which you realistically need only one or two. Without a permissions plugin such as LuckPerms, EssentialsX does almost nothing for ordinary players, because nearly every command sits behind its own permission node.
What does EssentialsX actually do?
Vanilla Minecraft has no /home and no /tpa. They only exist because a plugin adds them, and on most Dutch survival and SMP servers that plugin is EssentialsX. It runs entirely server-side on the Bukkit API, so players install nothing: they connect with a plain Minecraft client and can type /sethome straight away.
EssentialsX is the actively maintained continuation of the old Essentials project. Alongside player commands you get moderation tools such as /kick, /ban, /mute, /invsee, /vanish and /socialspy. Each player gets a userdata file holding their homes, balance and last known location, so you gain a slice of player administration too.
In our overview of the most important Minecraft plugins, EssentialsX sits at the top for good reason: together with LuckPerms it is the layer almost every other plugin leans on.
Which modules do you really need?
The EssentialsX download is a zip containing several jar files. You do not have to drop them all into your plugins folder, and you should not: every module you do not use is one more source of conflicts.
| Module | What it adds | When to install it |
|---|---|---|
| EssentialsX (core) | Homes, warps, teleport requests, kits, private messages, moderation and the built-in economy | Always, this is the required base |
| EssentialsXChat | Chat formatting with prefix and suffix, local chat within a radius, shouting to the whole server | Only if you are not already running another chat plugin |
| EssentialsXSpawn | A spawn point per group, respawn location and the spawn new players arrive at | If another plugin is not already handling spawn |
| EssentialsXProtect | Basic world protection: switching off creeper damage, fire spread and lava flow | Rarely, WorldGuard and the Paper config usually cover this |
| EssentialsXAntiBuild | Blocking building and breaking by permission | Only on servers without WorldGuard or GriefPrevention |
| EssentialsXGeoIP | Country code alongside a player's IP address | Only if your team uses that for moderation |
The rule of thumb: start with the core alone and add a module only when you find something missing. Working the other way round is harder, because when something breaks you have no idea which module caused it.
How do you install EssentialsX on a Paper server?
- Download the EssentialsX release that matches your server version. If you run Minecraft 1.21 "Tricky Trials" or the newer 26.2 "Chaos Cubed", grab the build that names that version.
- Unpack the zip and put
EssentialsX.jarin thepluginsfolder. On the Pterodactyl panel that comes with Minecraft hosting at MC-Node you can drag the file straight into the file manager. - Add LuckPerms in the same step, plus Vault if you want to use an economy or shops.
- Restart the server fully. Do not use
/reload: it reloads plugins halfway and produces errors that are painful to trace. - Open
plugins/Essentials/config.ymland work through at least the teleport settings, the economy anddisabled-commands. - Test with a second account:
/sethome,/home,/tpaand/msg. Do not test as an operator only, because operators have everything by default.
If you are setting up a server completely from scratch, our guide to making a Minecraft server is the logical first step; EssentialsX comes after that.
Why does EssentialsX do nothing without permissions?
This is the classic trap. You install EssentialsX, type /home yourself and everything works. Moments later your first player reports that they are not allowed to. That is because you are an operator with every permission automatically, while an ordinary player gets almost none by default.
So you need a permissions plugin, and in 2026 that is nearly always LuckPerms. In it you create groups (say player, donor, staff) and hand each group nodes such as essentials.home, essentials.sethome, essentials.tpa, essentials.spawn and essentials.msg. Warps are granted one by one with essentials.warps.<name>, so a donor warp stays usable by donors only.
What you must never do is attach essentials.* to a player group. That wildcard also covers /gamemode, /give, /tp, /god and /ban. It turns every player into a half-administrator, and you only find out when someone hands themselves a stack of diamonds. Always grant individual nodes per group and use inheritance: the staff group inherits the player group and gets the moderation commands on top.
How do you set teleport cooldown, warmup and homes per rank?
On a survival server, teleporting is the single biggest balancing lever EssentialsX hands you. Two settings in config.yml do most of the work. teleport-delay is the warmup: the number of seconds a player has to stand still before the teleport fires, which stops anyone escaping mid-fight. teleport-cooldown is the wait before someone may teleport again. teleport-invulnerability decides how long a player stays invulnerable after arriving.
The number of homes is controlled by sethome-multiple in the config, combined with the permission essentials.sethome.multiple.<group>. The split below is not gospel, but it is a starting point that works well on plenty of survival servers:
| Rank | Homes | Warmup (teleport-delay) | Cooldown |
|---|---|---|---|
| Player | 1 | 5 seconds | 30 seconds |
| Donor | 3 | 3 seconds | 15 seconds |
| VIP | 5 | 3 seconds | 10 seconds |
| Staff | 10 | 0 seconds | 0 seconds |
For your team, do not set those waits to zero in the config; grant the permissions essentials.teleport.timer.bypass and essentials.teleport.cooldown.bypass instead. That keeps the config identical for everyone and puts the difference in one place: your permission groups.
How does the economy work through Vault?
EssentialsX has a built-in economy with /balance, /pay, /baltop and /eco give. On its own that is a balance and nothing more. It gets interesting with Vault, the glue layer that lets other plugins reach that balance: a shop plugin never talks to EssentialsX directly, it asks Vault how much a player has and deducts an amount.
The order is simple: Vault in the plugins folder, EssentialsX next to it, then your shop or jobs plugin. At startup the console confirms that Vault has found an economy provider; if it finds none, no shop will work.
The biggest mistake is running two economy plugins at once. Vault then picks one, and players see one balance in one place and a different balance in another. If you use a different economy plugin, switch off the EssentialsX economy commands through disabled-commands. If you run a network behind a proxy, remember that balances live in per-server userdata files by default; in that case you want an economy that synchronises through a database.
Which conflicts do you get with other plugins?
EssentialsX touches so many commands that it quickly becomes the plugin that gets blamed. Conflicts come in four flavours.
- Chat. EssentialsXChat next to a second chat plugin gives you duplicated messages or a format where prefixes appear twice. Run one of them. If you do keep EssentialsXChat, it pulls prefix and suffix out of LuckPerms through Vault, so Vault has to be present as well.
- Teleporting. If a second plugin also registers
/homeor/tpa, load order decides who wins the command. Fix it withdisabled-commandsin the Essentials config, or by using the full/essentials:homein your aliases. - Spawn and worlds. EssentialsXSpawn and a world management plugin both fight over
/spawnand over your respawn point. Again, pick one. - Anticheat.
/fly,/godand/speedlook exactly like cheating to an anticheat. Set the exemptions properly, or your anticheat will kick your own staff.
One thing EssentialsX rarely causes is lag. If your TPS, the server's tick rate, starts dropping, look at chunk loading and entities first. Our guide to optimising your Minecraft server goes into that in more depth.
When you are better off skipping EssentialsX
If you run a modpack such as All the Mods 10 on NeoForge, your server loads no Bukkit plugins at all and EssentialsX is simply not an option; teleporting is handled by the mods in the pack. On a minigame or hub network EssentialsX is often redundant, because the minigame plugin itself decides where players may go. And on a small vanilla SMP, /home changes the game considerably: if you want people building roads and Nether portals, leaving teleport commands out is a perfectly good call.
Frequently asked questions
Do I really need LuckPerms alongside EssentialsX? In practice, yes. Without a permissions plugin only operators get every command and ordinary players get almost nothing, so nobody can use /home or /tpa. LuckPerms is the 2026 standard for permissions and ranks and works directly with EssentialsX.
Does EssentialsX work on a modpack server such as All the Mods 10? No. ATM10 runs on NeoForge with Minecraft 1.21.1 and Java 21, and a NeoForge server does not load Bukkit plugins. If you want EssentialsX you need a Paper, Purpur or Spigot server; if you want the modpack, use the teleport mods that come with it.
How much RAM does EssentialsX use? Barely any. Memory use is driven by your world size, player count and any mods, not by a command plugin. At MC-Node a 2 GB package costs EUR 2.20 per month and 8 GB costs EUR 8.80 per month; EssentialsX does not shift that choice.
What is the difference between Essentials and EssentialsX? EssentialsX is the continuation of the original Essentials project and the version you install today. Always download the build that matches your server version: Minecraft Java has used year-based version numbers since 2026, with 26.1 "Tiny Takeover" and 26.2 "Chaos Cubed", while 1.21 "Tricky Trials" is still the most played version on Dutch servers.
Can I disable individual commands? Yes, in two ways. Through disabled-commands in plugins/Essentials/config.yml you switch a command off completely, for example because another plugin should handle it. If you only want to block it for certain groups, simply do not grant that group a permission such as essentials.back.