LuckPerms Permissions Calculator
Browse common permission nodes from Essentials, WorldGuard, Minecraft and LuckPerms. Toggle permissions on and off, then copy the resulting LuckPerms commands.
Essentials
WorldGuard
Minecraft Commands
LuckPerms
Embed This Tool
Put the permissions calculator on your own site or server wiki.
<iframe src="https://tools.astroworldmc.com/embed/permissions-calculator" width="700" height="700" frameborder="0" style="border:none;border-radius:12px;" loading="lazy" title="Permissions Calculator"></iframe>
How to build a LuckPerms group
Name the group
The name is used in every command the page writes, so a default group produces different lines than a moderator group.
Search the nodes
Each node is listed with what it actually allows, and the search narrows the list by plugin or by word.
Tick what the group gets
The counter keeps track of how many nodes are selected while you work through the list.
Copy the commands
The output is a block of LuckPerms commands, ready to paste straight into the console.
How It Works
Generate LuckPerms permission nodes visually.
71 nodes published by EssentialsX, WorldGuard and LuckPermsPage updated
How to Use the Permissions Calculator
LuckPerms is the most widely used permissions plugin for Minecraft Java Edition servers. It manages which commands and features each player group can access by assigning permission nodes. Each node follows a dot-separated naming convention like essentials.home or worldguard.region.claim. Setting a node to true grants that permission, while false denies it.
This tool provides a browsable list of common permission nodes organized by plugin. Enter your group name at the top (such as "default", "vip" or "admin"), then check the permissions you want to grant. The tool generates the corresponding LuckPerms commands at the bottom. You can copy the entire block and paste it into your server console or a script file. Nodes decide what a group may do once it is on the server; who may connect at all sits in server.properties, which the server.properties generator writes.
Common Use Cases
New server owners setting up ranks for the first time use this tool to understand which permissions are available and build their rank structure from scratch. Instead of reading through plugin documentation pages one by one, all the common nodes are listed here with short descriptions. The search filter helps you quickly find specific permissions across all plugins.
Experienced administrators use this tool when adding a new plugin and needing to set up its permissions quickly, or when auditing existing groups to check which nodes are assigned. The generated commands follow the standard LuckPerms command format and can be pasted directly into the server console. Who may connect at all is a different file, kept by the whitelist manager, and LuckPerms files each user under a UUID rather than a name, which the UUID lookup resolves.
How a permission node resolves
| Shape of a node | Dot separated and lowercase, plugin first, then command, then the specific action. |
|---|---|
| Wildcards | A node ending in a dot and a star grants everything below it. It also grants anything a future update adds below it, which is the part people forget. |
| Negation | A node set to false denies. Denying one node under a wildcard is the normal way to hand out a group of permissions minus one. |
| Specificity | The more specific node wins over the wildcard, no matter which order they were added in. |
| Inheritance | A group takes everything from its parents. A permission set directly on a player beats anything inherited. |
| Contexts | A node can be limited to one world or one server in a network, so the same group behaves differently per world without a second group. |
None of these 71 nodes belong to Minecraft. They are the permission strings EssentialsX, WorldGuard and LuckPerms publish for themselves, next to the command nodes a vanilla server exposes, and the lp lines beside them are LuckPerms syntax that needs the plugin installed.
What a wildcard buys and what it costs, counted on these 71 nodes
Ticking boxes here produces one lp line per node, so the list length is the command count. Running the same 71 nodes through their own dots shows exactly how much a star saves and how much it hands over unread.
commands = one per node you ticka star at a prefix grants every node below that prefix, and nothing at the prefix itselfreach of a star = how many of the 71 sit under itFour of the 71 are a node and a parent at once: essentials.home, essentials.sethome, worldguard.region.remove and worldguard.region.flag. A star on those grants what sits below them and not the node itself, so a rank built on essentials.home.* can teleport to somebody else's home and still cannot run /home. That single case is worth more than the 67 saved lines.
Frequently Asked Questions
Questions about permissions
Why does a player still have a permission I removed?
Usually operator status. An op passes most checks before the permission plugin is ever asked, which is why permission setups start by taking op away and granting the nodes instead.
Is a star wildcard safe to give a moderator?
No. It grants every node the plugin has now and every node it gains later, including ones written after your setup. Grant the branches you mean and negate the rest.
How do I give a group everything except one command?
Grant the wildcard for the branch and add the single node set to false. The more specific node wins, so the exception holds without touching the rest.
Can a permission apply in one world only?
Yes, through a context. That is how a creative world can hand out build permissions that do not follow the player back to survival.
