How to create a warp point using EssentialsX plugin on your Minecraft server

Warps are one of the most-used features in EssentialsX. They let you create named teleport points — a spawn hub, a PvP arena, a shop district, an event zone — and let players jump straight to them with a single command. This guide is the complete, no-fluff reference for warps in EssentialsX: how to create them, how players use them, how to delete them, and how the per-warp permission system actually works so you can lock specific warps to specific ranks.

Before anything else, a quick platform check. EssentialsX is a Bukkit-API plugin, which means it runs on Spigot, Paper, and forks like Purpur — Minecraft: Java Edition only. It does not run on vanilla, Bedrock, Fabric, or Forge servers. If you are running a Paper or Spigot box, you are good to go. If you need a server that can drop EssentialsX in cleanly, our Minecraft server hosting plans ship Paper-ready out of the box, and our Minecraft setup documentation walks through plugin installation step by step.

What a warp actually is

A warp in EssentialsX is a saved location — a world, plus X/Y/Z coordinates and a facing direction — stored under a name you choose. Once a warp exists, any player with permission can teleport to it instantly. Warps are server-wide and persistent: they survive restarts and are shared by everyone (unlike a personal home set with /sethome). That makes them perfect for public destinations: spawn, market, nether hub, arena, and so on.

Creating a warp with /setwarp

To create a warp, stand exactly where you want the teleport destination to be — facing the direction you want players to arrive facing — and run:

/setwarp 

For example, to make a warp called spawn:

/setwarp spawn

That captures your current position and facing as the warp named spawn. The command also ships with several aliases that do exactly the same thing, in case you forget the primary name:

  • /createwarp
  • /ecreatewarp
  • /esetwarp

The permission required to create or overwrite a warp is:

essentials.setwarp

This is normally a staff/admin-only node — you don’t want every player redefining your spawn warp. If you want to give a specific player or rank the ability to set only one named warp without handing them the broad essentials.setwarp power, EssentialsX supports a scoped variant:

essentials.setwarp.

For instance, granting essentials.setwarp.event lets a trusted event host create or update the event warp, but nothing else. To overwrite an existing warp, simply run /setwarp again at the new location — it replaces the old coordinates.

Teleporting to a warp with /warp

Once a warp exists, players travel to it with:

/warp 

So /warp spawn teleports the player to the spawn warp. The full registered usage of the command is /warp [player], which tells you two things. First, running /warp with no warp name lists the available warps in a paginated menu (you can pass a page number to flip through pages). Second, an admin can warp another player by appending their name:

/warp  [player]

For example, /warp arena Steve sends the player Steve to the arena warp. The aliases for the warp command are:

  • /ewarp
  • /warps
  • /ewarps

The base permission to use warps at all is:

essentials.warp

To let a player warp someone else (the [player] argument above), grant:

essentials.warp.otherplayers

And to let a player see the warp list, the node is:

essentials.warp.list

Listing warps — /warps

Here is a detail that trips a lot of admins up: /warps is not a separate command. It is registered as an alias of /warp. When you run /warps on its own, it behaves exactly like running /warp with no warp name — it prints the paginated list of every warp the player is allowed to see. Both of these do the same thing:

/warps
/warp

Because the list is permission-aware (more on that below), two players running /warps may see different warps depending on what they have access to. Viewing the list is gated by the essentials.warp.list node.

Deleting a warp — /delwarp

To remove a warp permanently, use:

/delwarp 

So /delwarp arena deletes the arena warp. The deletion command has a generous set of aliases, all equivalent:

  • /edelwarp
  • /remwarp
  • /eremwarp
  • /rmwarp
  • /ermwarp

The permission node is:

essentials.delwarp

Like setwarp, this is a node you almost always restrict to staff. Deleting a warp does not affect any other warps and cannot be undone, so double-check the name before you confirm.

The four warp commands at a glance

TaskCommandAliasesPermission
Create a warp/setwarp /createwarp, /ecreatewarp, /esetwarpessentials.setwarp
Teleport to a warp/warp [player]/ewarp, /warps, /ewarpsessentials.warp
Delete a warp/delwarp /edelwarp, /remwarp, /eremwarp, /rmwarp, /ermwarpessentials.delwarp
List warps/warps (alias of /warp)essentials.warp.list

Per-warp permissions: locking individual warps to ranks

By default, anyone with essentials.warp can use any warp. On most servers that is fine. But often you want a VIP-only warp, a staff warp, or an event warp that regular players can’t see or use. EssentialsX supports exactly this through its per-warp permission system.

The feature is off until you enable it. Open your EssentialsX config.yml and set:

per-warp-permission: true

With that turned on, each warp is gated by its own node. The pattern uses the plural warps:

essentials.warps.

So a warp named vip requires the node essentials.warps.vip. A player who lacks that node cannot teleport to the warp — and importantly, the warp also will not appear in their /warps list, keeping it hidden from players who aren’t meant to know about it. To grant a player or group access to every warp at once, use the wildcard:

