EssentialsX

EssentialsX adds what a server misses most: a player can save a home (/sethome, /home), request a teleport (/tpa, /tpaccept), send a private message (/msg), return to spawn (/spawn), or see who is online (/list). Staff also get /kick, /mute, /jail, /vanish or player teleport.

The bundle is divided into modules: EssentialsX (core), EssentialsXChat (chat formatting and prefixes), EssentialsXSpawn (spawn and teleports), EssentialsXProtect (preventing destruction of others' builds), and EssentialsXGeoIP (where a player is from). For most servers, the core and Chat are enough.

A player can have multiple homes depending on permissions (essentials.sethome.multiple), including custom per-group rules — you can set it so a VIP has three homes and a regular player has one. If you set the permissions wrong, the player will save a home but won't be able to get to it; so it's worth starting with one and adding more.

EssentialsX only brokers economic commands (/balance, /pay, /worth) — it needs Vault and an economy plugin for them. Without Vault, these commands silently do nothing, which is a common source of confusion.

The Chat module supports colored chat, formatting with PlaceholderAPI, and private messages. The permission essentials.chat.color allows players to write in color and format text, which is quickly abused on public servers — give it only to ranks that can handle it.

EssentialsX pairs well with LuckPerms (permissions), Vault (economy), and PlaceholderAPI (placeholders for chat and tab list). On its own, it is a set of basic commands that most Czech servers take as their very first plugin.

1. Find out the server version (/version) and download EssentialsX from essentialsx.net/downloads or from Modrinth — choose the build for your Minecraft version.
2. Upload to the plugins folder the core .jar (EssentialsX) and only the modules you really want (Chat, Spawn, Protect, GeoIP).
3. Restart the server. The console will print how many commands were loaded and where the configuration files are.
4. Go through plugins/EssentialsX/config.yml: set mainly spawn-on-join (should the player appear at spawn after logging in?) and teleport-invulnerability (invulnerability after teleport so nobody dies from falling).
5. If you use Chat, edit plugins/EssentialsXChat/config.yml — chat format and prefixes. With PlaceholderAPI you can write a format with placeholders.
6. Set spawn: stand at the place and type /setspawn.
7. Create warps: stand at the place and type /setwarp nazev (players will get there with /warp nazev).
8. Assign permissions: a regular player needs essentials.home, essentials.sethome, essentials.tpa, essentials.spawn, essentials.warp, essentials.msg and essentials.list; management then essentials.kick, essentials.mute and essentials.vanish.
9. Deny players essentials.give, essentials.gamemode and essentials.tp — they belong only to management.
10. Verify on yourself: /sethome, /home, /spawn, /warp. Every command must respond, not stay silent.
11. If you want to use money, install Vault and an economy plugin — without them /balance a /pay nefunguj.
12. Back up the plugins/EssentialsX folder: it contains homes, warps, and the list of muted players.

Without Vault, economy commands (/balance, /pay, /worth) don't work — EssentialsX only mediates them. If players are to work with money, install Vault and an economy plugin (for example EssentialsX Economy).
The permission essentials.chat.color allows players to write in color in chat and format text. On public servers, this is quickly abused — give it only to ranks that can handle it.
Homes are tied to players. If a player changes their nickname, they may lose their homes; when moving to another server, without a backup of the plugins/EssentialsX folder they will be completely lost.
spawn-on-join is the most common source of misunderstanding: when it is disabled, the player stays where they logged out, and the owner then wonders why spawn doesn't work.
The chat format is set in the Chat module, not in the core. If the format hasn't changed, check that the module is actually installed, and after editing the config run /ess reload.
Kdy. If the command doesn't respond at all, usually the player doesn't have permission for it — and EssentialsX doesn't report it in some cases. Verify permissions via /lp info (LuckPerms).
Back up plugins/EssentialsX: homes, warps, and the mute list are only there and are not in the database.