Restrict one EssentialsX warp to an approved player group
Applies to: EssentialsX; match the linked maintainer documentation to your installed platform and release.
Documentation checked .
A staff or event warp should be usable only by its intended audience. Check per-warp permissions and test the destination without giving the group permission to create or delete warps.
Follow the procedure
- Choose an existing safe warp and record its exact name. Check that the arrival position has solid ground and does not expose a private staff area.
- Inspect the EssentialsX configuration’s per-warp-permission option. Save the previous setting because enabling this policy can affect every existing warp.
- List the public warps that ordinary players must keep using. Prepare the required individual permissions for those destinations before changing a live server’s policy.
- Grant the intended role the base warp permission and the documented node for the selected warp. Keep warp creation, deletion and wildcard destination access separate.
- Test arrival with a group member and denial with a normal player outside the group. Repeat for a previously public warp to detect an accidental loss of normal travel.
- Confirm menu buttons and aliases use the same restricted command path. A menu that runs the teleport as console may bypass the player’s intended permission check.
Check the result
The approved group should reach the selected warp while other ordinary players cannot use either the command or its menu shortcut. Existing public warps should remain usable by their intended audience. Check the actual teleport and destination rather than relying only on whether the warp appears in a list.
No comments to display
No comments to display