DayZ Priority Queue and Reserved Slots

A full DayZ server shows a queue. The public page on DayZ Manager reports that queue when the server reports it. Players experience it as a number that does not move. Reserved slots are the admin's way to keep a few connections for people who should not wait: staff, the event runner, the friend who is about to fix the crash. A priority queue is the same idea with ranks. Neither one is a whitelist. Everyone else can still join while a slot is free.

Decide how many slots you can afford to hold back. A 60-slot server that reserves 20 for a staff of three is a 40-slot server with a dishonest hostname. Players can see slots and players on the roster. They cannot see your reserve list, and they will still feel the difference when the queue never includes them. Publish the policy in one sentence. "Staff reserved" is enough. "Donators skip the line" is a product decision you should mean, because it changes who plays.

CFTools Cloud is where those lists should live if you want joins, reserves, and bans in one permission model. A reserved-slot text file on the host and a ban list in Cloud will drift. The person who donates and the person you banned last month might be the same person. Check. A reserve that overrides a ban is a bug in your process, not a feature of DayZ.

The queue is not lag. A server with a queue and a smooth simulation is popular. A server with no queue and a stall every time someone drives is under-provisioned. Do not "fix" a queue by raising slots until the CPU falls over. Read requirements before you chase a number. The player chart tells you the peak. Size the cap near the peak you can actually run. Empty slots do not improve rank, and a queue you cannot serve does not either.

Password servers and reserved slots stack. A password keeps strangers out. Reserved slots order the people you let in. If you wanted a private test, a password or a whitelist is the honest tool, and the server does not belong on the open list. If you wanted a public community with a short staff bypass, reserved slots are the tool, and the server can stay public.

Do not sell priority in a way you cannot administer. If the only record of who paid is a Discord pin, you will get it wrong. Cloud, or whatever list you actually check at ban time, has to be the list the queue honors. CFTools Architect does not decide your priority policy. It hosts the process. The policy is management. Pricing for Cloud is on cftools.com/pricing, not a number this page should invent, and it is not the same thing as whatever you charge players for a reserved slot. Those are your rules. Write them down. Apply them the same way twice.

When the queue is long every night, you have a success and a ceiling. Open a second server only if you can moderate it. A second unattended process is a second place for the problem player you banned on the first. Copy the ban list. Copy the mod list. Point the hostname at the reality. The management tools page is the argument for not running the second one from memory.

Count the seats you actually sell

Write the cap, the reserve, and the public remainder on one line. A 100 slot server with 15 reserved is an 85 slot public server. Say that in the rules if people ask why the queue starts early. Hiding the reserve and then acting confused is how trust dies. Staff reserves are easy to defend. A long donator reserve on a small cap is a product, and it belongs in the hostname or the Discord in plain speech, not in a surprise at the connect screen.

Check the reserve list against the ban list every time you add a name. The failure mode is a banned player with a priority flag who walks in while the queue watches. CFTools Cloud is the place both lists should live so that comparison is one screen. Two files, two editors, and you will do it by hand until you miss. Missing once is the story people tell about your server on the roster.

Do not raise slots to clear a queue you have not measured. Look at the chart for a week. If the peak is 40 and the cap is 40, you are full because people like the server. The next step is a second process with the same mods and the same bans, or a calmer acceptance of the wait. The wrong step is a cap of 80 on the same CPU. The queue disappears and the simulation stalls, and the community page still shows a high player count of people who are not actually playing. They will stop being in the count by the weekend.

Password and reserve solve different problems. A password is a door. A reserve is a line. A server that needs both should say both. A server that needs neither belongs on the open list and should not pretend to be exclusive. Priority does not make a vanilla ruleset. It does not make your map official. It only orders the join. If you cannot explain the order in one sentence, delete the list and let the queue be fair. Fair is easier to moderate, and you already have enough to moderate.