Advertisement
Guest User

Untitled

a guest
Jun 19th, 2020
683
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.36 KB | None | 0 0
  1. # Specify all your hub servers here: (required)
  2. servers:
  3. - Hub-1
  4. - Hub-2
  5. - Hub-3
  6.  
  7. # Specify the required client version for each Hub, leave as an empty array [] to use BungeeCords' defaults.
  8. # The values are parsed as Integers and can be obtained from http://wiki.vg/Protocol_version_numbers
  9. required-client-versions:
  10. Hub1: []
  11.  
  12. # Specify the duration (in seconds) between server pings.
  13. # This is used in selecting servers for the "lowest", "firstavailable", "random" and "sequential" modes.
  14. # 3 seconds is the default. If you have more than 10-12 hubs this number may need increasing.
  15. ping-duration: 2
  16.  
  17. # Specify the type of server selection you want.
  18. # HubMagic supports the following modes:
  19. # - lowest: Will attempt to connect to the least-populated server.
  20. # - firstavailable: Attempts to connect to the first available server in the list above.
  21. # - random: Attempts to connect to a random server.
  22. # - sequential: Attempts to connect to the the servers listed above in sequence.
  23. #
  24. # The recommended default is "lowest".
  25. type: random
  26.  
  27. # Specify how HubMagic will direct players to hubs upon connecting:
  28. # HubMagic supports the following:
  29. # - reconnect: Reconnects all players that join the network to a hub.
  30. # - none: Disables HubMagic's reconnect handling. This still provides for /hub.
  31. connection-handler: reconnect
  32.  
  33. # Specify the ping strategy to use.
  34. # HubMagic supports the following:
  35. # - bungee: Uses the BungeeCord ping handler. Recommended but doesn't work in some situations.
  36. # - fallback: Uses zh32's server list ping library which may work better in some cases.
  37. #
  38. # The recommended default is "fallback".
  39. ping-strategy: fallback
  40.  
  41. # Whether or not kicks will take you back to the hub.
  42. # This applies only when the server is not listed in this file as a hub server.
  43. # You may also optionally control it by using regex in this file.
  44. # The default is enabled, without any regex matches, effectively disabling the function.
  45. kicks-lead-to-hub:
  46. enabled: true
  47. mode: "reasons"
  48. reasons: []
  49. servers: []
  50. message: "&cThe server you were on is now down, you have been connected to the hub."
  51. # You can use any HubMagic selector here, but "random" and "sequential" is recommended.
  52. selector: random
  53. # Whether or not to invert the matched checks (allowing the matches to act as a blacklist). For instance, if a
  54. # player's kick reason or server matches the list, they WILL NOT be reconnected to the hub and will be kicked instead.
  55. # Conversely, this setting is on and no reasons or servers are fined, anyone on those servers will be moved to the hub.
  56. blacklist: false
  57.  
  58. # Options for the hub command.
  59. hub-command:
  60. # Whether or not the command is enabled.
  61. enabled: true
  62. # Whether or not to require hubmagic.hub permission.
  63. requires-permission: false
  64. # The aliases used to access this command.
  65. aliases:
  66. - hub
  67. - leave
  68. - lobby
  69. - h
  70. - l
  71. # If you have aliases that must be forwarded to the backend server,
  72. # this will ignore HubMagic's handling for it.
  73. # Regex is supported.
  74. forwarding:
  75. global:
  76. - minigameserver1
  77. - minigameserver2
  78. # Messages for /hub. There is only one message currently available.
  79. messages:
  80. already_connected: "&9&lYou are already connected to the hub."
  81. 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