LuckPerms

LuckPerms decides who can do what on the server. When a player types a command or opens a chest, the plugin handling it asks LuckPerms for permission (a node such as luckperms.user.info) and gets a yes or no answer. All rules are in one place — not scattered across the configurations of other plugins.

The basic idea: permissions are not given to a player, but to a group — and a player is a member of groups. On a typical server, a few groups are therefore enough (player, VIP, moderator, admin), and players simply move between them. When the rules change, you edit one group and it applies to everyone.

Groups can inherit: a moderator can inherit from player and add only their own. A denial (false) takes precedence only where it is as specific as the permission. If you're not sure which node applies, the command /lp info lists what the player can do and where they inherited it from, and /lp verbose on uk shows live which permission is currently being checked.

Permissions can also be set temporarily (a temporary VIP for 30 days) or only in a certain world (they can build only in the creative world). LuckPerms can also handle multiple servers at once when you connect them through a database — useful when you have a lobby, survival, and skyblock and want one set of permissions for all.

The fastest way to set it up is the web editor: /lp editor vyp writes out a link, you click through groups and permissions in your browser, and save them back into the game. Without a restart and without manually rewriting files.

Most servers use it — also because many other plugins depend on it, as they need to know who is a moderator and who is a regular player.

1. Check what the server runs on (/version v konzoli). LuckPerms has versions for Paper/Spigot, but also for Velocity, BungeeCord, Fabric, and Forge — choose the one that matches your server type.
2. Open luckperms.net and in the Download section choose the server type and the latest version.
3. Upload the downloaded .jar to the plugins folder on the server.
4. Restart the server. Avoid the /reload command — it can mess up even plugins that otherwise work correctly.
5. Check the console: a line with the LuckPerms version and information about which storage it saves data to must appear (the default is files in plugins/LuckPerms).
6. Write /lp info — it will output the version and storage status. If a report about missing data appears, run /lp sync.
7. Create basic groups: /lp creategroup hrac, /lp creategroup vip, /lp creategroup moderator, /lp creategroup admin.
8. Set up inheritance so permissions aren't duplicated: /lp group vip parent add hrac (and likewise for other groups).
9. Give yourself all permissions: /lp user permission set luckperms.* true. Without that you won't get access to permission settings.
10. Add yourself to the admin group: /lp user parent add admin.
11. Set the default group for new players: /lp default group set hrac. KaEvery new player automatically falls into it.
12. Open /lp editor a dokonfiguruj zbytek. Po ulo and verify that the permissions have taken effect: /lp info .
13. Before your first big change, make a backup: /lp export zaloha.json (saves the complete permission setup to a file).

Give permissions to groups, not individual players. Players keep growing, groups stay few — when you change the rules, you’ll save hours.
Set up your own group and don’t edit permissions directly for yourself: if you accidentally deny yourself access, you’ll lock yourself out of your own server. Keep the console or a second account on hand in case of emergency.
Watch out for false: a deny only wins where it is just as specific as the allow. If group hrac denies something and VIP allows it, the priority (weight) of the groups decides — not the order in which you added them.
Prefixes and ranks belong in meta (meta setprefix), not in permissions. The priority number decides which prefix shows in chat when a player has multiple ranks stacked on top of each other.
Before a bigger change, save a backup (/lp export zaloha.json) and also back up the plugins/LuckPerms folder. Permissions are the hardest thing to explain after the fact.
When permissions “don’t propagate”, /lp sync. Kdy helps. If the plugin after restart acts like it can’t do anything, the wrong version for the given server type (Paper vs. Velocity) is usually to blame.