How to Configure a BungeeCord Network in Multicraft

Overview

A Minecraft network lets players move between separate servers for lobbies, survival worlds, minigames, events, and other game modes. That kind of setup cannot run properly from one normal Minecraft server. BungeeCord solves this by acting as a proxy that connects multiple servers together.

A basic BungeeCord network needs at least three servers:

• One proxy server running BungeeCord
• One backend server, such as a lobby
• One additional backend server, such as survival or minigames

Players do not play on the proxy itself. The proxy only handles routing and passes players to the servers behind it. It is the traffic director, not the theme park.

For better security, it is strongly recommended to install a plugin such as PreventPortBypass on the backend servers. This helps stop players from connecting directly to a backend server instead of entering through the proxy. Without that protection, some backend servers may be reachable in ways you do not want, especially when offline-mode settings are involved.

Prepare the Proxy Server

The proxy server should be dedicated to BungeeCord. It does not need as much memory as a full gameplay server because it is only managing connections between servers.

To set up the proxy in Multicraft:

1. Open the Multicraft panel for the server you want to use as the proxy.
2. Stop the server.
3. Reset the server files if this server was previously used for something else. Only do this after backing up anything you need, since resetting files removes existing server data.
4. Find the server jar or version selector.
5. Choose BungeeCord.
6. Save the change and start the server once so the default BungeeCord files generate.
7. Stop the server again before editing the configuration.

Starting the server once is important because it creates the config files you need for the next step.

Configure BungeeCord

In the proxy server files, open `config.yml`. This is where the proxy behavior and server list are controlled.

Check the following settings:

• `force_default_server`: Set this to `true` if players should always join the default server first, usually a lobby. Set it to `false` if players should return to the last server they were on.
• `ip_forward`: Set this to `true`. This allows player IP and UUID information to pass correctly through the proxy.
• `online_mode`: Keep this set to `true` on the proxy.
• `motd`: Change this to the server list message you want players to see.

Next, find the `servers:` section. This is where each backend server is added. A default example entry may already exist, and you can use its format as a template.

Each backend server entry needs a name and an address. The address must include the IP and port of that specific backend server. For example, you might create entries named `Lobby` and `Survival`.

Server names are case sensitive. If you name a server `Lobby`, then `lobby` is not the same thing.

After adding your backend servers, find the `priorities:` section. This controls the default server players join first. Most networks set this to the lobby server. The name listed under `priorities:` must exactly match one of the names from the `servers:` section.

Save `config.yml`, then restart the proxy server.

Configure Each Backend Server

These steps must be completed on every server behind the proxy. Do not apply them to the proxy server.

For each backend server:

1. Stop the server from Multicraft.
2. Open the server files.
3. Edit `server.properties`.
4. Find `online-mode=` and set it to `false`.
5. Save the file.
6. Open `spigot.yml`.
7. Find `bungeecord:` near the top of the file.
8. Set `bungeecord:` to `true`.
9. Save the file and start the server.

This looks unusual at first because backend servers are placed in offline mode. That is normal for a BungeeCord network. The proxy stays in online mode and handles authentication before sending players to the backend servers.

Test the Network

After the proxy and backend servers are configured, connect using the proxy server address, not the backend server addresses.

Once connected, test movement between servers using your preferred BungeeCord command or server selector setup. If the proxy sends players to the correct default server and can route them to the other backend servers, the core network is working.

Common Problems

Kicked While Connecting to a Server

If the error mentions IP forwarding, the proxy is usually missing the correct setting. Open the proxy `config.yml` and make sure `ip_forward` is set to `true`. Save the file and restart the proxy.

Server Is in Online Mode

This usually means one of the backend servers still has `online-mode=true` in `server.properties`. Every backend server behind BungeeCord should have `online-mode=false`. The proxy should remain in online mode.

Players Are Not Joining the Right Server

Check the `priorities:` section in the proxy `config.yml`. The listed name must match a server name under `servers:` exactly, including capitalization.

Configuration Copied From the Internet Does Not Work

BungeeCord configs are specific to your server IPs, ports, and names. Copying a random template often creates more problems than it solves. Start from the default generated config, then edit it carefully for your own servers.