Created for @Aeronx , and posted with his permission.
This is just the bare-bone functions of the full system, so you will need to create talkactions, or a client interface to implement it fully.
--------------------
Generic Queue System - by Xikini
This system is designed to allow players to form queues, and be sent to an event area.
It tracks if an event is closed, open and occupied by global_storage
When sending players into an event, it will change the global storage from 0 to 1, and when the event is finished, will attempt to send the next set of players.
The system knows nothing about the events it is sending the players to, so keep that in mind.
The event must notify the Queue System that the event is finished by resetting the global_storage to 0.
The event must also call the function "removeFromQueue(playerId, completedEvent)" on each player that entered, or else the queue system will not know that individual players have finished the event.
Of note, party leaders are able to join and exit the queue, and will attempt to bring their entire party in/out of the queue.
Individual players can remove themselves from a queue, but party members cannot enter a queue unless the party leader initiates it.
Before sending players into an event, there is a readiness check, to confirm players are present.
If the player fails to ready up, they will be ejected from the queue. (If that player is in a party, will eject the entire party from the queue.)
(assuming they are in the same queue as the rest of the party.. cuz technically they could join a queue, and then join a party afterwards.. but the system basically handles this by not allowing the leader to join a queue if any of the members are currently in a queue / event. In this case the leader basically has the option of waiting for that member to cancel / finish event, or ejecting from the party. But that's a direct user issue and not something the system can handle on it's own, so we just assume players will understand that they should form their intended party, then join a queue. If they join queue, then form a party, none of the new members would be added to the queue, and vise versa.)
This is just the bare-bone functions of the full system, so you will need to create talkactions, or a client interface to implement it fully.
--------------------
Generic Queue System - by Xikini
This system is designed to allow players to form queues, and be sent to an event area.
It tracks if an event is closed, open and occupied by global_storage
When sending players into an event, it will change the global storage from 0 to 1, and when the event is finished, will attempt to send the next set of players.
The system knows nothing about the events it is sending the players to, so keep that in mind.
The event must notify the Queue System that the event is finished by resetting the global_storage to 0.
The event must also call the function "removeFromQueue(playerId, completedEvent)" on each player that entered, or else the queue system will not know that individual players have finished the event.
Of note, party leaders are able to join and exit the queue, and will attempt to bring their entire party in/out of the queue.
Individual players can remove themselves from a queue, but party members cannot enter a queue unless the party leader initiates it.
Before sending players into an event, there is a readiness check, to confirm players are present.
If the player fails to ready up, they will be ejected from the queue. (If that player is in a party, will eject the entire party from the queue.)
(assuming they are in the same queue as the rest of the party.. cuz technically they could join a queue, and then join a party afterwards.. but the system basically handles this by not allowing the leader to join a queue if any of the members are currently in a queue / event. In this case the leader basically has the option of waiting for that member to cancel / finish event, or ejecting from the party. But that's a direct user issue and not something the system can handle on it's own, so we just assume players will understand that they should form their intended party, then join a queue. If they join queue, then form a party, none of the new members would be added to the queue, and vise versa.)
