Direct answer

Identify which system owns the command before granting access. Vanilla operator status and plugin permission nodes are different; avoid giving every player OP as a workaround.

What it means

A command may be restricted by vanilla permissions, a plugin-defined node, a proxy command handler, or a region/world condition. The text “Unknown command” can also hide a command from unauthorized players.

If you are a player

  1. Copy the exact command and denial message and note whether the same command works for another player with the same group.
  2. Ask an administrator whether the command is vanilla, from a backend plugin or from a proxy. A plugin command on a backend may not exist on the proxy.
  3. Do not ask for full operator status merely to use one everyday command; request the minimum appropriate permission.

If you run the server

  1. Run the command as an operator or from the backend console to distinguish missing registration from a permission check. Console behavior can differ for player-only commands.
  2. Find the required node in the plugin’s official documentation or plugin.yml. Assign only that node to the correct group using the installed permissions manager; permissions are plugin-specific.
  3. Check command aliases, namespace collisions, world contexts and LuckPerms-style group inheritance where relevant. Restart after changing plugins; do not use global /reload to diagnose loading.
How to verify the fix

Test with the intended non-OP group, an unrelated non-OP group and an operator. Confirm only the intended group gains the command.

References

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