Direct answer

Velocity’s proxy commands are not Bukkit commands. Use /velocity for proxy management and /server for switching among configured backends.

Step-by-step procedure

  1. Run /velocity info to check proxy version if you have velocity.command.info.
  2. Run /velocity plugins to list proxy plugins with velocity.command.plugins; this does not list backend Paper plugins.
  3. Run /server to see your current backend or /server survival to request a named destination.
  4. For proxy-wide player counts, use /glist only after granting velocity.command.glist; /shutdown is console-only.

Common mistakes and trade-offs

Avoid giving ordinary players administrative proxy permissions. The /velocity heap dump can contain sensitive details; restrict and protect generated files.

How to verify it worked

Test each command with a restricted player account and an administrator, confirming which layer responds.

Version and platform differences

Command availability, permissions and plugin overrides should be checked against the installed Velocity build and plugin stack.

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.

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