A rank has two separate jobs: deciding what someone can do and deciding how the rank is displayed. When those are mixed together, it is easy to give a decorative “helper” role far more access than intended. Build a small permission model first.
Create a group, assign only the required nodes, add the player and test as a non-operator. Prefix display usually needs a compatible chat or formatting integration.
Prepare a safe place to test
Install the LuckPerms build for your platform and read the startup log. Back up its data using the appropriate method for the storage backend you use. Start with a test player and one group rather than replacing the entire live hierarchy at once.
Keep administrator permissions and web-editor sessions private. Do not give ordinary staff wildcard access just to make one missing command work.
Create and assign a small group
These commands are an example for a group named member and a player named Alex. Replace Alex with the intended account. In a panel console, omit the initial slash if the console expects bare commands.
/lp creategroup member
/lp user Alex parent add member
/lp user Alex info
Using parent add keeps other memberships; changing a player’s complete parent set can have different consequences. Inspect existing groups before modifying a real account.
Add a permission that an installed plugin uses
Permission nodes are defined by the plugin providing the feature. For example, if the installed plugin’s documentation specifies essentials.home, the following grants that node to member. Verify the exact node and default behavior for your plugin version before using the example.
/lp group member permission set essentials.home true
A misspelled node can be stored successfully without making a command work. If access is unexpected, investigate inheritance, explicit denials and world/server contexts.
Add a prefix and apply editor changes carefully
A simple prefix example is shown below. A chat/display plugin must actually read the metadata for it to appear where you expect. Giving a group a prefix does not make it an administrator.
/lp group member meta setprefix 100 "&7[Member] "
/lp editor
The editor link opens a permission-editing workflow. Keep it private, inspect the changes and use the save/apply command it generates for your session; do not reuse an unrelated code from a tutorial.
Verify the role with a real account
Join as the test player without operator privileges. Check the intended command and confirm that administrative commands remain unavailable. Test in the actual world and server context, especially across a proxy network.
Add one capability at a time to a helper or moderator role. Keep a short role description explaining what it may do and who approved it. This makes the next permission problem easier to diagnose than a collection of unexplained wildcard grants.
Before you finish
- Back up the current permission data.
- Create a small group and inspect memberships.
- Use permission nodes from installed-plugin documentation.
- Test display and privileges separately without operator access.
Common questions
Why does my prefix not appear in chat?
Check the formatting plugin and its LuckPerms or metadata integration. Storing a prefix does not by itself replace the chat renderer.
Why can the owner use a command but a player cannot?
Operator status and inherited permissions can bypass the situation you are trying to test. Use a non-operator test account and inspect its effective permissions.
Official documentation
Commands and configuration depend on your installed software version. Check its current documentation, keep a backup and test one change at a time.
Build a setup that fits your server
Compare monthly allocations and CPU tiers, or use the plan finder for a starting estimate.
Compare Minecraft hosting plans Find a plan