B
BlackSpigot Guides
Guest
Use a normal test account to investigate permissions. Giving everyone operator status hides the problem.
Start with one failing action
Write the exact command or menu action, the world/server where it happens and the message the player sees. Check the plugin's documentation for the permission associated with that action. A command can have one permission to open it and another for a specific subcommand.
Compare two controlled cases
Use the same command, world, location and plugin version for an admin account and an ordinary test account. Record the difference. Then inspect the ordinary account's effective permission result with your installed permissions manager. Include inherited groups and world/server contexts. A group membership by itself does not prove that a particular node is allowed in that context.
Change the smallest relevant setting
Grant only the documented permission to a temporary test group. Repeat the action. If it still fails, check plugin-specific restrictions such as a disabled feature, cooldown or world restriction before granting broader privileges. Remove the temporary grant when the test ends.
Post this worksheet for help
Do not post account credentials or an entire private permissions database. A small, redacted effective-permission result is easier to diagnose. If you find the answer, reply with the exact node and context that fixed it so the discussion helps the next server owner.
For plugin authors, declare and check your permission requirements consistently. Command and permission descriptor reference
Start with one failing action
Write the exact command or menu action, the world/server where it happens and the message the player sees. Check the plugin's documentation for the permission associated with that action. A command can have one permission to open it and another for a specific subcommand.
Compare two controlled cases
Use the same command, world, location and plugin version for an admin account and an ordinary test account. Record the difference. Then inspect the ordinary account's effective permission result with your installed permissions manager. Include inherited groups and world/server contexts. A group membership by itself does not prove that a particular node is allowed in that context.
Change the smallest relevant setting
Grant only the documented permission to a temporary test group. Repeat the action. If it still fails, check plugin-specific restrictions such as a disabled feature, cooldown or world restriction before granting broader privileges. Remove the temporary grant when the test ends.
Post this worksheet for help
Code:
Server and plugin versions:
Action and exact response:
World/server context:
Documented permission:
Effective result for the test account:
Temporary change tried:
Result after the change:For plugin authors, declare and check your permission requirements consistently. Command and permission descriptor reference