node-globaloffensive: cant connect to steam GC
[steam][ownershipCached] Already own CSGO
[steam] Sending message: ClientChangeStatus
[steam] Sending message: ClientGamesPlayedWithDataBlob
[steam] [W1#17] Handled message: ClientPersonaState
[steam] [W1#17] Handled message: ClientPersonaState
[steam] [W1#18] Handled message: ClientPlayingSessionState
[steam] [W1#18] Handled message: ClientGameConnectTokens
[steam] Received 1 game connect tokens. Had 10 tokens.
[steam] [W1#18] Unhandled message: PlayerClient.NotifyLastPlayedTimes#1
[steam] [W1#19] Handled message: ClientPersonaState
[csgo][debug] Sending GC message ClientHello
[steam] Sending 730 GC message 4006
[steam] Sending message: ClientToGC
[csgo][debug] Sending hello, setting timer for next attempt to 2000 ms
[steam] [W1#20] Unhandled message: ClientServersAvailable
[steam] [W1#21] Unhandled message: ClientServiceCall
[steam] [W1#22] Handled message: ClientFromGC
[steam] Received 730 GC message 9187
[csgo][debug] Got unhandled GC message 9187
[csgo][debug] Sending GC message ClientHello
[steam] Sending 730 GC message 4006
[steam] Sending message: ClientToGC
[csgo][debug] Sending hello, setting timer for next attempt to 4000 ms
[csgo][debug] Sending GC message ClientHello
[steam] Sending 730 GC message 4006
[steam] Sending message: ClientToGC
[csgo][debug] Sending hello, setting timer for next attempt to 8000 ms
[csgo][debug] Sending GC message ClientHello
[steam] Sending 730 GC message 4006
[steam] Sending message: ClientToGC
[csgo][debug] Sending hello, setting timer for next attempt to 16000 ms
when i try to login do csgo using node-user and globaloffensive packages my script gets stuck in this loop of sending hello this started happening after the recent csgo update, i tried different accounts, different IP addresses and so on nothing is working
About this issue
- Original URL
- State: closed
- Created 5 months ago
- Reactions: 1
- Comments: 20 (1 by maintainers)
https://github.com/DoctorMcKay/node-globaloffensive/blob/master/index.js#L120
changed to
After I can login
But interesting thing, after I logged in with version: 2000202 all works fine without version: 2000202
Fixed in 3.0.1.