LuckPerms Setup Guide — Minecraft Permissions for 2026

Download LuckPerms from the official page, drop the .jar into /plugins, restart. On first start, it creates the default configuration. Use '/lp editor' to open the web editor — the easiest way to manage permissions. The web editor generates a command you paste back into console to apply changes. Storage options: default is H2 (file-based) — good for single-server setups. For networks, use MySQL/MariaDB to share permissions across servers. Key config in config.yml: set 'server: global' if running multiple servers, or set specific server names for per-server permissions.

Create a hierarchy: default → member → trusted → moderator → admin → owner. Commands: '/lp creategroup member', '/lp creategroup moderator', etc. Set parent groups with: '/lp group member parent add default'. Inheritance flows down — default gets basic permissions, member inherits default + more, moderator inherits member, and so on. This structure means you only assign permissions to the lowest group that needs them.

Default group: 'essentials.*' limited (basic commands like /list, /msg, /tpa), 'minecraft.command.list', 'minecraft.command.help'. Set a rank above 'default' for 'trusted' group: add 'essentials.home.*', 'essentials.warp.*', 'essentials.sethome', 'essentials.setwarp', 'essentials.back', 'coreprotect.inspect' (for reporting grief). Moderator: 'essentials.kick', 'essentials.ban', 'essentials.jails', 'coreprotect.lookup', 'luckperms.*' limited. Admin: everything except 'op'. Use '/lp showtracks' to see built-in permission templates.

Contexts let you apply permissions based on conditions. Example: 'server=survival' gives fly only on creative server, 'world=spawn' prevents breaking blocks in spawn world, 'gamemode=creative' gives build permissions only in creative mode, 'day-of-week=saturday' gives double drops on weekends. Set contexts: '/lp group default permission set essentials.fly true server=creative'. Contexts keep your permission setup clean and prevent cross-server permission bleed in networks.

Tracks automate promotion through staff ranks. Create: '/lp createtrack staff'. Add groups in order: '/lp track staff append helper', '/lp track staff append moderator', '/lp track staff append admin'. Users promote via '/lp user <name> promote staff'. Each promotion can run commands: 'give-rank' sends chat announcement, 'set-group' promotes to next rank, 'demote' for reverse. Tracks ensure consistent promotion processes across your staff team.

Never give 'op' to anyone — use LuckPerms instead. OP bypasses all permission checks and is a security risk. Use '/lp user <name> info' to audit someone's effective permissions. Set up info nodes: '/lp group default permission set info.essentials.* true' gives players access to /info commands without /info admin. Regularly audit with '/lp audits' to see recent permission changes. Back up your LuckPerms data with backups.