Launch Stability Hotfix #1
OVERVIEW
WARDOGS announced a small client hotfix on 10 September 2026 after launch issues. The post said logged-in players would restart, download the update, return to the login queue, and be admitted in controlled batches while the team monitored entry to the servers. This page records the announcement as checked on 13 September; it does not certify the current queue or server state. On 12 September 2026, BULKHEAD followed that launch hotfix with “SCHEDULED MAINTENANCE & PATCH 0.11”. The post schedules about one hour of downtime on 14 September to improve the server browser, while tying the announcement to the 400,000 Peak Concurrent Users milestone. This is a dated plan, not a report of the current server state. The Steam post was updated on 14 September 2026. In its current body, the maintenance table lists China at Monday 16:00; an earlier saved copy grouped China and Taiwan, so this page follows the current official wording.
HISTORY
The notice followed the Steam Early Access launch. Its sequence was operational: restart, install the client update, rejoin the queue, then allow players in gradually after confirming that they were entering and populating servers successfully. The listed targets were failed server joins, unexpected kicks during play, and extended login queues. The team said it would monitor the situation through the night and apologised; the post did not publish a later result. The follow-up is more specific than the first hotfix. It splits the browser into Community and Official views, removes unnecessary Official filters, improves Community filtering and text search, keeps server IDs across matches and restarts, adds Show Empty/Full, and corrects the Host button. It also says cash exploits and more GPU crashes were addressed, Asia capacity was increased, and community servers would carry a 5% End of Match cash bonus for the next week. This is a source correction, not a new maintenance window. The announcement remains dated 12 September, but its official body was updated on 14 September; the current regional row says China, Monday 16:00. The current text does not give a Taiwan time in that row.
WHAT IT CHANGES IN PRACTICE
If you want to understand what the launch process was meant to do, this notice gives the sequence and the symptoms it was intended to address. It is useful as a dated explanation of the restart and queue procedure, not as a current support instruction. For today’s wait times or whether a problem is fixed, use a current official status source; this article does not turn historical directions into a present guarantee. Use this as the dated maintenance and patch plan, not as proof that the servers are currently up or that every listed future feature is already live. The announcement says community server favouriting, tiered priority queues, MOTD prompts, warmer warmup activities, seeding AFK controls and team-switching controls are still in the pipeline. It gives planned maintenance times rather than a completed result. Use the current Steam post for the regional timetable. Treat China at Monday 16:00 as the publisher’s current row, and do not assign a Taiwan time unless a later official source names one. The update changes the wording of the table, not the announced one-hour maintenance duration.
WHAT PLAYERS GET WRONG
Do not read the release of a client update as proof that every launch problem ended. The announcement describes its intent, procedure, symptoms and monitoring plan, but gives no uptime measurement, queue length, admission rate or later confirmation. Hotfix #1 is the publisher’s title; it does not establish a permanent fix. Do not turn “400,000 Peak Concurrent Users” into a permanent active-player count, and do not treat a planned one-hour maintenance window as proof of uptime or a completed fix. Keep the announced 5% community-server bonus and the future feature list separate from features already shipped; only the immediate browser changes and stated fixes are described as delivered by this post. Do not treat the 14 September edit as proof that maintenance finished or that the servers are available. Do not carry the older China-and-Taiwan grouping into the current table, and do not infer a Taiwan time from China’s 16:00 row.
THIS ENTRY WAS LAST CHECKED 14 SEPTEMBER 2026