Multiple servers and Velocity

One server versus a network#

A normal SMP is one Minecraft process and one set of worlds. A network has a public proxy in front of several backend servers.

Internet → Velocity → Lobby / Survival / Creative / Minigames

A proxy routes players. It does not merge several worlds into one simulation, share plugin data automatically or remove the need to secure backend servers.

Do you need it?#

Usually no. One Paper server can already have multiple worlds and game modes through plugins. Use a proxy when you need separate processes, independent restarts, different server software/versions or failure isolation.

Basic architecture#

1. 1
   Players connect only to Velocity’s public address.
2. 2
   Velocity authenticates/routes the connection.
3. 3
   Backend servers listen on private addresses or firewall rules that accept only the proxy.
4. 4
   Secure player-information forwarding tells backends the real authenticated identity.
5. 5
   Network-aware plugins coordinate chat, parties or shared data where needed.

Velocity#

Velocity is PaperMC’s modern proxy with a current API, secure forwarding options and active development. Velocity plugins are their own ecosystem; a BungeeCord plugin does not automatically work.

Official source: Velocity documentation ↗

BungeeCord and Waterfall#

BungeeCord is historically important and still has a large plugin ecosystem. Waterfall was PaperMC’s fork, but PaperMC announced its end of life and directs new deployments to Velocity. Do not begin a new network on Waterfall expecting current-version support.

Beginner-safe plan#

1. 1
   Build and back up two working backend servers first.
2. 2
   Put them on a private network.
3. 3
   Install current Velocity and use the exact Java version its docs require.
4. 4
   Configure modern forwarding exactly once across proxy and backends.
5. 5
   Firewall backend game ports from the public internet.
6. 6
   Add one backend at a time and test identity, skins, permissions and reconnects.
7. 7
   Back up proxy configuration and each backend independently.

Advanced details#

Shared inventories, permissions, bans and chat usually need databases or network-aware plugins. A proxy is not a database. Plan failure modes: what happens when the lobby, database, proxy or one backend is unavailable?