Set up EssentialsX on a Minecraft server

EssentialsX gives your Minecraft Java server homes, warps, spawn, kits, a basic economy and the moderation commands vanilla is missing. Here is how to install it, which modules you actually need, and how to hand the commands out.

6 min read · Updated Oct 21, 2026 · By GuavaHost Team

What EssentialsX actually adds

Vanilla Minecraft gives you operators and nothing else. EssentialsX is the plugin almost every survival server starts with, because it fills in the everyday things players expect:

• /home, /sethome and /delhome, so players can teleport back to their base.
• /spawn and /setspawn for a proper hub, plus /warp and /setwarp for named destinations like a shop district or a nether portal.
• /tpa and /tpaccept, teleport requests between players, instead of ops dragging people around with /tp.
• /kit, a named bundle of items players can claim, with a cooldown.
• A simple economy with /balance, /pay and /baltop, and the plumbing other plugins use to read it.
• Moderation: /mute, /kick, /tempban, /jail, /vanish, /socialspy, plus /nick and a chat format with rank prefixes.
• Quality of life: /back after a death, /afk, /seen, /msg, /ignore, /repair, /hat, /near.

It only runs on a plugin server, so Paper, Spigot, Bukkit or Purpur. On Fabric or Forge it will not load at all. If you are not sure which you are running, check the Version page under Minecraft tools and read Paper vs Purpur vs Spigot vs Fabric vs Forge before you pick.

Install it

EssentialsX is on Modrinth, so the Plugins page under Minecraft tools in your server menu can fetch it for you: open Find plugins, search EssentialsX, click Install, then restart. The full click path, and the manual upload route for anything not listed there, is in Installing plugins on Minecraft Java.

Take a snapshot on the Backups page first. EssentialsX writes a lot of new files and starts managing spawn, and rolling back is much easier than unpicking it by hand.

Pick your modules

EssentialsX ships as several jars. The core one is required, the rest are optional, and you should only add the ones you want:

Two warnings. Do not run EssentialsXChat alongside another chat plugin, because both rewrite the chat line and you get doubled messages or no prefixes. And if you already run a land claim or anti grief plugin, skip EssentialsXProtect: its block rules will fight the other plugin's, and you will spend an evening working out which one is denying a placement.

Every module has to be the same version as the core jar. Mixing an old EssentialsXSpawn with a new EssentialsX is a classic cause of a console error on boot.

Where its settings live

After the first restart, open the Files tab and look in plugins/Essentials/. The files you will touch:

• config.yml is the big one: homes per rank, teleport cooldowns and warmups, the starting balance, currency symbol, what /kit hands out, and whether /back works after death.
• kits.yml on newer builds holds the kit definitions.
• warps/ is one small file per warp, created by /setwarp.
• userdata/ is one file per player: their homes, balance, last location and mutes. Do not hand edit these while the server is running.

A useful starting point in config.yml:

teleport-cooldown: 5
teleport-delay: 3
starting-balance: 100
currency-symbol: '$'
sethome-multiple:
  default: 1
  vip: 3
  staff: 10

teleport-delay is the warmup, so a player has to stand still for three seconds before /home fires, which stops people escaping a fight mid hit. sethome-multiple is how you sell or reward extra homes: each entry is a permission group, and the player gets the highest number they have permission for.

Run /essentials reload in the Console after editing, or restart if a change looks ignored.

The permissions it needs

This is the part people skip, and then wonder why normal players cannot use /home. EssentialsX grants almost nothing by default. Every command has a node, shaped essentials.<command>, and you hand them out with a permissions plugin. Set up permissions with LuckPerms covers groups and the web editor.

A sane starting set for your default group:

essentials.home
essentials.sethome
essentials.delhome
essentials.spawn
essentials.warp
essentials.warp.list
essentials.tpa
essentials.tpaccept
essentials.tpdeny
essentials.msg
essentials.balance
essentials.pay
essentials.afk
essentials.back
essentials.kit
essentials.kit.starter

Note the last line. essentials.kit lets a player use the command, and essentials.kit.<name> lets them use one specific kit, so a starter kit needs both.

For staff, add the moderation nodes deliberately rather than giving the whole essentials.* wildcard. essentials.vanish, essentials.mute, essentials.kick, essentials.tempban and essentials.socialspy cover most of it. Give staff the right tools on a Minecraft server goes through which commands a moderator genuinely needs, and which ones you should keep to yourself.

Remember that ops bypass permission checks entirely, so test a rank with yourself deopped or you will think everything works when it does not.

The economy side

EssentialsX includes a working balance system, but on its own that is just a number. Shop plugins, job plugins and auction houses read it through Vault, a small bridge plugin that lets any economy plugin talk to any plugin that wants money. Install Vault, keep EssentialsX as your economy, and the rest fall into place. Add an economy and player shops to Minecraft covers the whole setup, including the Minecraft EULA rules about selling advantages for real money.

When commands collide

Two plugins can both register /home or /warp. Whichever loads first wins, and the other is reachable only by its full name, like /essentials:home. If a command does the wrong thing:

1. Run /plugins or check the Console startup log to see what else is loaded.
2. Open commands.yml in your server root on the Files tab and add an alias that points the plain command at the plugin you want.
3. Restart and test as a normal player, not as an op.

You can also disable individual EssentialsX commands in config.yml under disabled-commands, which is the cleaner fix when another plugin is meant to own that command.

Common questions

Do I need all of the EssentialsX modules?

No. Install the core jar, add EssentialsXSpawn if you want /spawn, and only add the others if you have a specific reason. Every extra module is more config to keep straight and another chance of a conflict with a plugin you already run.

Why can my players not use /home?

Because EssentialsX grants nothing by default, the permission node has to be given to your default group. Add essentials.home and essentials.sethome in LuckPerms, then test with yourself deopped, since ops bypass permissions and will always appear to work.

Will EssentialsX break my existing world or plugins?

It does not touch world data, so your builds are safe. The usual friction is with chat plugins and anti grief plugins, which is why you skip EssentialsXChat and EssentialsXProtect when you already run something in that space.

Can I remove EssentialsX later?

Yes. Delete the jars from plugins and restart. Homes, warps and balances stay in the plugins/Essentials folder, so you keep them if you reinstall, but any other plugin that read the economy through Vault will lose it until you give it another economy plugin.

Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.

• essentialsx
• plugins
• minecraft
• java
• permissions

Host a Minecraft Java server From $3.99/mo, with instant setup and DDoS protection.

Still need help? Our team is online 24/7 to answer questions.

Contact support