
LuckPerms for Minecraft: groups, ranks and permissions
Create LuckPerms groups, grant specific permissions and verify player access without giving every member operator-level control.
LuckPerms assigns specific permissions to players and groups. A displayed rank and an actual permission are different: naming a group moderator does not automatically grant its intended commands.
This example targets an existing Paper server. Choose the LuckPerms build for your server implementation, back up its settings and data, and install it using the project’s instructions.
Define roles before granting access
Write down what regular players, event organisers and moderators should be able to do. Obtain permission nodes from each relevant plugin’s documentation. LuckPerms assigns access; it does not implement commands missing from the server.
Avoid granting * simply to remove an access error. A wildcard may authorise much more than the intended action. An operator account is also unsuitable for testing restricted access.
Create a group and add a player
Run this in-game with the required administrative permissions:
/lp creategroup moderation
/lp group moderation parent add default
/lp user PLAYERNAME parent add moderation
Replace PLAYERNAME with the account being configured. Server consoles generally omit the opening slash. Inheriting default retains the baseline group’s access.
The grant syntax is /lp group moderation permission set PERMISSION_NODE true. Replace PERMISSION_NODE with the exact node documented by the plugin. The placeholder is not a real permission you should copy literally.
Apply changes from the web editor
/lp editor produces a link to LuckPerms’ web editor. Change the intended group, then use the apply command generated by the editor. Editing a browser view alone does not establish that the running server received the changes.
Keep editor session links and apply commands within the administrator group. Record each permission and its purpose so access can be reviewed when someone leaves the team.
Test and remove permissions
Use a non-operator account, assign the group and try one permitted action plus one action that should remain unavailable. Repeat after reconnecting. If the outcome differs, inspect inherited groups, individual permissions and world or server contexts.
Remove the group with /lp user PLAYERNAME parent remove moderation. Remove an explicitly assigned node with the group’s permission unset command. Unsetting an explicit value differs from forcing false: another inherited group may still grant the permission.
Include permission storage in recovery plans
Back up LuckPerms’ storage, particularly when it uses an external database. Our mods and plugins guide explains extensions generally. Here, useful hosting features are access to the plugin, its storage and a reliable restoration procedure.
You can also compare the terms on our NitroServ profile.
Frequently asked questions
Does a prefix grant access?
Why does a removed permission still work?
Is MySQL required?
Continue with: back up plugin data, check Bedrock player access.
Sources and documentation: LuckPerms commands, LuckPerms inheritance, LuckPerms permissions.
Ready to launch your Minecraft server?
Here are the best Minecraft hosting deals right now, promo codes included. Still unsure? Our quiz finds the ideal host for you in under 2 minutes.
My box 4
Minestrator
Specifications
Compatible games
Features
- ✓Hébergement web inclus
- ✓DDoS Protection
- ✓Backups
Casual (budget)
Shockbyte
Specifications
Compatible games
Features
- ✓1GB RAM
- ✓Protection DDoS
- ✓Support 24/7
- ✓Setup instantané
Stone
GGServers
Specifications
Compatible games
Features
- ✓DDoS Protection