Dr. McKay

You can do this with steam-session.

What do you receive error 15 in response to? How are you receiving it?

https://steamerrors.com/5 Sounds like you aren't logging in correctly.

Only one Steam client session can be in-game at a time or else you get the LoggedInElsewhere error you mentioned. That guy isn't running CS2 on the same account twice; the real game instance must be logged in under a different account. No.

Does the app in question actually use encrypted app tickets?

The first argument to webSession is sessionID, not cookies.

Sounds like you have some network issue.

Most methods don't work if you log on anonymously. getPersonas probably isn't one that does.

Doesn't look like you're doing anything wrong from those login options. The IP you're logging in from is probably just really suspicious.

You can see exactly what's happening internally if you add a debug listener like so: user.on('debug', console.log)

No.

Thanks for the info. This is caused by CS2 inventories that have items, but which have no items that are actually visible. The returned data looks like garbage because Valve. steamcommunity 3.48.5 fixes the error, instead returning an empty array. As of steam-tradeoffer-manager 2.11.7, you can use the deprecated TradeOffer.loadPartnerInventory() method to get those CS2 items.

Are you enabling useAccessTokens?

Yeah that should work fine.

Could you PM me the trade URL?

No, you can't get original_id for an item that's listed on the market.

Game developers don't implement VAC; the Steam client takes care of that fully. Game devs just opt into using it, at which point the Steam backend starts sending modules for the Steam client to execute properly and return responses for.

You would need to implement the client side of VAC, in its entirety, flawlessly. Good luck!

If api.steampowered.com is merely unreachable, I think autoRelogin should keep retrying. In this case, DNS resolution failed which should never happen unless your network is down.

Are you sure it's fatal and crashing the process? Looks to me like you're handling the error event as expected, not reconnecting, and the process exits as it should since there's nothing more on the event loop. autoReconnect does not apply for disconnects which emit the error event. In those cases, you're responsible for reconnecting manually.

Yes, that should work. I'd recommend some debouncing to ensure that you don't spam-call webLogOn if multiple sessionExpired events are emitted quickly.

Yes, you cannot call enableTwoFactor if the account already has 2FA enabled elsewhere, whether through the app or some other script.

I'm not aware of autoRelogin being broken in any way. Web sessions are completely independent of CM connections. When steam-user is "connected", that's a CM session. A web session is negotiated through the CM session, but they're entirely separate. Web sessions are never automatically renewed by steam-user; that responsibility falls onto you.

Right, that's a web session, not a client session. When you log in to the client using steam-user and receive a webSession event, that's a web session that's started through the client. Those web sessions expire independently of the client session, and you do need to call webLogOn() occasionally to get a new web session.

That's not a thing for CM (Steam client) connections. What's the actual symptom you're seeing?