WARDOGS error 1628505085: failed to initialize player session

If you came here for 1628505091, this is the wrong page. That code is one digit away and one step later — it fires after you clear the login queue, when you click a server and the join times out — and it has its own page: error 1628505091, join timed out, with launch night's record behind it. Everything below is 1628505085 and its two neighbours, which fire before you ever reach a server list.

This is the code a launch crush produces, and it is worth telling apart from the two it gets confused with. 1147405308 is a version mismatch and verifying files clears it. 1147405309 is the login service refusing you outright. 1628505085 is neither refusing nor mismatched — it is the online services failing to answer at all, which is why the wording is "failed to initialize" rather than "denied".

Our own report feed caught it arriving in two separate shapes on 21 August. The first block came between 15:32 and 16:08 UTC, roughly ninety minutes before Closed Beta 01 opened: players finished the tutorial, tried to go online, and hit it. The second came between 17:34 and 18:14, once the window was open and the queue had passed 400,000 — that one timed out at "fetching game data", and at least one player got through the queue only to be thrown back to the end of it. At 18:08 Bulkhead posted to Discord that the login queue was being hammered and that only a small number of players were logged in, which is the same event described from the other side.

The adjacent codes 1628505086 and 1628505088 belong here too. Both are worded as anti-cheat failures rather than session failures — 88 reads "Anti-Cheat could not initialize session correctly" — but they land in the same minutes and point at the same backend. 1628505088 arrived three times in our report feed during Closed Beta 02, from 4 September onwards, and the most thorough of those reports had already flushed DNS, reset Winsock, restarted the router and moved to a wired connection with no change. That is what a server-side fault looks like from the client.

Unlike the permission errors, this one is not a closed-beta artefact. The condition that produces it is load, and the load arrived on schedule: Early Access opened to everyone at once at 16:00 UTC on 10 September and WARDOGS peaked at 337,157 concurrent players, against the 105,774 of the beta that produced everything above.

What filled this site's feed that night was the step after the queue rather than the step before it — the join code, at the moment of joining a server — and Bulkhead's Launch Stability Hotfix #1 at 20:20 UTC named that symptom rather than this one. So the steps above remain what they were, which is the beta's evidence, and they still describe what 1628505085 is. If you are on the launch-day code, the join page is the one carrying the launch-day record.

1628505084 lands here as well. Its wording is different — "Game Data Unavailable: could not retrieve the latest game data from the game service" — but it is the same step failing: the client asking the backend for your account and getting nothing back. On launch day it arrived at 18:10 and 18:29 UTC for players who had just been removed from a match around the half-hour mark, posted to Team17's pinned login-issues thread. It came back on 14 September, the day Patch 0.11 went in, and one player had it all day through a full reinstall.

On the same day another player reported clearing it by verifying the game files: Steam → WARDOGS → Properties → Installed Files → Verify integrity of game files. Both reports can be true. If the code arrived with an update, a file check repairs a mismatched install; if it arrived with a load spike, nothing on your machine changes it. Verify once, then retry rather than reinstall.