Direct answer
Velocity permissions govern proxy commands and plugins. Paper/Bukkit backend permissions are separate unless you deliberately configure an integration that synchronizes them.
Step-by-step procedure
- Identify the exact proxy permission, for example
velocity.command.plugins, from official command documentation. - Grant it using a permission system that operates at the proxy layer; check the plugin’s own instructions for propagation and storage.
- Test with a normal client account via the proxy, then test the corresponding Paper command separately on a backend.
- Audit proxy-wide wildcard permissions and remove administrative grants not required for the user’s role.
Common mistakes and trade-offs
Making someone OP on a backend does not automatically grant all Velocity proxy permissions. Likewise a proxy-side grant does not promise access to a backend plugin.
How to verify it worked
Confirm a non-privileged account is denied sensitive /velocity commands and a designated operator account is allowed only intended commands.
Version and platform differences
Velocity permission defaults and specific nodes can change; consult the built-in command reference of the deployed version.
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.