[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?