Lucas Whitman
ceb7d4bbe4
Here's the markdown list: ## Queue Features Implemented in This Commit - Redirection to a queue server when the main server is full - Messages about users waiting spot - Fallback recovery if the main server goes down, this includes appropriate message updates and re-queueing - Admins bypass the queue entirely even if the server is full using the permission node `queue.admin` - Admins can use `/queue pull <PlayerName>` to force bypass them to the main server for a single time - `/queue pause` can be used to stop the queue from sending new players to the main server - `/queue status` will tell any player (not just admins) the current conditions of the main and queue server, such as: - If the main server is online - Position in queue - Min/max players on the main server - The status of whether the queue is paused or not - `/queue resume` unpauses the paused queue - `/queue list` is an admin command providing information on what players are in queue and how they are being prioritized (queue points) - Tiered queue points based ticketing system where whoever has the most points takes the next available server slot - Permission node configuration file allowing administrators to define how many seconds it takes for (let's say) a VIP player to get a queue point - Configuration files for server settings: - Which server is the queue server in Velocity - The max amount of non-admin player slots on the main server - The main server defined in a Velocity config
2 lines
27 B
Groovy
2 lines
27 B
Groovy
rootProject.name = 'queue'
|