Updated How It Works (markdown)

ME1312 2019-09-14 13:06:27 -04:00
parent d4b238d73a
commit 97d27fd2e1

@ -11,7 +11,7 @@ The **Green Arrow** signals that the app is hosting the server it points to
SubServers 2 on the surface may seem very simplistic, but the way it accomplishes it's goals is actually quite complex.
### SubServers.Bungee
SubServers.Bungee is the heart of SubServers 2. It is tasked with managing all of your servers — even ones not hosted by the internal host driver, provides a SubData Server for the rest of the apps to connect to, and routes players that connect to it where they need to go all at the same time. It also loads connection information for servers that will not be managed by the server manager from BungeeCord's config (*Server 3 in the chart*), and can make use of the RedisBungee plugin when available to access and utilize synced player information from other proxies on the network.
SubServers.Bungee is the heart of SubServers 2. It is tasked with managing all of your servers — even ones not hosted by the internal host driver, providing a SubData Server for the rest of the apps to connect to, and routing players that connect to it where they need to go all at the same time. It also loads connection information for servers that will not be managed by the server manager from BungeeCord's config (*Server 3 in the chart*), and can make use of the RedisBungee plugin when available to access and utilize synced player information from other proxies on the network.
### SubServers.Host
SubServers.Host is the way to create, add, and remove subservers to/from the server manager that exist on other machines. SubServers.Bungee is able to talk to SubServers.Host to tell it what to do and how it should go about doing what it does though it's connection SubData.