Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # Specify all your hub servers here: (required)
- servers:
- - Hub-1
- - Hub-2
- - Hub-3
- # Specify the required client version for each Hub, leave as an empty array [] to use BungeeCords' defaults.
- # The values are parsed as Integers and can be obtained from http://wiki.vg/Protocol_version_numbers
- required-client-versions:
- Hub1: []
- # Specify the duration (in seconds) between server pings.
- # This is used in selecting servers for the "lowest", "firstavailable", "random" and "sequential" modes.
- # 3 seconds is the default. If you have more than 10-12 hubs this number may need increasing.
- ping-duration: 2
- # Specify the type of server selection you want.
- # HubMagic supports the following modes:
- # - lowest: Will attempt to connect to the least-populated server.
- # - firstavailable: Attempts to connect to the first available server in the list above.
- # - random: Attempts to connect to a random server.
- # - sequential: Attempts to connect to the the servers listed above in sequence.
- #
- # The recommended default is "lowest".
- type: random
- # Specify how HubMagic will direct players to hubs upon connecting:
- # HubMagic supports the following:
- # - reconnect: Reconnects all players that join the network to a hub.
- # - none: Disables HubMagic's reconnect handling. This still provides for /hub.
- connection-handler: reconnect
- # Specify the ping strategy to use.
- # HubMagic supports the following:
- # - bungee: Uses the BungeeCord ping handler. Recommended but doesn't work in some situations.
- # - fallback: Uses zh32's server list ping library which may work better in some cases.
- #
- # The recommended default is "fallback".
- ping-strategy: fallback
- # Whether or not kicks will take you back to the hub.
- # This applies only when the server is not listed in this file as a hub server.
- # You may also optionally control it by using regex in this file.
- # The default is enabled, without any regex matches, effectively disabling the function.
- kicks-lead-to-hub:
- enabled: true
- mode: "reasons"
- reasons: []
- servers: []
- message: "&cThe server you were on is now down, you have been connected to the hub."
- # You can use any HubMagic selector here, but "random" and "sequential" is recommended.
- selector: random
- # Whether or not to invert the matched checks (allowing the matches to act as a blacklist). For instance, if a
- # player's kick reason or server matches the list, they WILL NOT be reconnected to the hub and will be kicked instead.
- # Conversely, this setting is on and no reasons or servers are fined, anyone on those servers will be moved to the hub.
- blacklist: false
- # Options for the hub command.
- hub-command:
- # Whether or not the command is enabled.
- enabled: true
- # Whether or not to require hubmagic.hub permission.
- requires-permission: false
- # The aliases used to access this command.
- aliases:
- - hub
- - leave
- - lobby
- - h
- - l
- # If you have aliases that must be forwarded to the backend server,
- # this will ignore HubMagic's handling for it.
- # Regex is supported.
- forwarding:
- global:
- - minigameserver1
- - minigameserver2
- # Messages for /hub. There is only one message currently available.
- messages:
- already_connected: "&9&lYou are already connected to the hub."
- no_hubs_available: "&9&lThere are no hubs available. Please try again in a few minutes."
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement