We are aware of a potentially service impacting issue. Learn more

How to Install and Configure BungeeCord Print

  • 16

Should you find setting up your network difficult while following this guide, you can also purchase our BungeeCord Setup addon ($15.00 USD for a one-time setup). You can find more information regarding our addons here.

To begin setting up a BungeeCord Network, you'll first need at least 3 servers. Your BungeeCord server can be our special Bungee plan ($1.99 USD/month). The Bungee plan can only be purchased by submitting a ticket to our Billing department. The BungeeCord server is a non-joinable server that holds your network together. This means you will only be able to play on the 2 or more connected servers that are set up within your BungeeCord configuration.

BungeeCord does not create servers, only connect to them, so all servers you use in this configuration must be active plans with MCProHosting or other methods of hosting Minecraft servers. These connected servers will need to be our Steve plan or higher.

We'll be using the following server IPs today to set up an example network:

BungeeCord: 111.222.333.44:55555

Hub: 222.333.444.55:77777

PvP: 333.444.555.77:88888

The IPs you will use in your configuration will not look like these IPs. These IPs are to be used solely as a reference and for this guide.

1. Installing BungeeCord
The very first thing you'll need to do to successfully create a BungeeCord network is to install BungeeCord to your server of choice. This can be done by using our Server Type module or by manually installing and enabling a BungeeCord jar file of your choice.

You will also need to run the Spigot server type on all other servers in your network, as Spigot comes with tools that allow it to easily link to your BungeeCord server. You can change your server to Spigot by using the same guides provided above.

2. Initial Setup
Now that we have our IPs laid out and BungeeCord and Spigot are installed to the servers we want to link together, we need to insert them into your config.yml file. This file is found in the home directory of your FTP after first starting up your BungeeCord server.

Once open, you'll want to first locate the 'servers' section, it will look a lot like this:

Notice that the servers section currently only has one server. You'll need to add another server to the servers section for each server you want to add to your network. Once done, you can rename the default 'lobby' name of the server to whatever you'd like to use. This name is what is used when using the /server command, so we recommend not using spaces and only using alphanumeric characters.

You'll also need to change the address line to the IP of the server you are looking to use. All other lines in the 'servers' section don't need to be changed to complete a basic configuration.

For our example, your servers section should look like this:

You can add as many servers as you would like, just keep in mind they must be active servers.

Once these servers are added, you should move down your 'config.yml' file and locate the host setting. By default, it will look like this:

Check the Firewall and Port Mapping section on your server control panel and for the Primary port mapping, check the Destination Port. You'll need to set this as the port for that host setting. Your Destination port will either be 25565 or 25577. Ensure that is changed in the host setting like this and then save changes:


3. Configuring a Hub

Now that we have all of our servers represented in BungeeCord's config.yml, you'll want to set what server your BungeeCord routes players to on their first time joining. This is usually a Hub server, but can be any of the servers on your network. To do this, simply change the priorities setting in your config.yml to the server's name you'd like players routed to. It will look like this:

In our case, we'd change the setting to Hub.


You can also add other servers to this setting if you would like. BungeeCord will attempt to route players from the highest listed server to the lowest listed, so if our Hub server crashes, players will be moved to our PvP server so long as it is listed. This configuration looks like this:



4. Configuring IP Forwarding

After finishing with the host setting and changing priority, you should change the ip_forwarding setting. This setting is used by BungeeCord to forward a player's IP to your server. This is extremely useful when you need to lookup the IP of a player or IP ban a user. If this setting is not changed to true, then all players will be assigned the IP of your BungeeCord server and IP banning will not be possible.

5. Configuring Connected Servers

After we've configured all of these settings and have made it so our BungeeCord server can function properly, you'll need to change a few settings on the servers you've connected to BungeeCord to allow them to function properly. 

For Spigot servers, this is as simple as opening the spigot.yml file from your FTP's home directory and changing the bungeecord setting to true.

You'll then need to open your server.properties file and change the online-mode setting to false. This is necessary so your BungeeCord server can properly route players.

Now that these settings are changed and your BungeeCord network is configured, simply restart all servers on your network and you should be able to connect!

If you encounter issues setting up your network or have any questions, simply send us a ticket and we will be happy to help!

Further Configuration and Settings

Now that we have the basic settings for BungeeCord configured and the rest of our network is enabled, we can start changing the settings that determine how you BungeeCord server and network looks and functions. You can find these settings and what they do below.

Online_mode: This setting is used to determine whether your BungeeCord server is in offline or online mode. We highly recommend having this setting set to 'true'.

Motd: This setting determines the motd displayed in the server's listing of Minecraft's Multiplayer section. This motd setting uses formatting codes instead of the usual method of creating an motd.

Tab_list: Unfortunately, this setting was discontinued in the newest versions of BungeeCord. We recommend using the BungeeTablistPlus plugin instead.

Max_players: This setting determines what number of players the server displays in its server listing. This setting is completely cosmetic. If you want to change how many players can connect to the server, you'll want to change the 'player_limit' setting instead.

Tab_size: This setting simply determines how large your tablist is across servers when pressing the 'tab' key.

Force_default_server: This setting is very important if you want to route players to your Hub server every time they disconnect. By changing this setting to 'true', your players will be moved to the spawn point of your highest priority server. This means if a player disconnects from our PvP server, they will be automatically moved to our Hub server when logging back into our network. Having this setting set to 'false' simply means players will login where they had logged out.

Adding Administrators to your Network

Now that we have BungeeCord set up properly, configured, and customized, we can now add players to your BungeeCord network that can run administrator commands.

To do this, simply locate the following section in your 'config.yml' file:

To add a player, you can simply change the 'md_5' variable to your username or another player's username. You can add as many players as you like. If you choose to do so, your configuration should look similar to the following:

You've now completed setting up, configuring, and adding players to your network! If you have any questions or experience issues with your network, you can send us a ticket at any time to receive assistance.

Was this answer helpful?

« Back