LuckPerms Mod FAQ

Use the command to set a permission node directly on the player, like setting a node to true. You can also add them to a group that already has the permission, which is usually the cleaner approach.

A permission node is a single string that grants or denies one specific ability, while a group is a container of nodes you can assign to many players at once. Groups let you manage permissions in bulk instead of editing every player individually.

Use the info command on the player to see their assigned nodes, their groups, and any inherited permissions. This is the fastest way to figure out why a player can or can't do something.

Most changes apply immediately, but some plugins cache permissions and need a reload or a re-login. Also check that no other group or node is explicitly denying the permission, since a deny overrides a grant.

Set the child group as a parent of the other group, so the child picks up all of the parent's permissions. This lets you build a hierarchy like default, then member, then moderator, then admin.

Setting a node to false explicitly denies it, which overrides any group that grants it. This is useful for removing one specific ability from a player without pulling them out of their group.

Apply the permission with a context that targets that world, so it only counts while the player is there. Contexts can also target servers, gamemodes, and other conditions.

Configure the default group so every player automatically joins it on first login. Then give that group the basic permissions you want everyone to have.

LuckPerms is a full replacement for other permission plugins, so you should remove the old one to avoid conflicts. Most plugins that use permissions will work with it out of the box.

LuckPerms is designed to be lightweight and caches permission lookups, so it has minimal impact on a normal server. Performance issues usually come from other plugins or from extremely large permission setups.