Direct answer

A Velocity plugin must load in the Velocity proxy’s plugin directory, not in a Paper or Spigot backend plugins folder. Installing the right JAR in the wrong process can cause unknown plugin type errors or no effect.

What it means

Velocity plugins target the Velocity API; Paper plugins target a different API. A network plugin may offer separate artifacts for the proxy and backend.

Practical example: Example: a Velocity-only authentication extension copied into Paper’s plugins folder may fail to register any commands. Removing that JAR from Paper and placing it under the proxy’s plugin directory can fix the deployment, but check whether the extension requires a separate Paper companion before assuming installation is complete.

If you are a player

  • Report which server you connect through and which feature is missing.
  • Avoid retrying a backend-specific command on the proxy without checking the plugin documentation.

If you run the server

  1. Check the artifact name and official platform compatibility list.
  2. Stop the proxy, remove the misplaced Velocity JAR from the backend and install it in the proxy plugins directory.
  3. If the feature also needs a backend companion, install only the separate compatible backend build documented by its author.
  4. Restart both processes in a controlled order; read Velocity startup logs for plugin registration.
  5. Test through the public proxy rather than connecting directly to a backend.

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