Direct answer
Permission nodes determine which plugin commands or features players may use. A permissions manager such as LuckPerms assigns those nodes to users and groups; being OP is not the same as managing every plugin permission.
Step-by-step procedure
- Find the exact node in the plugin’s documentation or the command’s permission error. Do not invent a node from the command name.
- Grant the node to a narrowly scoped group or user with your permissions plugin; avoid broad
*grants. - Test as a normal player and as an administrator, including commands with similar aliases or plugin namespaces.
- If the command still fails, inspect permission context, group inheritance, world/server scope and proxy versus backend placement.
Common mistakes and trade-offs
A permission plugin installed only on Velocity does not automatically manage a Paper backend. Permissions can also be overridden by a plugin’s own configuration.
How to verify it worked
Remove the temporary test grant and verify the normal account loses access while the intended role retains it.
Version and platform differences
Paper’s plugin.yml supports plugin-declared defaults, but permissions may also be registered dynamically; exact nodes vary by plugin build.
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.
Related guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.