Minecraft

How to Set Up PermissionsEx Ranks on a Minecraft Server

Minecraft·May 20, 2026·17 min read

PermissionsEx Overview

Many Minecraft servers use ranks to separate regular players, staff, donors, moderators, and administrators. Those ranks are only useful when each one has the right permissions attached. PermissionsEx, often shortened to PEX, is a plugin that lets you create groups, assign commands, set inheritance, and control what each player can do.

You can manage PEX with in-game or console commands, or by editing its `permissions.yml` file directly. Commands are usually easier for a first setup, while file editing gives more control once you understand the format. YAML is picky, so one misplaced space can ruin an otherwise peaceful afternoon.

For chat prefixes or suffixes to show beside player names, you also need Vault and a compatible chat plugin such as EssentialsXChat.

Installing PermissionsEx

  1. Open the PEX 1.0 GitHub releases page and download the `.jar` file from the release you want to use.
  1. Open your server panel and stop the Minecraft server.
  2. Check that the server is using a plugin-compatible software type, such as Paper or Spigot.
  3. Open the file manager or FTP for the server, then go to the `plugins` folder.
  4. Upload the downloaded PEX `.jar` file into that folder.
  1. Return to the main server page and start the server again.

After the restart, run `/plugins` in-game or `plugins` from the console. If PermissionsEx appears in the plugin list, the installation worked and you can begin creating groups.

Creating Your First Group with Commands

The first commands should be run from the server console so you do not need permissions before permissions exist. When using console commands, remove the `/` at the beginning. For example, `/pex` becomes `pex`.

To create an administrator group:

  1. Run `pex group Admin create` to create the group.
  2. Run `pex group Admin add permissions.*` to give that group every permission node.
  3. Run `pex user YourPlayerName group set Admin` to place yourself in the group.

Example:

`pex user Steve group set Admin`

Once assigned, join the server and test an admin command. If it works, the group is active.

Customizing Groups

PEX groups can be adjusted with ranks, prefixes, and specific permission nodes. A lower rank number means higher importance, so an owner or admin group often uses a very low value.

Useful examples:

  • `pex group Admin set rank 1` makes Admin one of the highest priority groups.
  • `pex group Moderator set rank 100` gives Moderator a lower priority than Admin.
  • `pex group Admin prefix "&0(&4Admin&0)&7 "` adds an Admin prefix in chat, if Vault and a chat plugin are installed.
  • `pex group Mod add essentials.fly` gives the Mod group access to the EssentialsX fly command.

You can repeat the same pattern for groups such as Member, VIP, Helper, Moderator, Admin, and Owner. Keep group names simple so they are easy to type when assigning players.

Editing the Permissions File

Some server owners prefer editing the configuration file because it shows the complete structure in one place. This is useful for larger setups, but it is less forgiving than commands.

Before editing, stop the server and keep a backup copy of the current file. A plain text backup is enough. Future you may appreciate it.

Finding the File

  1. Stop the server from your panel.
  2. Open the file manager or FTP.
  3. Go to `plugins`, then open the `PermissionsEx` folder.
  4. Edit `permissions.yml`.

Understanding the Format

A fresh file usually contains only the default group. To create a new group manually, copy the default group structure and change the values.

An Admin group usually includes these parts:

  • `Admin:` is the group name. You can rename it to anything clear and consistent.
  • `permissions:` lists the permission nodes the group receives.
  • `permissions.*` gives access to every permission, which should only be used for trusted administrators.
  • `rank:` controls the group priority. Lower numbers are higher priority.
  • `prefix:` controls the chat tag shown before the player name when Vault and a chat plugin are present.

After adding the group, add your username or UUID under the users section and set the group to Admin. Make sure indentation matches the rest of the file, then save and restart the server.

What to Add Next

After the first admin rank works, build the rest of your permission structure. A simple server might use:

  • `Member` for regular players.
  • `VIP` for supporters or special access.
  • `Mod` for moderation commands.
  • `Admin` for full management access.

Add only the permissions each rank actually needs. Giving every group `permissions.*` is fast, but it also turns basic mistakes into server-wide problems.

For deeper command coverage, check the official PermissionsEx documentation or wiki for the plugin version you are using.

Common Issues

Plugin Commands Do Not Work

Confirm that the server is running Paper, Spigot, or another plugin-compatible server type. Also check that the PEX `.jar` file is inside the `plugins` folder, not the server root or another directory. Restart after uploading the file.

Permissions Do Not Apply After File Edits

This is usually a YAML formatting problem. Check indentation, spacing, and group nesting. A YAML validator can help find mistakes before you paste the corrected file back into the panel editor. After saving, restart the server.

Prefixes Do Not Show in Chat

PEX does not display chat prefixes by itself. Install Vault and a chat plugin such as EssentialsXChat, then restart the server. If the prefix still does not show, confirm that the group has a valid `prefix` value and that the player is actually assigned to that group.

Helpful References

  • EssentialsX
  • Vault
  • PermissionsEx wiki

Final Notes

PermissionsEx is a practical way to build a rank system for a Minecraft server. Once the first group is working, the rest is mostly careful repetition: create a group, add the permissions it needs, assign players, then test. Keep backups before editing `permissions.yml`, watch the indentation, and avoid handing out wildcard permissions unless the player truly needs full control.

Still have questions?

Come chat with us and we will get back to you as soon as possible!

Contact Support