Our Discord Find a crew to play with. Join
Discord
Servers - Administration

Minecraft server ranks and permissions

A rank and permission system is the foundation of every serious Minecraft server. It decides who can use which commands, who gets a VIP prefix in chat and how players climb the ladder of ranks. This guide walks you through LuckPerms, from installation to advanced promotion tracks and Vault integration.

What permissions are in Minecraft

Permissions are an access control system that decides what a player can do on a server. Every command, every plugin feature and every ability, from opening shops to teleporting, is tied to a specific permission node.

A permission node is just a string, such as essentials.home, essentials.tpa or worldedit.selection.pos1. If a player has that node in their permission profile, they can use the feature. If they don't, they get a "You don't have permission" message.

Permissions are usually assigned to groups (ranks) rather than to individual players. A player who belongs to a group automatically inherits all of its permissions. That way, changing the permissions of one rank instantly affects all of its members, instead of you editing hundreds of profiles by hand.

Where to find a list of permission nodes

Every plugin documents its own permission nodes. Look for them in:

  • The plugin's documentation on the developer's website (e.g. wiki.luckperms.net, essentialsx.net)
  • The plugin.yml file inside the .jar file (a ZIP archive), in the permissions: section
  • Sites like luckperms.net/wiki or the plugin's page on SpigotMC

The OP system: why not to use it on a serious server

The /op nick command gives a player operator status, and that's where the trouble starts. A player with OP has literally every permission, with no exceptions. They can:

  • Ban other admins
  • Run WorldEdit commands across the whole map
  • Run debug commands from the server panel
  • Switch to Creative mode and take any items they want
  • Delete the entire map with the Multiverse /mv delete command

On a small server with friends, that may be fine. On a server with hundreds of players and moderators you don't fully trust, it's a recipe for disaster.

The right approach: OP only for the server owner, and every other rank set up through LuckPerms. Even the head admin should have precisely defined permissions, not free access to everything.

The principle of least privilege: Each rank should have only the permissions it actually needs. A moderator doesn't need WorldEdit. A builder doesn't need /ban. The fewer permissions, the lower the risk of abuse, whether through malice or an honest mistake.

LuckPerms: installation and first steps

LuckPerms is the de facto standard among Minecraft permissions plugins. It replaced older solutions such as PermissionsEx and GroupManager and is actively developed. It supports Paper, Spigot, Fabric, Forge and even proxies (Velocity, BungeeCord).

Installation

  1. Download LuckPerms from luckperms.net, choosing the version that matches your server (Paper/Spigot/Velocity etc.)
  2. Put the .jar file in the plugins/ folder
  3. Restart the server (or use /reload confirm if you have to)
  4. LuckPerms creates a plugins/LuckPerms/ folder with a config file

Basic storage

By default, LuckPerms stores its data in H2 files (a local database). That's enough for small servers. Bigger setups should consider MySQL or MariaDB, which you configure in config.yml under storage-method. On a BungeeCord/Velocity network with several servers, a shared MySQL database is essential so that permissions stay in sync across servers.

First commands after installing

Log in to the server and check that the plugin works:

  • /lp info - version and status
  • /lp user your_nick info - your permission profile
  • /lp group default info - the default group (which everyone belongs to)

By default, all players belong to the default group. That's your starting point for configuration.

Creating ranks: creategroup

In LuckPerms, a rank is a group. You create one with this command:

  • /lp creategroup <name> - e.g. /lp creategroup vip

Write group names in lowercase, without spaces or special characters. The display name (prefix) can contain any characters; more on that in a moment.

A typical rank hierarchy on a survival server

An example structure from lowest to highest:

  1. default - unregistered and new players (minimal permissions)
  2. player - players who have registered/logged in
  3. vip - a paid rank or one earned through activity
  4. svip - Senior VIP, extended perks
  5. helper - volunteers who help players
  6. moderator - moderators with ban/mute permissions
  7. admin - administrators with full access to the configuration
  8. owner - the server owner (optional; the owner can just have OP)

Creating all the groups:

  • /lp creategroup default
  • /lp creategroup player
  • /lp creategroup vip
  • /lp creategroup svip
  • /lp creategroup helper
  • /lp creategroup moderator
  • /lp creategroup admin

Group weight

Every group has a weight, which sets its priority when a prefix is displayed. Give higher ranks a higher weight:

  • /lp group vip meta setweight 10
  • /lp group moderator meta setweight 50
  • /lp group admin meta setweight 90

Weight matters when a player belongs to several groups at once: the system shows the prefix of the group with the highest weight.

Adding permissions to groups

The basic command is /lp group <name> permission set <node> <true/false>.

