| 1 | # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
|
| 2 | # #
|
| 3 | # _ ___ #
|
| 4 | # (_) / _ \ #
|
| 5 | # __ _ _ | | | | _ _ ___ _ _ ___ #
|
| 6 | # / _` || || | | || | | | / _ \| | | | / _ \ #
|
| 7 | # | (_| || |\ \/' /| |_| || __/| |_| || __/ #
|
| 8 | # \__,_|| | \_/\_\ \__,_| \___| \__,_| \___| #
|
| 9 | # _/ | #
|
| 10 | # |__/ #
|
| 11 | # #
|
| 12 | # Welcome to the config for ajQueue! #
|
| 13 | # #
|
| 14 | # Make sure to read the comments above each option to know what that option does. #
|
| 15 | # #
|
| 16 | # If you have any questions, first make sure you've read the comment above the option, then #
|
| 17 | # feel free to join my discord and ask there (invite link is on the plugin page) #
|
| 18 | # #
|
| 19 | # Happy configuring! #
|
| 20 | # #
|
| 21 | # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
|
| 22 |
|
| 23 |
|
| 24 | # The time the server will wait between sending people in the queue (in seconds, supports decimals)
|
| 25 | # Default: 5
|
| 26 | wait-time: 5.0
|
| 27 |
|
| 28 | # The time ajQueue will wait between sending players update messages on
|
| 29 | # what position they are in the queue, their ETA, and status of the queue (in seconds)
|
| 30 | # You can set to any negative number to disable the messages
|
| 31 | # Default: 10
|
| 32 | message-time: 10
|
| 33 |
|
| 34 |
|
| 35 | # Should we require permissions for players to be able to join queues?
|
| 36 | # If enabled, players will be required to have the permission ajqueue.queue.<server> to be able to join queues
|
| 37 | # Replace <server> with the name of the server or group to let the player queue for
|
| 38 | # Default: false
|
| 39 | require-permission: false
|
| 40 |
|
| 41 | # Should we act like servers a player doesn't have permission for doesn't exist?
|
| 42 | # So if a player doesn't have permission to queue for a server, and they try to queue for it,
|
| 43 | # ajQueue will send the server-not-exist message instead of the noperm message.
|
| 44 | # This option does nothing if require-permission is disabled.
|
| 45 | # IMO this is pointless, but people keep asking for it so here you go...
|
| 46 | # Default: false
|
| 47 | act-like-no-permission-servers-dont-exist: false
|
| 48 |
|
| 49 | # Require a permission for players to be able to join a queue from a server.
|
| 50 | # If enabled, players will need the permission ajqueue.joinfrom.<server> to join queues.
|
| 51 | # Replace <server> with the name of the server
|
| 52 | # Default: false
|
| 53 | joinfrom-server-permission: false
|
| 54 |
|
| 55 | # Should we enable the ajqueue.bypasspaused permission?
|
| 56 | # If enabled, anyone with the permission ajqueue.bypasspaused will be able to join paused servers
|
| 57 | # Default: false
|
| 58 | enable-bypasspaused-permission: false
|
| 59 |
|
| 60 |
|
| 61 | # What kick reasons should cause the player to be removed from the queue?
|
| 62 | # This works on contains, so you only need to include a word or two from the kick message.
|
| 63 | # For example, if one of the below kick reasons is 'banned' and the player gets kicked when trying to connect to
|
| 64 | # a server in a queue with a message saying "You are banned from this server!" then it will kick them from the queue too.
|
| 65 | kick-reasons:
|
| 66 | - 'banned'
|
| 67 | - 'blacklisted'
|
| 68 |
|
| 69 |
|
| 70 | # When a player is kicked from a server, should we automatically add that player to the queue?
|
| 71 | # On BungeeCord, you will still need to use another plugin to make sure the player doesn't get kicked from the proxy completely.
|
| 72 | # Default: false
|
| 73 | auto-add-to-queue-on-kick: false
|
| 74 | # The delay for the above option.
|
| 75 | # In seconds, decimals supported.
|
| 76 | # Default: 1
|
| 77 | auto-add-to-queue-on-kick-delay: 1
|
| 78 |
|
| 79 | # With what kick reasons should we auto-add the player to the queue
|
| 80 | # This won't work if auto-add-to-queue-on-kick is disabled.
|
| 81 | # If you set it to [], then all kick messages will cause the player to be added to the queue
|
| 82 | # This works on contains, so you don't have to include the whole kick message, just a few words.
|
| 83 | auto-add-kick-reasons:
|
| 84 | - "restarting"
|
| 85 | - "closed"
|
| 86 |
|
| 87 |
|
| 88 | # If a player is in a server, you can have the plugin make them automatically join a queue for another server
|
| 89 | # Example with the default values: Player joins the limbo server, they will auto-join the queue for the lobbys group
|
| 90 | # Note that you don't have to use groups. Just put the name of a server to use a single server instead.
|
| 91 | # You do NOT have to set a queue server to use queues.
|
| 92 | queue-servers:
|
| 93 | - 'limbo:lobbies'
|
| 94 |
|
| 95 | # How much should we delay queueing players in queue servers?
|
| 96 | # You should only use this if you have issues with the instant sending.
|
| 97 | # Set to 0 or any negative number to disable
|
| 98 | # In milliseconds. Maximum value is 3000 (3 seconds)
|
| 99 | # Default: 0
|
| 100 | queue-server-delay: 0
|
| 101 |
|
| 102 | # Before a player connects to a queue-server, check if they would be instantly sent to the target server.
|
| 103 | # If they would, this option will bypass the queue-server completely and connect them directly to the target server.
|
| 104 | # If they would not be sent instantly, then they will be put in the queue in the queue-server as normal.
|
| 105 | # Default: true
|
| 106 | skip-queue-server-if-possible: false
|
| 107 |
|
| 108 |
|
| 109 | # Should we completely kick the user from the server if they are in a queue-server
|
| 110 | # and are kicked from the server with one of the above reasons?
|
| 111 | # Note this will do nothing on servers that aren't queue-servers
|
| 112 | # (as in the config option queue-servers)
|
| 113 | # Default: true
|
| 114 | kick-kicked-players: true
|
| 115 |
|
| 116 | # This option allows you to manually set player caps for servers
|
| 117 | # Note that this does NOT override the player cap returned by the server.
|
| 118 | # Format: - '<server>:<max-players>'
|
| 119 | # Example: - 'lobbys:50'
|
| 120 | # The example above will limit the lobbys group to have a total of 50 players.
|
| 121 | # This works on both groups and individual servers
|
| 122 | manual-max-players: []
|
| 123 |
|
| 124 |
|
| 125 | # Server groups are a group of servers that you can queue for. It will send you to the server that is the least full.
|
| 126 | # If all servers in the group are full, it will act the same as it would when a single server is full.
|
| 127 | # Same if all servers are offline. It will only send players to servers that are online.
|
| 128 | # Format: "groupname:server1,server2,etc"
|
| 129 | server-groups:
|
| 130 | - "lobbies:lobby,lobby2,lobby3,practicelobby"
|
| 131 | - "smps:smp"
|
| 132 | - "duelss:duels"
|
| 133 | - "swordffas:swordffa"
|
| 134 | - "uhcpracs:uhcprac"
|
| 135 |
|
| 136 | # What balancer should we use for groups?
|
| 137 | # If a group is not specified here, then the default one is used
|
| 138 | # Example: - "bedwars:minigame"
|
| 139 | # The example above will set the bedwars group to use the minigame balancer
|
| 140 | # Balancers:
|
| 141 | # default - Will send the player to the server in the group with the least number of players
|
| 142 | # minigame - Will send the player to the server with the most players, until that server is full, which it will then send to the next server
|
| 143 | # first - Will send the player to the first available server in the group (as long as it is joinable)
|
| 144 | balancer-types:
|
| 145 | - "default:lobbies"
|
| 146 | - "default:smps"
|
| 147 | - "default:duelss"
|
| 148 | - "default:swordffas"
|
| 149 | - "default:uhcpracs"
|
| 150 |
|
| 151 | # If a player is in a server that is in a group and they re-queue for that group, should we allow it?
|
| 152 | # false - prevent player from re-queueing; say "already connected" message
|
| 153 | # true - let player re-queue; will send them to a server other than the one they're connected to
|
| 154 | # Default: false
|
| 155 | allow-group-requeue: false
|
| 156 |
|
| 157 |
|
| 158 | # What priority should we give whitelisted players priority when the server is whitelisted?
|
| 159 | # This will have no effect if the server isn't whitelisted
|
| 160 | # If you set to 0, this will be disabled
|
| 161 | # If you have the free version, set it to 1 to enable
|
| 162 | give-whitelisted-players-priority: 0
|
| 163 |
|
| 164 | # What priority should we give players that are able to bypass paused priority when the server is paused?
|
| 165 | # This will have no effect if the server isn't paused
|
| 166 | # If you set to 0, this will be disabled
|
| 167 | # If you have the free version, set it to 1 to enable
|
| 168 | give-pausedbypass-players-priority: 0
|
| 169 |
|
| 170 | # What priority should we give players that are able to bypass full servers priority when the server is full?
|
| 171 | # This will have no effect if the server isn't full
|
| 172 | # If you are using make-room, this also applies to that
|
| 173 | # If you set to 0, this will be disabled
|
| 174 | # If you have the free version, set it to 1 to enable
|
| 175 | give-fulljoin-players-priority: 0
|
| 176 |
|
| 177 |
|
| 178 | # Should we remove a player from the queue if they move servers?
|
| 179 | # This will remove the player from if they switch to any other server
|
| 180 | # Default: false
|
| 181 | remove-player-on-server-switch: false
|
| 182 |
|
| 183 | # Should we enable the server command being a queue command?
|
| 184 | # This may require extra setup on bungeecord. See the wiki:
|
| 185 | # https://wiki.ajg0702.us/ajqueue/setup/replacing-server-command
|
| 186 | # Requires a server restart after changing to apply
|
| 187 | # Default: false
|
| 188 | enable-server-command: false
|
| 189 |
|
| 190 | # What servers should we make slash server commands for?
|
| 191 | # For example, if survival is in this list, then if a player executes /survival
|
| 192 | # then they will be put in the queue for survival
|
| 193 | # This works for both servers and groups
|
| 194 | # If you have ajQueuePlus, you can also make aliases.
|
| 195 | # For example, if you have a server called lobby, and you want people to be able to use /hub, you can use this:
|
| 196 | # - "hub:lobby"
|
| 197 | # If you have the free version, you can only put the server name, no aliases.
|
| 198 | slash-servers: []
|
| 199 |
|
| 200 | # Should we enable /send as an alias for /ajQueue send?
|
| 201 | # If on bungeecord, this requires extra setup (same as replacing the server command but with send instead)
|
| 202 | # Requires a server restart to apply.
|
| 203 | # Default: false
|
| 204 | enable-send-alias: false
|
| 205 |
|
| 206 |
|
| 207 | # Should we enable priority messages?
|
| 208 | # Configure the priority messages in the option below.
|
| 209 | # Default: false
|
| 210 | enable-priority-messages: false
|
| 211 |
|
| 212 | # Messages we send to players with priority queue when they join the queue
|
| 213 | # In the free version, "priority" is 1.
|
| 214 | # The * will send when a player joins with any priority.
|
| 215 | # The format is <priority>:<message>
|
| 216 | # Example: 1:You have a priority of 1!
|
| 217 | priority-messages:
|
| 218 | - "*:<green>Joining the queue with a priority of {PRIORITY}!"
|
| 219 | - "100:<yellow>Wow! You have a priority of 100!"
|
| 220 |
|
| 221 |
|
| 222 | # Should the plugin send a title to the player?
|
| 223 | # The title shows what position the player is in the queue
|
| 224 | # Default: false
|
| 225 | send-title: false
|
| 226 |
|
| 227 | # Should we log to the proxy console when a player fails to get sent to a server from the queue?
|
| 228 | # Enable this if you are having an issue with one player stopping the queue
|
| 229 | # Default: false
|
| 230 | send-fail-debug: false
|
| 231 |
|
| 232 | # Should the plugin send an actionbar to the player?
|
| 233 | # The actionbar contains some info such as which server they are queued for, what position they are in, estimated time remaining, etc.
|
| 234 | send-actionbar: true
|
| 235 |
|
| 236 | # THIS FEATURE IS ONLY AVAILABLE ON ajQueuePlus (https://www.spigotmc.org/resources/ajqueueplus.79123/)
|
| 237 | # This will show players a different name than the actual proxy server name
|
| 238 | # for example, instead of showing players "event-a", this option can make it appear as "Event A"
|
| 239 | # With this example, you would use this: - "event-a:Event A"
|
| 240 | # Note that currently players still have to use the normal names in queue commands and leave commands
|
| 241 | # Format: "realname:Alias"
|
| 242 | server-aliases:
|
| 243 | - "event-a:Event A"
|
| 244 |
|
| 245 | # The time that a server has to be offline to be marked as offline instead of restarting (in seconds)
|
| 246 | # Default: 120
|
| 247 | offline-time: 120
|
| 248 |
|
| 249 | # On velocity, should we send a player a message when they are kicked while trying to connect to a server with the queue?
|
| 250 | # This has no effect on bungee, because the message is sent from bungee and there's no way to change that in ajQueue
|
| 251 | # Default: false
|
| 252 | velocity-kick-message: false
|
| 253 |
|
| 254 | # Should we wait until the server is done loading to load the servers?
|
| 255 | # Enable this if you have a plugin that adds servers to the server list during startup.
|
| 256 | # Default: false
|
| 257 | wait-to-load-servers: false
|
| 258 |
|
| 259 | # How long should we wait after the server finishes loading to load the server list?
|
| 260 | # Only works if the above is enabled.
|
| 261 | # This is in milliseconds so 1000 = 1 second
|
| 262 | # Default: 500
|
| 263 | wait-to-load-servers-delay: 500
|
| 264 |
|
| 265 | # How often (in seconds) we should check for new servers to add queues for.
|
| 266 | # If you dynamically add servers, set this to something other than 0.
|
| 267 | # To disable, set to 0
|
| 268 | # Default: 0
|
| 269 | reload-servers-interval: 0
|
| 270 |
|
| 271 | # Should we let players join more than one queue?
|
| 272 | # If enabled, players will be able to be in multiple queues at once.
|
| 273 | # If disabled, players will be removed from the previous queue when joining a new queue
|
| 274 | # Default: true
|
| 275 | allow-multiple-queues: true
|
| 276 |
|
| 277 | # If the player is queued for multiple servers, which server should we pick to use in things like placeholders and actionbars
|
| 278 | # Options are first and last
|
| 279 | # Default: last
|
| 280 | multi-server-queue-pick: last
|
| 281 |
|
| 282 | # How long should we wait after a server is online before sending players?
|
| 283 | # The server will still show up as offline or restarting until this amount of time after its up
|
| 284 | # Meant to let your server 'cool down' after lag from starting up
|
| 285 | # In seconds
|
| 286 | # Default: 1
|
| 287 | wait-after-online: 1
|
| 288 |
|
| 289 | # This is for helping with finding issues with the server pinged
|
| 290 | # This will spam the console when enabled
|
| 291 | # When this enabled, if servers are offline then it will spam errors. You can ignore them.
|
| 292 | # Default: false
|
| 293 | pinger-debug: false
|
| 294 |
|
| 295 | # When a queue is paused, should we prevent players from joining it?
|
| 296 | # (instead of having players wait in the queue until it's unpaused)
|
| 297 | # Default: false
|
| 298 | prevent-joining-paused: false
|
| 299 |
|
| 300 | # When a server goes back online, should we send all players in the queue instantly?
|
| 301 | # Default: false
|
| 302 | send-all-when-back-online: false
|
| 303 |
|
| 304 | # Should we allow tab-completing in the /queue command?
|
| 305 | # Any server the player doesn't have permission for (require-permission)
|
| 306 | # will not tab-complete
|
| 307 | # Default: true
|
| 308 | tab-complete-queues: true
|
| 309 |
|
| 310 | # Should we have no wait time for these servers?
|
| 311 | # If the server is joinable, the plugin will attempt to send players who join these queues as soon as they join.
|
| 312 | # If the server is not immediately joinable, they will have to wait for the normal wait-time
|
| 313 | # This also works with group
|
| 314 | # NOTE: Server names are caps sensitive
|
| 315 | send-instantly:
|
| 316 | - "lobbys"
|
| 317 |
|
| 318 | # Should we require permissions for queue-servers to work?
|
| 319 | # If enabled, players will need to have the ajqueue.queueserver.<server> permission
|
| 320 | # <server> being the target server
|
| 321 | # Note that this will only affect queue-servers
|
| 322 | # Default: false
|
| 323 | require-queueserver-permission: false
|
| 324 |
|
| 325 | # After how many (unsuccessful) attempts of sending the player should we remove them from the queue?
|
| 326 | # Set to -1 to disable
|
| 327 | # Default: 10
|
| 328 | max-tries: 10
|
| 329 |
|
| 330 | # What QueueHolder should we use?
|
| 331 | # By default, the only QueueHolder available is 'default'
|
| 332 | # But more may be available via addons (registered via the API)
|
| 333 | queue-holder: default
|
| 334 |
|
| 335 |
|
| 336 | # Should we enable the ajqueue.make-room permission?
|
| 337 | # The make-room permission will force there to be room in a server.
|
| 338 | # So, if a player with this permission queues for a server and has this permission,
|
| 339 | # someone from the server will be moved to the lobby to make room
|
| 340 | # This can be further configured using the next few options
|
| 341 | # Default: false
|
| 342 | enable-make-room-permission: true
|
| 343 |
|
| 344 | # What server should the make-room permission move players to?
|
| 345 | # Default: lobby
|
| 346 | make-room-kick-to: lobby
|
| 347 |
|
| 348 | # For the make-room permission, players with the lowest priority are kicked first.
|
| 349 | # Of those players, this option decides which to kick.
|
| 350 | # true - kick players who have been on the server the longest
|
| 351 | # false - kick players who have been on the server the shortest
|
| 352 | # Default: true
|
| 353 | make-room-kick-longest-playtime: true
|
| 354 |
|
| 355 |
|
| 356 | # Should we check every 4 seconds if a player has a higher priority permission than before
|
| 357 | # If they do, they are removed and re-added to the queue (only if they would be put in a higher position)
|
| 358 | # Default: false
|
| 359 | re-check-priority: false
|
| 360 |
|
| 361 | # Should we check to make sure that people don't get sent quicker than wait-time?
|
| 362 | # Default: true
|
| 363 | check-last-player-sent-time: true
|
| 364 |
|
| 365 | # Should we send debug info to the console when priority queue is used?
|
| 366 | # This will print several lines to the console when a player joins a queue,
|
| 367 | # so you should probably only use this for debugging purposes
|
| 368 | # Default: false
|
| 369 | priority-queue-debug: false
|
| 370 |
|
| 371 | # What protocols do servers support?
|
| 372 | # The protocol version number list can be found here: https://wiki.vg/Protocol_version_numbers
|
| 373 | # Format: server(s):protocol(s)
|
| 374 | # Example: 1.17:755,756
|
| 375 | # This example will only allow 1.17 and 1.17.1 on the server called 1.17
|
| 376 | # Example: lobby-1,lobby-2,lobby-3:754,755,756
|
| 377 | # This example will only allow 1.16.5, 1.17, and 1.17.1 on the 3 lobby servers
|
| 378 | supported-protocols:
|
| 379 | - "1.17:755,756"
|
| 380 |
|
| 381 | # Should the updater be enabled?
|
| 382 | enable-updater: true
|
| 383 |
|
| 384 | # Should we force players to be queued every few seconds for queue-servers?
|
| 385 | # This will check every few seconds, and if a player in a queue-server is
|
| 386 | # not in the queue for the target server, it will add them.
|
| 387 | force-queue-server-target: true
|
| 388 |
|
| 389 | # How long should the cooldown for queue commands be? (in seconds)
|
| 390 | # Set to -1 to disable
|
| 391 | # Default: 3
|
| 392 | queue-command-cooldown: 3
|
| 393 |
|
| 394 | # Should any server switch (including the initial join) count against the queue command cooldown?
|
| 395 | include-server-switch-in-cooldown: false
|
| 396 |
|
| 397 | # The minimum time between pinging the server. (in seconds)
|
| 398 | # If ajQueue is pinging your backend servers too often, raise this number
|
| 399 | minimum-ping-time: 1.0
|
| 400 |
|
| 401 | # In ajQueuePlus, if your permission plugin isn't yet supported, you can use this workaround to
|
| 402 | # be able to use levels 1-10 for priority, or 15, 30, 60, and 120 for stayqueued
|
| 403 | # If you want more levels than that, contact aj to add support for your permission plugin if possible.
|
| 404 | # Does nothing if you are not on ajQueuePlus, or if you have a supported permission plugin
|
| 405 | plus-level-fallback: false
|
| 406 |
|
| 407 | # Should we print some extra stuff to the console that might help aj diagnose some issues?
|
| 408 | debug: false
|
| 409 |
|
| 410 |
|
| 411 |
|
| 412 | # # # # # # # # # # # # # # # # # # # # #
|
| 413 | # #
|
| 414 | # End of config. Happy queue-ing :) #
|
| 415 | # #
|
| 416 | # # # # # # # # # # # # # # # # # # # # #
|
| 417 |
|
| 418 |
|
| 419 |
|
| 420 |
|
| 421 | # Don't touch this number please
|
| 422 | config-version: 47
|
| 423 |
|
| 424 |
|
| 425 | # This is ONLY here so that they can be moved to messages.yml. Please edit these in messages.yml!
|
| 426 | protocol-names: []
|
| 427 | # ^ only edit these in messages.yml
|
