Direct answer

LuckPerms permissions should be assigned to groups, with user assignments used only when justified.

Recommended procedure

  1. Confirm LuckPerms is running on the intended backend or proxy. Use /lp editor to inspect existing groups and permission assignments.
  2. Create a test group such as /lp creategroup helper and grant a verified, narrow permission node, for example /lp group helper permission set example.permission true with your real plugin’s documented node.
  3. Add a test user with /lp user PlayerName parent add helper; use /lp user PlayerName parent info to review inheritance.

Why this matters

Plugins add another compatibility and permission layer. Use the plugin author's current documentation for commands, nodes, and configuration keys.

Important limitation: Velocity and Paper permission contexts are not automatically interchangeable. Record where LuckPerms is installed and how storage is shared.

How to verify the result

  • Test the granted command as the non-OP account and confirm a disallowed command remains blocked.

Version and compatibility notes

  • When a setting, command, or file name differs from this guide, stop and check the documentation for your exact Minecraft/server-software version instead of forcing an old example.

Official references

These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000