Examples for the player group

  • /lp group player permission set essentials.home true - setting a home (/home)
  • /lp group player permission set essentials.tpa true - teleporting to a player (/tpa)
  • /lp group player permission set essentials.spawn true - returning to spawn
  • /lp group player permission set essentials.kit true - kits

Examples for the moderator group

  • /lp group moderator permission set essentials.ban true
  • /lp group moderator permission set essentials.kick true
  • /lp group moderator permission set essentials.mute true
  • /lp group moderator permission set essentials.tempban true
  • /lp group moderator permission set essentials.vanish true

Wildcards: permissions in bulk

Instead of adding every permission one by one, you can use a wildcard (*) for an entire plugin:

  • /lp group admin permission set essentials.* true - all EssentialsX commands
  • /lp group admin permission set worldedit.* true - full WorldEdit

Use wildcards carefully: * covers every node, including dangerous ones (for example, essentials.sudo lets someone run commands as another player).

Negating permissions

You can take away a specific permission by setting it to false. This is useful when you give a group a wildcard but want to block one particular permission:

  • /lp group moderator permission set essentials.sudo false - blocks sudo despite the wildcard

A negated permission takes priority over a positive one at the same level of the hierarchy.

Rank inheritance

Inheritance is one of the most powerful features of LuckPerms. Instead of copying permissions from one group to another, a lower rank inherits the permissions of a higher one (or the other way around, depending on your setup).

The right approach: higher ranks inherit from lower ones. The moderator inherits from the player, so it automatically has the player's permissions plus its own extra ones.

Setting up inheritance

  • /lp group vip parent add player - VIP inherits from player
  • /lp group svip parent add vip - SVIP inherits from VIP (and, through VIP, from player)
  • /lp group moderator parent add player - moderator inherits from player
  • /lp group admin parent add moderator - admin inherits from moderator

With this setup, admin automatically has the permissions of moderator, player and every group in the inheritance chain. Changing the permissions of the player group instantly affects VIP, SVIP, moderator and admin.

Note: Don't create inheritance loops (A inherits from B, B inherits from A). LuckPerms will detect it and report an error, but it's better to avoid the situation from the start.

Giving a player a rank

To assign a player to a group:

  • /lp user Steve parent set vip - sets the VIP rank (removes the previous rank)
  • /lp user Steve parent add moderator - adds a rank without removing the previous one
  • /lp user Steve parent remove vip - removes a rank

You can also give a rank for a set time:

  • /lp user Steve parent addtemp vip 30d - VIP rank for 30 days

Chat prefixes and suffixes

A prefix is text shown before a player's name in chat and on the player list (TAB). A suffix appears after the name. LuckPerms stores prefixes as group metadata, but actually displaying them requires a chat plugin.

Setting a group prefix

  • /lp group vip meta setprefix "&6[VIP] " - a gold [VIP] prefix
  • /lp group moderator meta setprefix "&c[MOD] " - a red [MOD]
  • /lp group admin meta setprefix "&4[ADMIN] " - a dark red [ADMIN]

The color codes are the standard Minecraft codes: &a green, &b aqua, &c red, &6 gold, &e yellow, &f white. If your server supports MiniMessage (Paper 1.16+), you can use <gold>, <red>, <gradient:#ff0000:#0000ff> and so on.

Chat and TAB plugins

LuckPerms stores the prefixes, but you need a separate plugin to display them. Popular options:

  • TAB - shows prefixes on the player list (Tab key) and above players' heads, highly configurable
  • EssentialsX Chat - a chat format with prefixes, part of EssentialsX
  • LPC (LuckPerms Chat) - a lightweight chat plugin made specifically for LuckPerms
  • DeluxeChat - advanced chat formatting with PlaceholderAPI

To set up EssentialsX Chat, find the chat section in the EssentialsX config.yml file and set the format:

  • format: '{DISPLAYNAME}&f: {MESSAGE}' - uses the display name, which EssentialsX takes from the LuckPerms prefixes

Contexts (world, server)

Contexts let you grant permissions or ranks only under certain conditions: in a specific world, on a specific server of a network or for a set time. It's an advanced feature, but extremely useful on multi-world servers.

World context

The player has the VIP rank only in the survival world:

  • /lp user Steve parent add vip world=survival

A permission that's active only in a specific world:

  • /lp group moderator permission set worldedit.* true world=creative - WorldEdit only in the creative world

Server context (BungeeCord/Velocity)

On a server network, you can grant permissions on one specific server only:

  • /lp user Steve parent add admin server=lobby - admin only on the lobby

This requires setting server in LuckPerms on every backend server (the config.yml file, server option).

Contexts in the web editor

Contexts are easiest to configure in the LuckPerms web editor: the graphical interface shows them as tags next to each permission and lets you add or remove them with a click.

Tracks: promotion paths

A track is a LuckPerms feature that defines the order of ranks and lets players be promoted with a command, without an admin assigning ranks by hand. It works great for activity-based rank systems or for selling successive VIP tiers.

