Bookmark and share the address of UP-Community on your social bookmarking website
The old Join Queue mechanism
This is a straight queue, with no prioritization. The first person to join the queue will be first to join the server when there is room available.
The new Join Queue mechanism
Players are divided into three groups:
1. Players on the Reserved Slots list (eg. UP clan members who are at the list)
2. Premium players
3. Normal players
The "Reserved Slots" list is a list with player names. The list is stored locally on each server, and managed by each server administrator.
When a player attempts to enter a full server, the player will go into the queue. Later on, when a player leaves the server, one player from the queue will be let onto the server. The server will first pick a player from the Reserved Slots group; if that group is empty, one from the Premium players group; lastly, one from the Normal players group.
If there are several people in a group, the player who has been waiting the longest in a group has precedence.
In addition to this there is the "aggressive join" setting. If Aggressive Join is enabled, then if a Reserved Slots player joins the queue, a user on currently on the server will be kicked to make room for the Reserved Slots player.
The Aggressive Join setting does not apply when Premium or Normal players enter the queue.
Bugs in the new Join Queue mechanism
There are two known bugs in Server R24 (which is currently running on all servers).
The first, and biggest, is that players who enter via the join queue will not get GUIDs. Also, "player.onJoin" events are not sent. This confuses some third party admin tools. PunkBuster does not always display these players in the "pb_sv_plist" output either. So-called 'ghost players' are caused by this as well.
We have identified the problem and developed a fix for this earlier this week. We expect it to go live sometime during next week. Until that time we recommend that server administrators who have problems with the new queue do not run third-party autobalancers or other similar scripts.
The second is that servers sometimes don't display the right number of max players on Battlelog. This seems to happen only to servers which run "adaptive server size" plugins. We are still investigating this. It is probably not related to the Join Queue at all, but the reports arrived at the time when we switched to the Join Queue mechanism - so, it's worth mentioning.
Powered by lakes of coffee and mountains of jaffa cakes.
- VIP staff member
- Posts: 669
Join date: 2012-01-18
- Posts: 287
Join date: 2012-01-14
Location: London, UK