WARDOGS Queue Not Moving? Join Timeout & Server Checks

If a crash is followed by login that never finishes

A recent player report, reviewed 13 October, describes a crash followed by endless logging in. The poster had already tried verification, reinstalling and restarting without success. Its exact posting date and client Build were not verified, and the visible replies do not confirm a repair.

Treat the crash and the following login wait as two failure stages, not proof of a full selected server or the separate 1/6-counter case. Save the original error using the crash guide, then note whether the login reaches the menu at all. Check current official notices and pending updates before one normal retry. If it still hangs, send both stages, region, time zone and visible Build to support; do not repeat an already unsuccessful reinstall or present a forum logout suggestion as a confirmed fix.

This page is for queues, not a character stuck in a match

If you already reached a match and your character cannot move around a map object or building, use the character-stuck guide. That is an in-match movement report, not evidence that a login or selected-server queue is frozen. This page stays focused on waiting before the menu, after selecting a server, or at a join timeout.

Stuck in the WARDOGS queue? Start with the waiting stage

Before changing settings, identify where the wait begins. A queue before the main menu is a login-stage symptom; a queue after choosing a server is a match-join symptom. Check for a pending update and a newer official notice, then make no more than one normal retry unless that notice tells you otherwise.

There is no verified maximum wait time or supported queue bypass here. An unchanged number is an observation, not proof that the queue is broken.

Follow the wording in your installed client. We have not independently inspected its current queue UI or measured its refresh interval.

What the launch hotfix means

The 10 September official hotfix notice told players to update, re-enter the login queue and wait for admission in batches. A queue after that update was therefore not, by itself, evidence of a broken installation.

That was a dated rollout instruction. Check newer notices before applying it to a later session.

Still queued? Check current information first

The developer’s 14 September maintenance thread reports recovery after that event. It is historical context, not a current server-status check. Do not keep waiting for its old maintenance end time, and do not assume that announcement reserves a place for you.

1. Check Steam Downloads for an unfinished update and check newer service notices.
2. Note whether you can reach the menu. If you cannot, record a login problem rather than a particular match server being full.
3. If you can select a server, record its name or visible ID and the exact queue or error message. Use the browser checks if filters are hiding alternatives.
4. If the game closes instead of waiting, move to the after-update crash checks. Repeatedly rejoining a queue will not diagnose a process that crashes.

This is a diagnostic sequence, not a measured waiting-time rule. Queue size, another player’s successful login and a general recovery notice cannot predict your wait. Community priority queues were still listed as upcoming in the Patch 0.11 notice; this guide does not recommend paying for an unverified bypass.

Decide whether to wait or retry

1. An applicable official incident or admission notice exists: follow it. Changing graphics options will not increase login capacity.
2. Position changes and the interface responds: keep observing unless you choose to leave.
3. Position stays unchanged but the interface responds: record two observations with timestamps. We cannot infer a timeout from the number alone.
4. An explicit error appears: save it. Check for a pending client update, then consider one normal exit and relaunch if no official notice says otherwise.
5. The process stops responding: attempt a normal close. Ending only the game process through Task Manager is a last resort and abandons the session.

We cannot promise a restart preserves your position. Repeated restarts also erase the timeline needed to distinguish progress from a new session.

If a selected server is full

Use whatever capacity information your build displays. You can choose a different suitable server, but we cannot guarantee any particular slot will be available when you join.

If the list is empty, use the browser guide. If the game displays a refusal rather than a queue, use Access Denied checks; do not reinterpret an unknown code as “server full.”

A useful queue report

Record the client and visible version, region, time joined, queue wording, position changes, whether the menu responds, and the final outcome. Add the selected server only if you reached that stage.

There is no supported queue bypass offered here. Do not install modified clients, delete shared services, or pay for a “priority” connection based on this guide.

Dated community report: a full server or a 1/6 counter loop?

On 6 October 2026, a Reddit discussion included a player report that a 1/6 counter remained after they cancelled and switched. That is one player’s observation, not proof of a widespread queue incident or a confirmed cause. Do not treat the report as live server status.

Keep two symptoms separate: a selected server that the current client identifies as full is a capacity message; a counter that remains at 1/6 after cancelling or switching is a reported interface/queue symptom. We have not reproduced either behavior in the current client. Check current official notices, then record the selected server (if shown), region, time and time zone, exact counter/message, and what happened after the cancel or switch. Do not infer a platform, network or attack cause from the counter alone.