You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
When the server is down steam-install of zero-k takes an abnormally long time to launch when networking is turned on. #931
myself and at least 2 other report abnormally long startup times on linux durring the unprecedented server downtime. I'm guessing because there's a 120 second timeout after attempting to ping the server before launching recoil.
The wait is in the launcher (Zero-K-Infrastructure), not in Chobby. Before it starts the engine, also for Steam, it loads community news from the server (ChobbylaHelper.cs:76) with no time limit of its own. In a test of that code on Mono, a server that does not answer held the start for 100 s, and a dropped connection for about 134 s. With networking off the call fails at once, so there is no wait. ZeroK-RTS/Zero-K-Infrastructure#3072 stops this wait after 10 s.
Activity
moss-orbit-9f339e commentedon Nov 2, 2026
The wait is in the launcher (Zero-K-Infrastructure), not in Chobby. Before it starts the engine, also for Steam, it loads community news from the server (
ChobbylaHelper.cs:76) with no time limit of its own. In a test of that code on Mono, a server that does not answer held the start for 100 s, and a dropped connection for about 134 s. With networking off the call fails at once, so there is no wait.ZeroK-RTS/Zero-K-Infrastructure#3072 stops this wait after 10 s.
Found and tested with Claude Code.