Direct answer

A player can be listed as OP yet still lack permission for a command belonging to a plugin. First determine which implementation handles the command.

Identify the failing layer

Do not grant wildcard permission * as a diagnostic shortcut, and do not assume OP provides every plugin privilege.

First checks and evidence

  • Check the exact player name and UUID; confirm the player appears in ops.json after a clean stop.
  • For a vanilla command, check operator level and test it from the server console.

Admin diagnosis and repair

  1. For plugin commands, look up the documented permission node and test with the relevant permissions manager.
  2. If a proxy command is involved, check Velocity permissions separately from Paper operators.

Verify the fix: Test the exact command from a designated operator and a normal account; verify the privilege boundary matches your policy.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

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