EssentialsX Commands Every Admin Should Know

ZCraft Studios

The commands that actually get used day-to-day, grouped by what they're for — not the full three-hundred-command list.

EssentialsX Commands Every Admin Should Know

EssentialsX ships with close to three hundred commands. Most servers use about twenty of them regularly.

Movement & Teleport

/home <name>        teleport to a saved home
/sethome <name>      save a home at your location
/tpa <player>        request to teleport to a player
/tpahere <player>     request a player teleport to you
/warp <name>         teleport to a server warp
/spawn               teleport to world spawn
/back                 return to your previous location

Economy

/balance              check your own balance
/balance <player>      check another player's balance
/pay <player> <amount>  send money to another player
/baltop                 leaderboard of richest players

Economy commands need a Vault-compatible plugin backing them — EssentialsX ships its own economy provider, but any Vault-compatible economy plugin works too.

Moderation

/kick <player> [reason]
/ban <player> [reason]
/tempban <player> <duration> [reason]
/mute <player> [duration] [reason]
/warn <player> [reason]
/jail <player> <jail name>

/tempban 1d and similar duration shorthand (h, d, w) are supported directly in the command.

Kits & Items

/kit <name>        claim a kit
/kits               list available kits
/give <player> <item> <amount>
/item <item>        give yourself an item (op only)

Kits are defined in kits.yml, including cooldowns per kit.

Server Management

/essentials:reload     reload EssentialsX's config without a full restart
/whitelist add <player>
/whitelist remove <player>
/seen <player>         last-login info for a player

A Couple of Things Worth Knowing

  • Most of these commands have permission nodes under essentials.<command> — a rank without the matching node simply can't use it, which is the basis of most rank/permission setups.
  • kits.yml and messages.properties are the two files admins end up editing most — kits for progression pacing, and messages.properties (not YAML — EssentialsX's message files use Java's .properties format) for making the plugin's default text actually match the server's tone.

Rewriting messages.properties From Scratch

Editing messages.properties directly means working through several hundred keys, each controlling one specific plugin message — doable, but a real time investment if the goal is a fully restyled, consistent tone across every command rather than tweaking a handful of lines. ZCraft Studios' EssentialsX Messages Config is a complete rewrite of that file (1,600+ lines, English and Spanish) if that's the faster path.

Share: