Dr. McKay

As far as I'm aware, there's no limit of accounts per IP, but there is a rate limit for logon attempts per IP. As long as you don't get rate limited, you should be good.

That's just the GC being slow. It's a complete mess in CS:GO. CM stands for connection manager.

True, though I wouldn't worry too much about it personally. I don't have any plans at the moment for steam-user v5. Be aware that refresh tokens expire after 200 days and I've yet to see a way to refresh them, so you will need to re-auth with your password after that time.

https://github.com/DoctorMcKay/node-steam-user#steamguard

I don't see that anything changed on how the request is made to Steam, so probably a temporary Steam issue. How long has it been going on?

I also commented this on your issue: The first argument to loggedOn is a CMsgClientLogonResponse object, not a login key. You get a login key from the loginKey event.

Might've been a temporary Steam issue. It's working fine for me.

Yeah, just store your SteamCommunity and TradeOfferManager objects in global variables.

That's not a good idea. Steam will invalidate your session if your IP changes too much.

If steam-user connects with a WebSocket, it sends pings automatically every 30 seconds and disconnects (and emits the disconnected event) if Steam doesn't reply. If you want to make sure that the pings get sent, you can force the connection protocol using the protocol option. Example: let user = new SteamUser({ protocol: SteamUser.EConnectionProtocol.WebSocket });

steam-gameserver hasn't been updated a ton, but it does still work. You're better off using that than hacking steam-user to login as a server.

If it's possible, then yeah I'll figure out how to make it happen. As far as I'm aware, right now you can't use a sentry file with the new login system.

Ah, my bad. The version with proxy support isn't published to npm yet. I'll go ahead and yolo it.

let session = new LoginSession(EAuthTokenPlatformType.SteamClient, {httpProxy: 'http://127.0.0.1:8888'}); let startResult = await session.startWithCredentials({ accountName: '...', password: '...', steamGuardCode: generateAuthCode('...') }); Works fine for me. What does your proxy variable look like?