The WARDOGS Login Queue

What the developers have confirmed

On 10 September, developer G_Medlin posted Launch Stability Hotfix #1 on the official Steam discussions. It names three problems the hotfix targets: players unable to join servers, players being unexpectedly kicked from servers during play, and extended login queue times.

The same announcement explains the mechanism players found confusing. Applying the hotfix forced every logged-in player to restart, download the client update and return to the queue — which is why some people who were already in a match found themselves back at the end of a line.

The controlled-batch approach is the important detail. The queue is not simply draining at whatever rate the servers allow; the team is holding the rate down on purpose and raising it as stability is confirmed.

Why leaving and rejoining makes it worse

Your place in the queue is held by your session. Closing the client and reopening it does not refresh a position, it surrenders the one you had and requests a new one at the back.

This is the single most expensive mistake during a launch queue, because the cost is invisible until you are already back at the end. If the number is moving at all, it is working.

The same applies to verifying game files, reinstalling or switching regions while you are waiting. None of those touch the account service that is actually rate-limiting you.

A queue position that appears frozen for several minutes is not evidence of a failure. Admission happens in batches, so the number moves in steps rather than continuously.

Telling the queue apart from a real error

A queue shows you a position and a wait. An authentication failure shows you an error code instead, most commonly 1147405308, and drops you back out rather than holding you in line.

That distinction decides what to do next. A queue needs patience; an error code means the login request reached the service and the service failed to process it, which is a different fault with its own guide on this wiki.

Being disconnected mid-match is a third case again. The hotfix explicitly lists unexpected kicks as a separate bug from the queue, so a mid-match removal is not you losing your queue slot.

What BULKHEAD has not published

There is no official figure for how long the queue takes. No target wait, no throughput rate and no published position-to-minutes conversion exists, so any specific number you see quoted is a player estimate rather than a developer statement.

There is also no official priority mechanism. Nothing in the announcements describes a paid queue skip, a Supporter Edition advantage or a regional fast lane, and this page will not repeat community claims that one exists.

The team has not said when the throttle comes off entirely. The stated approach is incremental, tied to observed stability rather than to a date.

Queue questions answered

Short answers to the most common queue problems.

• Is the WARDOGS queue matchmaking or login? — Login. It is a queue for the account service, before any server is chosen.
• Does restarting the game speed it up? — No. It gives up your position and puts you at the back of a new queue.
• How long is the queue? — No official figure has been published. BULKHEAD admits players in controlled batches and raises the rate as stability allows.
• Why did I get sent back to the queue mid-match? — The launch hotfix forced all logged-in players to restart and update, which returned them to the queue.
• Can I pay to skip the queue? — No queue priority of any kind is described in the official announcements.
• Is a stuck position number a bug? — Not by itself. Admission is batched, so the number advances in steps.