How To: Configure BungeeCord

This guide is designed to help you configure a BungeeCord server after you’ve installed it. If you haven’t installed it yet, please refer to our guide on [How To Install BungeeCord](/en-us/article/bungeecord-installation-1cxxqyq/) before you continue reading. If you would like to have our technicians set up a BungeeCord server for you, please check out our BungeeCord Installation Addon on our [Adding Addons](/en-us/article/adding-addons-1ap1h1q/) page.

`config.yml`
groups
* Here, you can assign players to a permission group. The permission groups will be created later in the configuration. The format is “groups”, followed by each player, followed by each group he/she is in. Every player gets the permissions of the default group only. Add players who need more than the default permissions to this setting.

`disabled_commands`
* Use this to disable commands on your BungeeCord instance. You can disable BungeeCord or Bukkit commands.

`player_limit`
* This is the global player limit for your BungeeCord instance. If this is set to -1 (default), this will allow an unlimited amount of users to join your network.

`stats`
* This is used for stats purposes, please do not remove or alter the code. This is a randomly generated number in the purpose of providing stats. Stats are anonymous packets of usage collected on MCStats. This is something you should never edit, so leave it be.

`permissions`
* These are the permissions of what commands or actions each group can use within the proxy. Please note, that these are different to Bukkit/Spigot permissions. The permissions are group based. All players will have ability to use the commands under “default”. Players assigned to a group in the “groups” section are allowed to use the extra commands for BungeeCord as stated below that group. Note each group only inherits “default” so you may need to put the same node in different groups if you choose for those groups to have additional permissions.

`listeners`
* These items are configurable options that can be found under the listeners section of the BungeeCord configuration. Multiple listeners can be added to listen on several IP’s and ports.

`max_players`
* The max player limit shown in the Minecraft client’s multiplayer menu. Note that this limit is fake, so even if you set it to 0, players will still be able to join. Look at ‘player_limit’ above for a “real” player limit.

`fallback_server`
* This settings sets the server to connect to if the default server is unavailable.

`host`
* This the IP and port in which the BungeeCord instance will be hosted on. You’ll want to use your server IP and port that is assigned your BungeeCord server here.

`bind_local_address`
* Whether the address Bungee uses to connect to your servers will be explicitly set to the address Bungee is listening on. This serves no purpose unless your system has multiple IP addresses.

`ping_passthrough`
* Whether to pass the ping through when we can reliably get the target server (force default server).

`tab_list`
* The tab list has a choice of 3 options.
1. GLOBAL_PING: This shows all players connected to the proxy, complete with ping.
2. GLOBAL: As above, but without updating their ping.
3. SERVER: This shows the local players on the server you are connected to.

|| Note – BungeeCord 1.8 versions currently do not have working GLOBAL or GLOBAL_PING options due to 1.8 having a new tab list.

`default_server`
* The server that first time players will connect to, or if forcing default server, will always join upon connecting.

`forced_hosts`
* Allows for redirection. If the pvp.md-5.net sub-domain of the domain md-5.net is joined, it will bypass the default server and go to the server that is stated in the config, in this case directly to the pvp server.
Note: this requires you to make sub-domains forwarded to your BungeeCord address via the main Dynamic DNS as for your main domain.

`tab_size`
* The amount of players that will show up in the tab list (pressing TAB on keyboard). NOTE: This does not currently do anything for 1.8.x servers.

`force_default_server`
* If this is set to true, the player will always connect to the default server when they join. If this is set to false, the player will join the server they were last connected to. Note: “forced_hosts” does NOT override this. To make the “forced_hosts” setting work, set this setting to false.

`motd`
* This is the message that will be displayed in the multiplayer menu when players ping the server.

`query_enabled`
* This settings sets whether or not to enable UDP query.

`query_port`
* This setting sets the port to run the UDP query on.

`timeout`
*This setting sets how long the proxy should go unresponsive before shutting off all connections.

`connection_throttle`
* This setting sets the time delay before a client is allowed to connect again after a recent connection attempt to prevent attacks (in milliseconds).

`servers`
* Within this section, you will list all the servers that will be connected to via the BungeeCord instance. It is recommended to use lowercase for the names of the servers.

`ip_forward`
* Whether to enable IP forwarding which allows you to see the true IP of the player, rather than the proxy IP address.

`online_mode `
* Whether the BungeeCord instance will authenticate with the Mojang servers. If set to false, cracked players will be able to join your server.

Sample Config: http://pastebin.com/2Cnindm6

||| Disclaimer: GGServers provides this sample “as-is” and “as-available”. GGServers and its staff are not responsible for any problems that may arise from your use of these samples and will not be held liable for any actions that derive from such use.

| Feel free to open a ticket in your client area if you need any assistance.