Dr. McKay

That login route is outdated and doesn't work anymore. Logins are handled by steam-session these days.

If there's a request outstanding when you call logOff(), it has to wait for the request to timeout before the Node.js process can exit. There's a bunch of requests that get made internally when you first log on; you're better off waiting a second or so after loggedOn is emitted before calling logOff(). In the future I'll try to add a mechanism to cancel outstanding requests when we log off, but it's not quite as simple as it first sounds.

No, you'd have to register one using the web page at https://steamcommunity.com/dev/apikey or node-steamcommunity's createWebApiKey method. If you're calling methods that aren't account-specific (e.g. GetPlayerBans returns the same data for everyone, nothing is specific to your account) then you could register one API key and use it for everything, but I don't know if that meets your specific needs.

Not really. Some WebAPI methods allow you to use an access token (which is the same as a steamLoginSecure cookie without the SteamID prefix), but not all. GetPlayerBans is not an API method that accepts an access token, so you do need an API key for that.

Yeah, that looks fine. But ordinarily it shouldn't ever be possible for your SteamUser client to disconnect without you being aware of it, since the error event will be emitted.

So you're using steam-user? You can check if the steamID property is set to a non-null value, which will indicate that you're still logged in. But from the sound of things, you're running into expired cookies. Your web session cookies expire from time to time and need to be refreshed using steam-user's webLogOn() method.

It depends on how you're logging into Steam.

I've messed with this in the past and I think the status key is only paid any attention if you're actually authenticated in a game server.

I see. I can't give you an estimate as to when I'll be able to add this, if ever. You may want to maintain your own fork of steam-user or use SteamKit for this.

This isn't supported. Why do you want to connect to a specific CM?

There was a bug in 5.0.7 that made SteamUser automatically reconnect after you call logOff(). I suppose it's possible that this contributed to your issue. You might have a bunch of zombie processes running in your stateless environment. I don't know your environment, but see if there's some way to kill everything.

Thanks for the info, fixed in 5.0.8.

I don't see anything wrong with your code, but I also can't reproduce the issue myself on the latest v5 version. Multiple sessions on the same account with differing logon IDs are working fine.

Yes, you can do it with steam-session. https://github.com/DoctorMcKay/node-steam-session/blob/master/examples/login-with-qr.ts

No, automating the market is a violation of the Steam TOS and isn't a supported use case.

npm update

GetAssetClassInfo can be called for multiple items at a time. You could also cache the result since the same classid+instanceid combo will always have the same description.

I'm familiar with what lancache is and how it works. If you want hashes of chunks, SHA1 hashes of every chunk is in the manifest. I'm not really seeing how downloading files through a lancache will help you to hash them, but your project is your business. Adding lancache support is pretty simple, but validating that it works is a little less so since I'll have to set up a cache server to test with.

That would be possible, though I can't imagine there's too many people who would actually make use of this. Do you have a personal use case for that?

Listen for the sentOfferChanged event to see if an offer was accepted. Trade offers cannot be modified so you don't need to worry about checking if it was changed.

That's still correct for CS2.

I don't believe the JWT public key was ever published.

You don't need a key to decode it. It's just a JWT.

I don't know why you'd have requests fail, but you could always call setCookies separately with the value you want for steamCountry.

I don't have any special insight into what account flags mean.