Using Bungee to link multiple servers together is an effective way to manage and efficiently operate your servers should you desire more than one instance or game type of Minecraft. It may seem daunting at first but setting up a Bungee Cord for use on Apex Minecraft Hosting is rather simple and can be installed by those with little previous experience. Lets first start with the structure of a Bungee minecraft server network.
To utilize a bungee network you should have at least 3 servers. 1 for the proxy and 2 backends servers which players physically join to. The proxy server acts as the gateway that delivers players onto a backend server such as a Hub or lobby.
Installing BungeeCord
- First thing we do is install the Bungee proxy jar which we can find on the Spigot Jenkins repo; select the BungeeCord.jar file.
- Now connect to your server files via FTP.
- To ensure a successful installation it’s recommended you delete all files prior to installing the jar with the exception of the jar folder.
- With all other files removed we can now upload the BungeeCord.jar into the jar folder; once it’s finished uploading you should rename it to custom256.jar.
- Now we need to tell the server what jar to use. Since we named it “custom256.jar” we select Custom 256 from the jar drop list, save and then start the server.
- From this point we will need to review the console to ensure its up and running due to compatibility issues outputting the correct state on the status indicator.
Installing Spigot
- The next step is to setup the two backend servers. For this you simply need to install Spigot on both and you can quickly do this by selecting the it from the jar dropdown.
- Once selected, save and then start the server to ensure they are up and running.
Configuring BungeeCord
Once you install the BungeeCord.jar onto the proxy server and started it will have generated a config.yml file. Access the proxy’s server files via FTP and edit this file. When you go to edit this file you will see a configuration setup similar to the following. Most of it we can ignore. What you should take note of are lines 2, 14, 16-19, 22-23, and 27.
- To start off we need to set line 2 (ip-forward) to true.
- Line 14 (online-mode) true.
- Line 16-19 will list all the servers that will be connected to via the BungeeCord instance.
- Line 16 define the name of the backend server. It is recommended to use lowercase for the names of the servers
- Line 17 is the full IP address of the server. You will replace this with the IP:port of the backend server you plan to link up.
- Line 18 prevents players from joining the server when set to true.
- Line 19 sets the Message Of The Day for that particular server.
- To add more servers to the network simply add a new line under line 19 and paste the following code and edit its values accordingly.
- servername:
address: 192.168.1.1:25565
restricted: false
motd: ‘&1Just another BungeeCord – Forced Host’ - Line 22 is the fallback server, in event the default server (line 27) goes offline, all player attempting to connect will go to the fallback server.
- Line 23 is the full IP address of the server hosting the proxy, the server that is running the BungeeCord.jar. Enter in yours.
- Line 27 defines the default server in which all players attempting to connect will join to. This entry should be a name of one of you backend servers i.e line 16.
- Once you add all of your respective backend and configured their values on this config file, save and then restart the Proxy server. We now move to the backend servers.
#BungeeCord Config.yml file contents
groups:
AshKetchum:
- admin
disabled_commands:
- find
player_limit: 100
stats: 4DACA6AB-C060-41B1-8FC2-C20D96C42274
permissions:
default:
- bungeecord.command.server
- bungeecord.command.list
op:
- bungeecord.command.server
admin:
- bungeecord.command.server
- bungeecord.command.alert
- bungeecord.command.end
- bungeecord.command.ip
- bungeecord.command.reload
listeners:
- fallback_server: lobby
max_players: 100
host: 127.0.0.1:25565
tab_size: 60
force_default_server: true
tab_list: SERVER
motd: 'MOTD of my server'
default_server: lobby
forced_hosts:
example.net: auth
bind_local_address: false
ping_passthrough: false
query_enabled: true
query_port: 25577
timeout: 30000
connection_throttle: 4000
servers:
lobby:
address: 127.0.0.1:25566
restricted: false
motd: 'My Bungee Lobby'
ip_forward: true
online_mode: true
Configuring Backend Servers
- With Spigot installed we navigate to the respective servers file via FTP and edit the spigot.yml file.
- Locate the “bungeecord” value and set it to “true“.
- Next we need to set the respective backend servers “online-mode” value to false. YOu can edit this vaule in the server.properties file
That’s it, now repeat this process for every other backend server you plan to add to your network to link them as one. This process is a bit tricky at first but easy to grasp once you’ve done it. If you need any help in setting up a bungee network, Apex Support offers services with such requests granted you carry our Premium Support service.
You will need to purchase a server for people to connect to which will be running the Bungee Cord jar file and be the only point of access for the public. This server can be the smallest package that we offer as it won’t need very much RAM to be stable, we estimate using 10MB per estimate player or a 1GB server for a player base of 100. The next server will host your lobby where all of the players will automatically be directed to. This server will be used to show off your building skills and link off to all of the individual games in sections of the lobby. I’m sure everyone here has seen a typical hub server setup. The rest of the servers will host the individual games, it is ideal to put one game per server and link off to that. If you want to host multiples of the same game, purchase multiple minecraft hosting and put one server on each.
