BungeeCord is NOT a requirement for the Enhanced ProxySync add-on. It may even run with Velocity and any other proxy sync add-on, as the add-on is only being installed on the Spigot server.
There is an official add-on that provides an easy-to-use solution for setting up a complex network of servers. Within them, you may join and manage your arenas from any server. You may obtain the addon from the following sources:
Basically, it includes the following features:
storage-typeeither being MYSQL, MARIADB or MICROSOFT_SQL). We suggest to use Redis during production as it provides greater stability, efficiency and a lower latency. You MUST use the REDIS protocol if you are using the MongoDB storage type. For deeper instructions, you might want to check out the
protocol-typeconfiguration within the addon's config.yml file.
is-hubconfigurations (located inside configs.yml)
That's it! You may restart your servers once. They should automatically find each other. This addon supports reloading and automatically syncs the servers in case one lost the connection.
Displays the current status of the network.
Displays all the arenas that are currently connected with this server.
Displays some informations about a server.
Measures how long it takes to ping a server (how long it takes to send a messages and to get a reply).
Moves you or an other player to a given server.
Moves you or an other player to a hub server.
Connects this server from the network and tries to establish a reconnection.
The cause for this could be:
bungee-channel-nameis not correct (located within the config.yml file)
Whenever you are supposed to be sent back, the plugin is going through all servers that have
is-hub set to true (located inside config.yml). With those servers, it is looking for the one with the lowest amount of online players, to which you will be sent. Reasons for it not working could be:
is-hubis not set to true
is-hubis set to true for the game server
Go through all servers and validate that the value of the
bungee-channel-name are correct (as specified within Bungee's config file).
Pool "Internal Arenas" = All the arenas that are created on your own server
Pool "Remote Arenas" = All the arenas that one server has fetched from other servers
To clarify that an arena is coming from an other server, and not the current one, it is being prefixed using "@". It is not possible to prefix a local arena using that character. As it is possible that multiple servers in the network are having an arena with the same name (as in the example the arena "marmor"), further arenas are being extended by a # and an upcounting number. Keep in mind that the number may vary of when the server has received the information from an other server. It is possible that the arenas (as in the example "@marmor" and "@marmor#2") are switching their names, as it depends on which server has sent his informations the first.
Which of these pools are being used by a feature depends on the implementation and the use case of the feature itself.
Some features may only use Pool "Internal Arenas", such as:
Some features may use both Pool "Internal Arenas" and Pool "Remote Arenas", such as:
The plugin is going to try to warn you if you are trying to use a feature that is not being supported for remote arenas.