--- title: "LuckPerms Setup Guide | ZCraft Studios" description: "Set up LuckPerms ranks, prefixes, tracks and inheritance, avoid the default group trap, and debug permissions that do not work." url: "https://www.zcraftstudios.com/blog/luckperms-ranks-setup-guide" updated: "2026-10-20T07:16:50.972429+00:00" source: "ZCraft Studios" --- > Site index for AI agents: https://www.zcraftstudios.com/llms.txt (full reference: https://www.zcraftstudios.com/llms-full.txt). Every page is available as Markdown by adding `.md` to its URL or sending `Accept: text/markdown`. 1. [Home](https://www.zcraftstudios.com/) 2. [Blog](https://www.zcraftstudios.com/blog) 3. LuckPerms Setup Guide: Ranks, Prefixes, Tracks and Debugging [ All posts](https://www.zcraftstudios.com/blog) # LuckPerms Setup Guide: Ranks, Prefixes, Tracks and Debugging ZCraft StudiosOct 3, 2026Updated Oct 20, 2026 Set up LuckPerms ranks, prefixes, tracks and inheritance, avoid the default group trap, and debug permissions that do not work. ## In this guide - [The three ideas you need](#the-three-ideas-you-need) - [Install and storage](#install-and-storage) - [Plan the layout before typing commands](#plan-the-layout-before-typing-commands) - [Inheritance, and the default-group trap](#inheritance-and-the-default-group-trap) - [Giving permissions](#giving-permissions) - [Prefixes, and why they don't show up](#prefixes-and-why-they-dont-show-up) - [Tracks: promotions without remembering the ladder](#tracks-promotions-without-remembering-the-ladder) - [Temporary ranks and contexts](#temporary-ranks-and-contexts) - [Debugging a permission that doesn't work](#debugging-a-permission-that-doesnt-work) - [The web editor and backups](#the-web-editor-and-backups) - [The mistakes worth avoiding](#the-mistakes-worth-avoiding) - [Official documentation and links](#official-documentation-and-links) - [Diagnose a permission that does not apply](#diagnose-a-permission-that-does-not-apply) ## LuckPerms Setup Guide: Ranks, Prefixes, Tracks and Debugging Most LuckPerms trouble comes from the first hour of setup. A rank layout that works for three ranks falls apart at eight, and a prefix that never shows up in chat sends people searching for a bug that isn't there. This guide builds a structure you can grow, then covers the debugging commands for when a permission still doesn't behave. ## The three ideas you need - **Permission nodes** are strings like `essentials.fly`. A plugin checks whether the player has the node. - **Groups** hold nodes. A player gets nodes by being in a group, and groups can inherit from other groups. - **Contexts** limit a node to one server or world, so a permission can apply in `survival` but not in `lobby`. Give permissions to groups, not individual players. When you give a node to one player directly, you will forget it exists, and so will every other admin. ## Install and storage [LuckPermsA permissions plugin/mod for Minecraft servers.On Modrinth ](https://modrinth.com/plugin/luckperms) Download LuckPerms from the project linked above. Check the supported Minecraft version, server platform, Java requirement and dependencies for the selected release. 1. Back up the server files and any plugin database. 2. Stop the server before changing JAR files. Put the compatible plugin build and its required dependencies in the correct plugin folder. 3. Start the server and read the startup log. Resolve missing dependencies or version errors before editing the generated configuration. 4. Stop the server, make one small configuration change, then restart and test it with a non-operator account. Confirm LuckPerms loads after a clean restart. Test the feature you need with an ordinary player account before adding optional integrations. ## Plan the layout before typing commands Keep donor ranks and staff ranks as separate ladders. Players who buy a rank should never end up inheriting staff permissions. A layout that works: - `default` for everyone, weight 0 - `supporter`, weight 100 - `helper`, weight 200 - `mod`, weight 300 - `admin`, weight 400 Space the weights out by 100\. When you need a rank between `helper` and `mod` in a year, you can add it without renumbering. Weight decides which group wins when a player is in several and their values conflict, such as two different prefixes. The higher weight wins. ``` /lp creategroup supporter /lp creategroup helper /lp creategroup mod /lp creategroup admin /lp group supporter setweight 100 /lp group helper setweight 200 /lp group mod setweight 300 /lp group admin setweight 400 ``` ## Inheritance, and the default-group trap Here is the one that catches most people. When you set a player's rank with `parent set`, it replaces their old group, including `default`. If `mod` doesn't inherit `default` somewhere up its chain, a promoted player loses the basic permissions everyone else has. Chain your staff groups so each inherits the one below, and the bottom one inherits `default`: ``` /lp group helper parent add default /lp group mod parent add helper /lp group admin parent add mod /lp group supporter parent add default ``` Now a node added to `default` reaches everyone, and a node added to `mod` reaches mods and admins. Put each permission in the lowest group that should have it. ## Giving permissions ``` /lp group default permission set essentials.spawn true /lp group helper permission set essentials.kick true /lp group mod permission set essentials.mute true ``` Two warnings. Avoid the `*` wildcard on anything except a group you would trust with the console, because it grants every node, including ones added by plugins you install next year. And remember that `false` is an explicit deny, which beats an inherited `true`. Leaving a node unset is not the same as setting it to false. LuckPerms accepts any string as a node. If you mistype one, nothing warns you and the permission simply never applies. Always confirm the exact node in the plugin's own documentation, or find it with the verbose tool below. ## Prefixes, and why they don't show up ``` /lp group admin meta addprefix 100 "&c[Admin] " /lp group mod meta addprefix 100 "&a[Mod] " ``` The number is the prefix priority. When a player has several prefixes, the highest priority one is displayed. LuckPerms stores the prefix but does not format chat itself. You need something that reads it: - **EssentialsX Chat** with `{PREFIX}` in its chat format, reading from Vault. - **PlaceholderAPI**, where `%luckperms_prefix%` can go into TAB, a scoreboard or a chat plugin. If a prefix is set but absent from chat, the cause is almost always the missing second half of this setup. ## Tracks: promotions without remembering the ladder A track is an ordered list of groups, so staff can be promoted with one command: ``` /lp createtrack staff /lp track staff append helper /lp track staff append mod /lp track staff append admin /lp user Steve promote staff /lp user Steve demote staff ``` Promoting a player who isn't on the track yet starts them at its first group. Tracks are also the clean way to keep a trial period honest, since you can demote in one step. ## Temporary ranks and contexts ``` /lp user Steve parent addtemp supporter 30d /lp user Steve permission settemp essentials.fly true 1h /lp group supporter permission set essentials.fly true server=survival ``` The first two expire on their own. The third applies the permission only on the server named `survival`, which is how you keep a lobby from handing out survival perks. ## Debugging a permission that doesn't work Work through these in order: ``` /lp user Steve permission check essentials.fly /lp user Steve info /lp verbose on ``` `permission check` tells you whether Steve has the node and which group it came from. `info` lists his groups and their weights. With verbose on, trigger the action in game and LuckPerms prints every permission check as the plugin makes it, which shows you the real node the plugin is asking about. Turn it off with `/lp verbose off`. This is also how you catch the mistyped node problem above. ## The web editor and backups `/lp editor` gives you a link to a browser editor, which is much easier than commands once you have more than a few groups. Changes are not live until you save in the editor and then run the `/lp applyedits` command it shows you in game. Back up before big changes: ``` /lp export before-rank-rework /lp import before-rank-rework ``` Export writes a file in the LuckPerms folder, and import restores from it. ## The mistakes worth avoiding - Giving staff ranks to people through op instead of through a group - Using `*` on a group that isn't the top one - Forgetting that `parent set` removes `default` - Setting a prefix and never installing anything that displays it - Editing individual players instead of groups - Trusting a node name you typed from memory without checking it with `verbose` Get the structure right once, and adding a new rank later is two commands. ## Official documentation and links - [LuckPerms documentation](https://luckperms.net/wiki/Home) - [Designing a Minecraft Server Rank and Permission System](https://www.zcraftstudios.com/blog/minecraft-server-rank-permission-system) [LuckPermsA permissions plugin/mod for Minecraft servers.On Modrinth ](https://modrinth.com/plugin/luckperms) ## Diagnose a permission that does not apply Start with `/lp verbose on` during a controlled test, reproduce one denied command with a non-OP account, and inspect the recorded permission node and context. Turn verbose off after testing. If a prefix is missing, check whether the chat or TAB plugin can actually render LuckPerms metadata; setting a prefix alone does not guarantee it appears everywhere. Avoid adding the wildcard permission `*` just to silence permission errors. Resolve the precise node and inheritance instead. ## Resources for this topic - [Premium TAB & Scoreboard Config | Minecraft Tablist and Scoreboard UI](https://www.zcraftstudios.com/products/premium-tab-scoreboard-configuration) - [EternalTags Config | Premium Minecraft Chat Tags GUI (100+ Tags)](https://www.zcraftstudios.com/products/eternaltags-clean-modern-tags-gui) ## Continue reading - [Designing a Minecraft Server Rank and Permission System](https://www.zcraftstudios.com/blog/minecraft-server-rank-permission-system) - [EssentialsX Commands Every Admin Should Know](https://www.zcraftstudios.com/blog/essentialsx-commands-cheat-sheet) - [LuckPerms Config, Placeholders and Verbose Guide](https://www.zcraftstudios.com/blog/luckperms-config-placeholders-verbose-guide) - [LuckPerms vs PermissionsEx: Why LuckPerms Won](https://www.zcraftstudios.com/blog/luckperms-vs-permissionsex-comparison) [ Previous guide Minecraft Server vs. Realms: Which One Should You Use](https://www.zcraftstudios.com/blog/minecraft-server-vs-realms)[ Next guide How to Create a Minecraft Server: Step-by-Step Guide (Paper)](https://www.zcraftstudios.com/blog/how-to-create-a-minecraft-server-walkthrough)