Creating a track

  • /lp createtrack players - creates a new track called "players"
  • /lp track players append player - adds the player rank as the first step
  • /lp track players append vip - VIP as the second
  • /lp track players append svip - SVIP as the third

To preview the track, use /lp track players info, which shows: player -> vip -> svip

Promoting and demoting a player

  • /lp user Steve promote players - promotes the player one step on the "players" track
  • /lp user Steve demote players - demotes the player one step

You can also let players promote themselves through a shop or a command, for example essentials.eco.buy combined with a shop that runs /lp user {player} promote players.

A staff track

It's worth creating a separate track for staff:

  • /lp createtrack staff
  • /lp track staff append helper
  • /lp track staff append moderator
  • /lp track staff append admin

Promotions on the staff track are usually manual: the server owner decides when someone gets a higher rank.

Web editor: the LuckPerms graphical interface

Typing dozens of commands into the console can get tedious. LuckPerms has a built-in web editor, a browser interface that lets you manage everything graphically.

How to open the web editor

  1. Type /lp editor in the console or in the server chat
  2. LuckPerms generates a unique link, e.g. https://luckperms.net/editor/abc123
  3. Open the link in a browser on your computer
  4. Make your changes in the graphical interface
  5. Click "Save": the editor generates a command to paste
  6. Paste the generated command into the server console, and LuckPerms applies all the changes

What you can do in the web editor

  • Browse and edit the permissions of all groups at once
  • Add and remove permission nodes with autocomplete
  • Set up inheritance (drag & drop)
  • Set prefixes and suffixes with a color preview
  • Manage tracks and contexts
  • View any player's profile

Security note: The web editor link is unique and expires after a set time. Don't share it with anyone: it gives full access to your server's permission configuration. Every session needs a new link generated with /lp editor.

Vault integration

Vault is an API that lets different plugins talk to each other, especially economy and permissions plugins. Most shops, reward plugins and ranking systems need Vault to read a player's groups or give ranks.

Installing Vault

  1. Download Vault from SpigotMC and put it in the plugins/ folder
  2. LuckPerms detects Vault automatically and registers itself as the permissions provider
  3. No extra configuration needed: Vault and LuckPerms work out of the box

How plugins use Vault with LuckPerms

Examples of integration through Vault:

  • Shops (ShopGUI+, UltraShop) - can add a player to the VIP group after a purchase
  • Quest plugins (Quests) - the reward for a quest is a rank-up
  • PlaceholderAPI - the %vault_rank% and %vault_prefix% placeholders in any plugin
  • DiscordSRV - syncs Minecraft ranks with Discord through Vault

Direct LuckPerms API integration

If you're writing your own plugin or script, LuckPerms has its own Java API (no Vault needed). It's more precise and faster, but you need to know how to program. The documentation is at luckperms.net/wiki/developer-api.

Tips for admins: common mistakes and good practices

Test as another player

Before you make your rank setup public, test it on a test account. Give yourself the player rank and check that a new player can do what they should, and can't do what they shouldn't. Many servers have too many or too few permissions in the default group.

Back up your configuration

The plugins/LuckPerms/ folder is your permission configuration. Back it up regularly. LuckPerms also has a built-in export:

  • /lp export backup.json.gz - exports the entire configuration to a single file
  • /lp import backup.json.gz - restores from the backup

Don't give OP to moderators

Back to basics: no moderator or admin (except the owner) should have OP status. If a moderator needs a new permission, add it to their group through LuckPerms. OP isn't "more permissions": it's literally no limits at all.

Weight vs. inheritance

Group weight (meta setweight) and inheritance are two different mechanisms. Weight only decides which prefix to show when a player has several ranks. Inheritance decides which permissions a player gets. You can have a high weight without inheritance and vice versa: the two settings are independent.

Use wildcards with care

The essentials.* wildcard includes, among others, essentials.sudo (run commands as another player), essentials.eco.give (give out currency) and essentials.createkit (create kits). Before using a wildcard, check the plugin's full list of nodes and think about whether all of them are safe for that rank.

Debugging permissions

If a player gets a "You don't have permission" message, check their effective permissions:

  • /lp user Steve permission check essentials.ban - whether the player has a specific permission (true/false/undefined)
  • /lp user Steve permission info - a list of all the player's permissions
  • /lp user Steve meta info - the player's prefixes, suffixes and meta
  • /lp verbose on - verbose mode: logs every permission check in real time (turn it off once you're done debugging!)

LuckPerms on a server network

With BungeeCord or Velocity, set up a shared database (MySQL/MariaDB) for all servers. The sync-minutes: 3 option in config.yml syncs changes between servers every 3 minutes. You can also force an immediate sync with /lp networksync.