essentials.warps.*

Pay close attention to singular vs. plural here, because it is the number-one source of confusion:

  • essentials.warp — singular — grants command access (the ability to use /warp at all).
  • essentials.warps. — plural — grants per-warp access to one specific named warp when per-warp-permission is enabled.
  • essentials.warps.* — plural with wildcard — grants access to all warps.

Both forms are real and distinct nodes. A player typically needs essentials.warp to use the command in the first place, and then the relevant essentials.warps. (or the wildcard) for each warp you’ve locked down.

Worked example: a VIP-only warp

Say you want a warp called vipzone that only VIP members can reach. Here is the full sequence.

  1. Enable the feature in config.yml: set per-warp-permission: true and reload or restart EssentialsX.
  2. Stand at the destination and run /setwarp vipzone (requires essentials.setwarp).
  3. In your permissions plugin (LuckPerms, etc.), give your VIP group the nodes essentials.warp and essentials.warps.vipzone.
  4. Make sure your default/regular player group has essentials.warp for normal warps, but not essentials.warps.vipzone — so the VIP warp stays hidden and inaccessible to them.

Now a VIP runs /warp vipzone and arrives; a regular player who tries it is denied and never sees the warp in their list. You can repeat this per warp — staff warps, donor warps, seasonal event warps — each with its own essentials.warps. node.

Warps vs. homes vs. RTP

It helps to know where warps fit among EssentialsX’s teleport tools. Warps are shared, public, admin-defined destinations. Homes (/sethome / /home) are personal points each player sets for themselves. And if you want players to scatter randomly into the wilderness rather than land on a fixed point, that is a job for random teleport — EssentialsX has a basic built-in option, but many servers use the dedicated BetterRTP plugin for far more control over radius, biomes, and per-world settings. Use warps for the places that should always be in the same spot; use RTP for “drop me somewhere new.”

Other EssentialsX staff tools worth setting up

Warps are usually one of the first things admins configure, but EssentialsX is a deep toolkit. A few sibling features pair naturally with a warp setup on most servers:

Troubleshooting common warp problems

  • “You do not have access to that warp.” You enabled per-warp-permission: true but the player lacks essentials.warps.. Grant the per-warp node or the essentials.warps.* wildcard.
  • A warp doesn’t show in /warps. Same cause — with per-warp permissions on, warps the player can’t access are hidden from the list. Also confirm the player has essentials.warp.list.
  • Players can’t warp at all. Check they have the singular essentials.warp node, not just the plural per-warp nodes.
  • Can’t warp another player. The admin needs essentials.warp.otherplayers to use the [player] argument.
  • Setwarp says no permission. The player needs essentials.setwarp (or the scoped essentials.setwarp. for a single warp).

Frequently asked questions

What command creates a warp in EssentialsX?

Stand where you want the destination and run /setwarp — for example /setwarp spawn. It requires the essentials.setwarp permission. Aliases include /createwarp and /esetwarp.

How do players teleport to a warp?

They run /warp , which needs essentials.warp. An admin with essentials.warp.otherplayers can send someone else with /warp .

What’s the difference between /warp and /warps?

None functionally — /warps is registered as an alias of /warp. Running either with no warp name shows the paginated list of warps the player is allowed to see, gated by essentials.warp.list.

How do I make a warp VIP- or staff-only?

Set per-warp-permission: true in EssentialsX’s config.yml, then grant only the intended group the node essentials.warps.. Use essentials.warps.* to allow all warps at once. Note the plural warps in these nodes.

How do I delete a warp I no longer need?

Run /delwarp (permission essentials.delwarp). Aliases include /rmwarp and /remwarp. Deletion is permanent and doesn’t affect other warps.

Does EssentialsX work on my server type?

EssentialsX runs on Spigot, Paper, and forks like Purpur for Minecraft: Java Edition. It does not run on vanilla, Bedrock, Fabric, or Forge. If you need a Paper-ready box, see our Minecraft documentation for installing plugins.

Free Minecraft Tools

Speed up your server with our free Minecraft tools:

Ready to play?

Run your own Minecraft server with XGamingServer

Spin up an always-on Minecraft server your friends can join in minutes — no port-forwarding, no tech headaches.

99.9%Uptime SLA
< 5 minInstant setup
24/7Human support
DDoSProtected
Instant setup Your server is live in minutes with a one-click control panel.
Mods & plugins Install mods, plugins and workshop content in a few clicks.
DDoS protected Enterprise DDoS mitigation keeps your server online 24/7.
Low-latency hardware Premium CPUs & NVMe SSDs for lag-free multiplayer.
Free backups Automatic backups so your world is never lost.
Real human support Gamers helping gamers — 24/7, no bots, no scripts.

Pick your Minecraft plan & play in minutes

See all plans
Starter $8.40/mo 4 GB RAM Renews $12/mo Buy now
Rookie $17.50/mo 8 GB RAM Renews $25/mo Buy now
Pro $24.50/mo 12 GB RAM Renews $35/mo Buy now