Learning how to install EssentialsX is the first thing most server owners do, because it adds the core commands players expect: /home and /sethome, /warp, /spawn, kits, /tpa teleport requests, and a simple built-in economy. EssentialsX is a Bukkit-family plugin, so it runs on Paper, Spigot, Purpur, and Bukkit servers and drops straight into your /plugins folder. This guide walks through downloading the correct build from the official source, installing it on your Loafhosts Java server, adding the modular extras like Chat and Spawn, and wiring the economy to Vault so other plugins can read player balances.
What EssentialsX Does and Why You Want It
EssentialsX is the modern, maintained successor to the original Essentials plugin and bundles hundreds of quality-of-life commands into one suite. Out of the box it gives players personal homes, server warps, a spawn point, kits, teleport requests between players, message and mail commands, and a lightweight economy with /balance and /pay. For admins it adds moderation tools like /mute, /kick, /ban, /vanish, and god mode. It is the de facto baseline for survival, SMP, and economy servers.
Tip: EssentialsX replaces the abandoned original Essentials; never run both at once
Tip: Most survival and SMP servers treat EssentialsX as a required base plugin
Tip: Players get /home, /sethome, /warp, /spawn, /tpa, and /pay the moment it loads
Note: EssentialsX is a Bukkit-family plugin, so it loads on Paper, Spigot, Purpur, and Bukkit. It can technically load on Folia, but the EssentialsX team advises against it due to userdata-loss risk. It is not a Forge or Fabric mod and will not load on Vanilla, Forge, or Fabric servers
How EssentialsX Is Built: Core Plus Modules
EssentialsX is modular. The main EssentialsX jar is the core and is the only one you strictly need. Optional add-on jars layer on extra features: EssentialsX Chat for chat formatting and channels, EssentialsX Spawn for spawn-on-join control, EssentialsX Protect for block and grief protection, EssentialsX GeoIP for showing player countries, EssentialsX AntiBuild for build permissions, and EssentialsX Discord for a Discord bridge. You install only the modules you want, and every module you add goes into the same /plugins folder alongside the core jar.
- Decide which modules you need; the EssentialsX core is mandatory
- Add EssentialsX Chat if you want prefixes, suffixes, or chat formatting
- Add EssentialsX Spawn if you want new players to spawn at a set point
- Add EssentialsX GeoIP, Protect, AntiBuild, or Discord only if you use them
- Keep every module on the exact same EssentialsX version as the core
Warning: Mixing module versions, for example a new core with an old Chat jar, causes errors on startup; keep them all on the same build
Where to Download EssentialsX (Official Source)
Download EssentialsX from its official channels only: the EssentialsX website downloads page at essentialsx.net, the EssentialsX project on Modrinth, the EssentialsX/Essentials releases on GitHub, or the EssentialsX resource on SpigotMC. All of these are run by the EssentialsX team. Grab the latest build that lists support for your server’s Minecraft version, and download the core jar plus any module jars from the same release. EssentialsX is listed on CurseForge, Modrinth, and SpigotMC, so the one-click Plugin Manager can install it from any of those sources; for the very latest build, downloading from one of these official channels and uploading it always works.
Tip: essentialsx.net offers both stable releases and dev builds; use a stable release for production
Tip: Always match the build to your Minecraft version, for example a 1.21-compatible build for a 1.21 server
Warning: Do not download EssentialsX from random reupload sites; use essentialsx.net, Modrinth, GitHub, or SpigotMC only
Install EssentialsX on Loafhosts (Manual Upload)
On Loafhosts the surest way to get the newest EssentialsX build is a manual upload through the LPV5 panel, and the one-click Plugin Manager can also install EssentialsX from CurseForge, Modrinth, or SpigotMC. Log in to LoafHub at hub.loafhosts.com, open your server, and use the File Manager to drop the jar into /plugins. Plugins are only picked up when the server starts, so a full restart is the final step. Once it loads, EssentialsX appears in the panel’s Plugin Manager labelled as External.
- Log in to LoafHub at hub.loafhosts.com and open your Java server
- Confirm the server type is Paper, Spigot, Purpur, or Bukkit in the LPV5 panel
- Open the File Manager and navigate to the plugins folder
- Upload the EssentialsX core jar, plus any module jars, into /plugins
- Restart the server from the LPV5 panel so the plugins load
- Check the console for an EssentialsX enabled message with no errors
Note: You can also upload via SFTP using the connection details shown in the LPV5 panel; the destination is still the plugins folder
Note: Manually uploaded plugins show up in the LPV5 Plugin Manager as External, which is expected
Using the One-Click Plugin Manager (If Listed)
Loafhosts also has a one-click Plugin Manager that searches CurseForge, Modrinth, and SpigotMC (a provider dropdown lets you pick All sources or a single source) and installs the jar into /plugins for you. It works on Bukkit-family servers; a few CurseForge resources whose authors disable automated downloads can’t be auto-installed, but you can usually grab those same plugins from the Modrinth or Spigot provider instead. EssentialsX is published on all three, so a search inside the Plugin Manager should return it; pick the official EssentialsX and install it, or use the manual upload above when you want a specific or newer build. The Plugin Manager guide shows the one-click flow in detail.
- Open your server in LoafHub and open the Plugins tool in the LPV5 panel
- Search for EssentialsX in the Plugin Manager
- If the official EssentialsX appears, install it and restart the server
- If it does not appear, fall back to the manual upload steps above
Tip: Manual upload from an official source is always reliable and gets you the exact build you want
Pairing the EssentialsX Economy with Vault
EssentialsX ships its own economy, but shops, jobs, and other money plugins do not read it directly. They read Vault, the abstraction API that sits between plugins. To make the EssentialsX economy usable across your server, install Vault as well: it lets EssentialsX register as the economy provider so every Vault-aware plugin can see balances and process /pay transactions. Vault does nothing on its own; it simply connects EssentialsX to everything else. Installing Vault is identical to any other plugin: drop the Vault jar into /plugins and restart.
- Install the EssentialsX core so it provides the economy
- Install Vault into /plugins as the economy bridge
- Restart the server so Vault detects EssentialsX as the economy provider
- Add a permissions plugin like LuckPerms so Vault can also serve permissions and prefixes
Warning: Run only one economy provider; if you install another economy plugin alongside EssentialsX, disable EssentialsX economy to avoid balance conflicts
Note: EssentialsX provides the economy; Vault exposes it to other plugins; LuckPerms provides permissions and chat data through Vault
First-Time Configuration and Common Gotchas
On first start EssentialsX generates a config.yml inside the plugins/Essentials folder. The most common early tasks are setting the spawn point, defining warps, and granting command permissions. EssentialsX commands are permission-gated, so on a fresh install non-operators may not be able to use /home or /tpa until you grant the matching permission nodes through your permissions plugin. Edit config files through the LPV5 File Manager, and remember that config changes apply on restart for safety.
| Command | Description | Example |
|---|---|---|
/setspawn | Set the server spawn point at your current location (requires permission or operator) | /setspawn |
/setwarp | Create a named warp at your current location | /setwarp shop |
/sethome | Let a player save a personal home | /sethome base |
/tpa | Send a teleport request to another player | /tpa Steve |
Tip: Grant the essentials.home, essentials.sethome, essentials.warp, and essentials.tpa nodes to your default player group so normal players can use them
Tip: Set max homes per group with the essentials.sethome.multiple permission tiers in config
Warning: A common gotcha is players reporting that /home does nothing; that is almost always a missing permission node, not a broken install
Frequently Asked Questions
Is EssentialsX a plugin or a mod?
EssentialsX is a Bukkit-family plugin. It installs into your server’s /plugins folder and runs on Paper, Spigot, Purpur, and Bukkit. It does not officially support Folia, and the EssentialsX team warns against using it on Folia due to risk of data loss. It is not a Forge or Fabric mod and will not load on Vanilla, Forge, or Fabric servers, which use a separate /mods folder.
Where do I download EssentialsX?
Use an official source: the essentialsx.net downloads page, the EssentialsX project on Modrinth, the EssentialsX/Essentials releases on GitHub, or the EssentialsX resource on SpigotMC. Download the latest build that supports your Minecraft version, plus any module jars from the same release.
How do I install EssentialsX on Loafhosts?
Log in to LoafHub at hub.loafhosts.com, open your server, open the File Manager, go to /plugins, and upload the EssentialsX core jar (plus any modules). Then restart the server from the LPV5 panel. Plugins only load on restart, and the plugin then appears in the Plugin Manager as External.
Do I need Vault for EssentialsX?
Not for the basic commands like /home and /warp. You need Vault if you want the EssentialsX economy to work with other money plugins such as shops or jobs, because those read balances through Vault rather than directly from EssentialsX. Vault is installed the same way: drop the Vault jar into /plugins and restart.
Why can players not use /home or /tpa after I installed EssentialsX?
EssentialsX commands are permission-gated. On a fresh install, non-operator players need the relevant permission nodes, such as essentials.home and essentials.tpa, granted through a permissions plugin like LuckPerms. The install is fine; the players simply lack the permissions for those commands.
Do I install the EssentialsX modules separately?
Yes. The EssentialsX core jar is required, and each module like Chat, Spawn, Protect, or GeoIP is a separate jar you place in /plugins. Keep every module on the exact same version as the core, then restart so they all load together.