Direct answer
Audit plugin permissions using the actual permission nodes and contexts exposed by each plugin, not only a list of administrators.
Recommended procedure
- Gather plugin documentation for every command and bypass node used by staff; map each node to the correct LuckPerms group.
- Review wildcard grants and inheritance with
/lp editor, paying special attention to world protection bypasses and economy modification. - Test each group with a non-OP account in a protected area and record exactly which commands succeed or fail.
Why this matters
Treat console access, operator status, remote-control credentials, and proxy secrets as privileged access. Limit them to people and systems that actually need them.
Important limitation: Reloading configuration may not refresh all plugin permission caches. Use each plugin’s documented reload or a controlled restart.
How to verify the result
- A moderator should have moderation actions but be unable to change plugin configuration or grant administrator permissions.
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.
Related guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.