Skip to content
Platforms

BungeeCord and Velocity proxy plugins

Proxy plugins that run on BungeeCord (or Waterfall) and Velocity. What to specify, what Codexe generates and how the build is checked.

Updated

On this page
  1. BungeeCord or Velocity?
  2. What to put in the request
  3. Build and verification
  4. Install

A proxy plugin runs on the proxy in front of your backend servers, not on a game server. Typical uses: network-wide chat, staff tools, server switching, maintenance mode, MOTD and player counts.

#BungeeCord or Velocity?

The BungeeCord/Velocity type covers both, but they're different APIs. Say which proxy you run in the request:

  • BungeeCord / Waterfall: the classic API, bungee.yml.
  • Velocity: the modern API, velocity-plugin.json or annotations.

If you run both, ask for two separate projects.

#What to put in the request

  • The proxy and its version.
  • Commands (proxy commands, not backend commands), permissions and who can run them.
  • How it talks to backend servers (plugin messaging channels need a companion backend plugin; ask for that as a separate Spigot/Paper project).
  • Storage and config.

#Build and verification

The proxy plugin is compiled with Maven and checked for the right descriptor (bungee.yml, plugin.yml or velocity-plugin.json) before it's Ready. Without a version in the request, the BungeeCord API 1.21 is used.

#Install

Put the JAR in the proxy's plugins/ folder and restart the proxy.

BungeeCord and Velocity proxy plugins | Codexe Docs