Minecraft Proxies and You
Proxies are the perfect solution if you’re looking to lighten the load off a single server, or if you’re looking to branch out and support multiple play-styles under one umbrella. Overall this post aims to give a medium-level rundown, keeping the nitty-gritty details for the proxies’ official docs. If you want to read more on different server softwares, check out my post here. Overall, a proxy takes in a Minecraft client connection on one port, then directs that player’s connection to a multitude of backend servers.
Note, to use a proxy in AMP, your backend servers must have Standalone Server
disabled in the Minecraft instance’s settings.
Velocity
Yes, I’m putting Velocity first because I’m biased, but also because it has the most info to cover. Velocity offers three forwarding methods: modern, bungeeguard, and legacy (BungeeCord). Modern forwarding is by far the most secure, cryptographically signing the initial player-hello packet that’s sent to the backend server when the player switches to said server. BungeeGuard does something similar, but is compatible with legacy forwarding, and is optional on the backend servers. Legacy forwarding is inherently insecure and shouldn’t be used if you don’t have access to a firewall.
Note, if you want to proxy Forge 1.13-1.20.1 servers, you must use the Ambassador Velocity plugin.
Good reads:
BungeeCord
As mentioned, BungeeCord’s default forwarding is insecure without either firewall rules or BungeeGuard, and caution should be taken when setting up BungeeCord (or even just legacy forwarding in general), as someone who’s been at the receiving end of UUID-spoofing, it’s not fun, and it involves restoring a bunch of backups.
You can forward Arclight 1.14+ servers using the LightFall-Client mod along with the LightFall Waterfall/BungeeCord fork, otherwise modern Forge support is near nonexistant on BungeeCord.
Good reads:
Modern Forwarding
-
Overall only supported with 1.13+ servers
-
Natively supported by Paper/Sponge
-
Supported on Forge 1.14.4-1.21.1 using Proxy Compatible Forge (yes, I do help maintain this one)
-
Supported on NeoForge using Proxy Compatible Forge (1.20.2-1.21.1) or NeoForwarding (1.20.4-1.21.1)
-
Supported on Fabric 1.16.5-1.21.1 using FabricProxy Lite
-
Supported on some Modloader-Bukkit hybrids, see my other post for a full list. Though it’s usually best to let a mod handle it.
BungeeGuard Forwarding
-
Supported on 1.7.10-present
-
Supported on Sponge and any Spigot derivative assuming the BungeeGuard plugin supports the version
- Modloader-Bukkit hybrids implement Spigot and should be compatible as long as ProtocolLib (a BungeeGuard dependency) can load.
Legacy Forwarding
-
Supported on 1.7.10-present
-
Is not secure without firewall rules
-
Supported on Sponge and any Spigot derivative
-
Supported on most popular Forge versions from 1.7.10-1.20.1 using BungeeForge
-
Supported on Fabric 1.16.4-1.18.1 using FabricProxy, but is no longer maintained in the primary repo