[node-globaloffensive] Connection to CS2 Game Coordinator times out

[diegob]

I'm working on a project where I need a bot to connect to the CS2 Game Coordinator, with the goal of eventually joining a game server. However, I've hit a wall that I'm hoping you can shed some light on.

The Problem: After a successful login with `steam-user` and setting `gamesPlayed = [730]`, the connection attempt to the Game Coordinator consistently times out. The `ready` event from `globaloffensive` is never emitted. We have tested this exhaustively on multiple accounts, networks, and PCs, with the same result.

Investigation and Root Cause: After extensive debugging, we believe the root cause is that the CS2 GC now requires an up-to-date `client_version` to be sent with the initial `ClientHello` message. Without a valid version, the GC appears to ignore the connection attempt, which leads to the timeout.

The Library's Limitation: Looking at the `globaloffensive` library, it seems there is no exposed option to pass a custom `client_version` during initialization.

My Question: Is our analysis correct? And more importantly, are there any plans to update the library to allow setting a dynamic `client_version`? Or is there perhaps a workaround or a different method to establish a GC session that we have missed? .

[Dr. McKay]

The latest version of globaloffensive is working fine for me. Do your accounts own a CS2 license?

[diegob]

Thanks for the quick response, Dr. McKay. Yes, the accounts we're testing with do own a CS2 license. We've tried this with several accounts, including a main account that has owned the game for years, and also a newer account. To be certain, we even used the `client.requestFreeLicense([730])` method from `steam-user`, and the callback confirmed that the license was already owned on every account we tested. That's why we are so puzzled. Even with the license confirmed, every single connection attempt to the CS2 GC times out, and the `ready` event from `globaloffensive` never fires. This behavior is consistent across different PCs and different networks. Is there any other common prerequisite for the account that we might be missing? For example, does the account need to have Prime Status, or have launched CS2 at least once manually via the official client? We appreciate you taking the time to help us debug this.

[Dr. McKay]

No, there's no other prerequisite. Were you previously using these accounts for something like requesting item data? I've heard reports of people having their accounts "banned" from connecting to the GC after doing so.

[diegob]

Thank you for that insight on GC bans. It was a very strong theory, but we have a confusing result that seems to contradict it. We ran the test one last time using a "clean" main account. This account has zero history of botting, scripting, or any automated activity – it has only ever been used for normal gameplay through the official Steam client. The result was exactly the same: a successful login, followed by a consistent timeout when trying to connect to the Game Coordinator. The `ready` event never fires. Since this happens even on a clean account, it suggests the issue isn't related to the account's *past* history. Is it possible that the GC now instantly flags any account that attempts a non-client login? Or is there any other subtle account requirement (like profile privacy settings, Steam Guard configuration, etc.) that could be causing the GC to silently refuse the connection? This is our final piece of the puzzle, and we're completely stuck. Any final thoughts you have would be incredibly helpful.