LuckPerms Permissions Builder - Groups, Prefixes and Commands

Lay out your ranks with inheritance, weights, prefixes and per-world permissions, and get the exact /lp commands to paste in, or the group files LuckPerms writes to yaml-storage.

Groups

Higher weight wins when a player is in several groups. The default group is called default and every player is in it.

Group settings

Inherits from

Permissions

=

Start typing a vanilla command name and the minecraft.command node fills in. Plugin nodes (essentials.fly, worldedit.wand) go in as typed. A context limits the node to one server, world, gamemode or dimension.

/lp creategroup mod 50 Moderator
/lp creategroup admin 100 Admin
/lp group default permission set minecraft.command.help true
/lp group default permission set minecraft.command.msg true
/lp group mod parent add default
/lp group mod meta setprefix 50 "&a[Mod] "
/lp group mod permission set minecraft.command.kick true
/lp group mod permission set minecraft.command.ban true
/lp group mod permission set minecraft.command.teleport true
/lp group mod permission set minecraft.command.gamemode true world=creative
/lp group admin parent add mod
/lp group admin meta setprefix 100 "&c[Admin] "
/lp group admin permission set * true

Paste these into the console or chat as an operator. Temporary permissions use settemp with the duration you typed.

A rank ladder that works

Three groups cover most servers: default for everyone, mod for the people who kick and ban, admin for the people who run the server. Make each one inherit the one below it, give them rising weights, and put only the extra permissions on each rank rather than repeating the lot.

Contexts are what make LuckPerms more than a list. A permission with world=creative on it only applies in that world, so a builder rank can have /gamemode there and nowhere else, and server=lobby keeps a lobby permission off the survival server behind the same proxy. The builder writes each context as the key=value pair the command expects, and the YAML form the plugin writes to disk.

Commands or files

The command output is the safe route: it works with every storage backend and the plugin validates each line. The YAML file is for yaml storage only, and it is the exact shape the plugin writes itself, so a group you build here and drop into yaml-storage/groups reads back cleanly. Weight and display name are stored as weight.N and displayname.Name nodes inside the permissions list, which is how the plugin does it, not a quirk of this page. Expiring permissions are the one thing the file cannot carry from here, because the plugin stores them as a unix timestamp; use settemp for those.

Frequently Asked Questions

How do I give a group a permission in LuckPerms?

/lp group <group> permission set <node> true. Add a context on the end to limit it, for example world=world_nether or server=survival, and use permission unset to remove it. Setting a node to false takes it away even when a parent group grants it, which is how you carve exceptions out of an inherited rank.

What is the permission node for a vanilla command on Paper?

minecraft.command.<name>, for example minecraft.command.gamemode or minecraft.command.teleport. Players already have help, list, me, msg, teammsg and trigger by default; everything else is op-only until a permissions plugin grants it. The builder's node field lists all of them as you type.

How do group weights work?

When a player is in more than one group, LuckPerms uses the weights to decide which group's prefix, suffix and meta win: higher weight beats lower. Set it on creation with /lp creategroup <name> <weight> or later with /lp group <name> setweight <weight>. Give admin the highest number and default the lowest.

How do I make a rank inherit another rank?

/lp group <child> parent add <parent>. The child gets every permission of the parent, and of the parent's parents, so a typical ladder is admin inherits mod, mod inherits default. Use parent set instead of add to replace every existing parent at once.

How do I set a prefix with colour in LuckPerms?

/lp group <group> meta setprefix <priority> "&c[Admin] ". The & codes are standard chat colours, the trailing space keeps the prefix off the name, and the priority decides which prefix shows when several apply (higher wins). A chat plugin or a placeholder such as %luckperms_prefix% has to display it; LuckPerms itself only stores it.

Can I edit the YAML file instead of using commands?

Yes, if your storage method is yaml: the files live in plugins/LuckPerms/yaml-storage/groups/. Edit with the server stopped, or run /lp sync afterwards so the running plugin reloads them. For MySQL, H2 or any other storage the files do not exist, so paste the commands instead, or use /lp editor for the web editor.

LuckPerms Permissions Builder - Groups, Prefixes and /lp Commands