For a new network on current Paper versions, Velocity is usually the stronger starting point: Modern Forwarding protects player information with a secret and MAC, and the API targets modern Minecraft. BungeeCord remains reasonable when an existing network depends on BungeeCord plugins or very old versions and migration adds more risk than value.
PaperMC explicitly recommends Velocity. That recommendation comes from Velocity's provider and maintainer; its own comparison page acknowledges that perspective. BungeeCord is not discontinued: its repository and Jenkins still received commits and successful builds in 2026. Waterfall, PaperMC's former BungeeCord fork, is end of life.
Comparison at a glance
| Criterion | BungeeCord | Velocity |
|---|---|---|
| existing BungeeCord plugins | native | not generally compatible; verify each plugin |
| legacy Minecraft | broad historical compatibility | Modern Forwarding starts at 1.13; legacy modes exist |
| secure native forwarding | legacy format without its own MAC secret | Modern Forwarding with secret/MAC |
| BungeeGuard | optional additional protection | BungeeGuard mode exists; Modern is usually preferred |
| new Paper networks | works with strict network protection | recommended by PaperMC |
| Waterfall migration | API-adjacent, but Waterfall is EOL | separate proxy/API; migration required |
| proxy plugins | BungeeCord API | Velocity API |
The table makes no blanket player-count or performance claim. Hardware, compression, plugins, protocols, and traffic shape all affect performance and require reproducible load tests.
Forwarding and security
BungeeCord legacy forwarding transports IP, UUID, and profile data but has no proxy-specific signature secret. An offline-mode backend must therefore be reachable only from the correct proxy. BungeeGuard can add a secret; use version 1.4.0 or newer and rotate affected tokens after upgrading.
Velocity Modern Forwarding signs the forwarded information with a shared secret. This makes proxy impersonation substantially harder, but it does not replace a clean network boundary. A backend port should not be unnecessarily public in either design.
Paper's official documentation ranks the modes accordingly: Modern is more secure, BungeeGuard improves on plain legacy, and legacy is more compatible but less secure. Modern Forwarding is unavailable below Minecraft 1.13.
When BungeeCord is the sensible choice
- The running network relies on critical BungeeCord plugins with no verified Velocity replacement.
- Old Minecraft or mod-loader versions are business-critical.
- The team understands the current configuration and backend network protection is proven.
- A migration would put UUIDs, permissions, or plugin messaging at risk without a complete test path.
In that case, “keep and harden” beats an untested modernization. Use the BungeeCord setup guide, config.yml reference, and secure forwarding guide.
When Velocity is the sensible choice
- You are building a new network on current Paper versions.
- Every required proxy plugin exists for Velocity or has a tested replacement.
- Modern Forwarding is compatible with all backends.
- You want a modern API and can fully test migration on a clone.
Fabric and Forge still require version-specific checks. “Better mod support” is not a compatibility guarantee for every loader and Minecraft release.
BungeeCord-to-Velocity migration checklist
- Create and restore-test backups of proxy configuration, plugins, databases, and backend player data. Use the backup and rollback workflow.
- Inventory all proxy plugins and classify each as “Velocity native,” “replacement,” “removed,” or “blocker.”
- Rebuild server list, listeners, forced hosts, and permissions intentionally; do not paste Bungee YAML into
velocity.toml. - Generate the Modern Forwarding secret on the target and treat it like a password.
- Configure Paper or the relevant mod loader for exactly one forwarding mode.
- Test online UUID, real client IP, skins, permissions, plugin messaging, lobby, switching, and fallback.
- Test a wrong-secret path and independent direct backend access as negative cases.
- Verify DNS/SRV and Geyser/Floodgate separately.
- Keep the BungeeCord rollback ready until production joins are stable.
Plugins and operations
BungeeCord plugins do not automatically run on Velocity. Compatibility layers do not replace explicit support. When installing plugins, verify platform, current release, dependencies, data migration, and security notices.
A proxy restart disconnects players but does not restart backends. For either proxy, plan maintenance, back up configuration and plugins, and monitor process, TCP, Minecraft ping, and a real lobby join separately.
Decision matrix
| Starting point | Recommendation |
|---|---|
| new, current Paper network | evaluate Velocity with Modern Forwarding first |
| existing BungeeCord network with critical plugins | keep and secure BungeeCord; test migration separately |
| Waterfall | plan replacement; the project is EOL |
| Minecraft below 1.13 | inspect compatibility; Modern Forwarding is unavailable |
| unclear plugin landscape | inventory and clone-test before any production migration |
DNS points at the proxy in either case; the domain and SRV guide stays applicable. To build new instances, start with Minecraft server hosting.