Skip to main content

Create Minecraft ranks and inheritance with LuckPerms

LuckPerms controls which actions Minecraft players may perform. A rank is a group of permissions; its visible chat prefix is a separate presentation setting. Design access first, then add colours or labels. A moderator should not need full administrator access merely to receive a staff title.

Prepare a small permission plan

Install the LuckPerms build for your server platform using the plugin installation guide. Record whether you are configuring a Paper backend or a proxy: their permission stores can differ. Keep a backup of the existing LuckPerms configuration and its database before changing an established rank structure.

List what each role needs. Start with ordinary players and one helper role rather than recreating an entire hierarchy at once. Read the relevant plugin's permission reference for each command. A permission node is not necessarily the same as its command name, and a group name alone grants no command access.

Create and assign a limited group

These examples are for a Paper server's Console, without leading slashes. Replace PlayerName with the intended player. They create a helper group with access to the vanilla kick command:

lp creategroup helper
lp group helper permission set minecraft.command.kick true
lp user PlayerName parent add helper

Run one line at a time and read the response. Check that the player and group are correct before assignment. Do not use wildcard permissions or operator status as a shortcut to make a single command work.

Use parent add when you want to retain existing memberships. The parent set operation can remove existing parents in the selected context. If a player already has a paid role or another staff responsibility, replacing their memberships can remove access unexpectedly.

Use inheritance deliberately

To make an existing moderator group inherit helper permissions, use lp group moderator parent add helper. The direction matters: moderator gains helper access. Giving helper the moderator parent would grant the more powerful role to helpers instead.

Check inherited permissions as well as directly assigned ones. A permission scoped to one world or server is different from an unrestricted permission. Record contexts so that an allowance intended for a build world does not silently apply to the survival world.

Review and apply editor changes

Open a focused session using lp group helper editor. Keep the editor URL private because it exposes your permission structure and editing session. Review the target group, permission values, parents and contexts before saving. The editor supplies a command to apply the saved changes; saving the browser page alone does not complete the server-side update.

Test with an ordinary, non-operator account that has the intended memberships. Check both an allowed command and a command the role must not use. If access is wrong, inspect inherited groups and contexts before granting more permissions. Keep your console available while testing, and retain the previous data until the new permissions have been checked.

Further reading

No comments to display