Minecraft: BungeeCord Plugins

BungeeCord plugins are extensions for the BungeeCord proxy, not for a single game server. Players connect to the proxy first, and it forwards them to the right backend server, such as a lobby, survival or minigame server, keeping the connection open when they switch. Plugins on the proxy control what happens across the whole network: connections and server switching, permissions, network-wide chat, the MOTD and protection against bots.

It depends on the proxy plugins your network needs. BungeeCord brings one of the largest libraries of proven proxy plugins, its own plugin API and central configuration through config.yml. Velocity is a separate project with its own plugin API, and BungeeCord plugins do not run on it. Many large plugins, LuckPerms among them, ship a build for both, so check which proxy your most important plugins support before you decide.

Proxy plugins go into the plugins folder of BungeeCord and work on the network layer: connections, server switches, chat and commands. Spigot and Paper plugins run on the backend servers where the actual gameplay happens, so you still need at least one backend server behind the proxy. Some tools need both sides: LuckPerms, for example, runs on the proxy and on every backend and keeps ranks in sync through a shared database. Paper plugins for your backend servers

The fastest way is the plugin browser in the ZAPX panel: search for the plugin, click install and restart the proxy. Plugins that are not in the catalog, for example from SpigotMC or BuiltByBit, go into the plugins folder of your proxy as a .jar file via the file manager. If a plugin does not load, read the proxy console: the usual causes are a Spigot plugin placed on the proxy, a missing dependency or the wrong Java version. Guide: BungeeCord server config settings

On Waterfall, usually yes: it is a BungeeCord fork and runs most BungeeCord plugins. Velocity uses its own plugin API that is not compatible with BungeeCord plugins, so every plugin needs a Velocity build or a Velocity-native alternative. Moving a network over? Back up your config.yml first, check each plugin for Velocity support and test the switch with a small group before you open the proxy to everyone again. Browse Velocity plugins

Set ip_forward to true in the proxy's config.yml and enable BungeeCord mode on your backend servers so they receive real player IPs and UUIDs. Add BungeeGuard so backends only accept connections that come through your proxy, keep the backend servers from being reachable directly and run an anti-bot plugin against join floods. Your proxy on ZAP-Hosting is DDoS-protected at no extra cost, with nothing for you to set up.