Dr. McKay

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.

Maybe your proxy's IP doesn't geomap to the country you expect.

Could you be more specific? Everything looks fine on my end.

Your uploaded image is broken.

No.

You'd also need to set a cookie on the login.steampowered.com, with name steamRefresh_steam and value equal to <your 64-bit steamid>%7C%7C<your refresh token>

I'm not able to reproduce this using your code. Error reading file machineAuthToken.somelogin.txt: ENOENT: no such file or directory, open 'C:\Users\-\AppData\Local\doctormckay\node-steamuser\machineAuthToken.somelogin.txt' API GET request to https://api.steampowered.com/ISteamDirectory/GetCMListForConnect/v0001/?format=vdf&cellid=12: 200 Randomly chose websockets server ext2-atl3.steamserver.net:27023 (load = 31, wtd_load = 22.909419059753418) [W1] Connecting to WebSocket CM ext2-atl3.steamserver.net:27023 [W1] WebSocket connection success; now logging in Logging on with account name and password; fetching a new refresh token Sending message: ClientHello Sending message: Authentication.GetPasswordRSAPublicKey#1 [W1#1] Handled message: Authentication.GetPasswordRSAPublicKey#1_Response Sending message: Authentication.BeginAuthSessionViaCredentials#1 [W1] WebSocket disconnected with code 1000 and reason: [W1] Connection closed, but message queue is active. Enqueueing __CLOSE__ [W1#2] Handled message: Authentication.BeginAuthSessionViaCredentials#1_Response [W1] Handling connection close steam-session startWithCredentials exception Error: InvalidPassword at eresultError (D:\Libraries\Repos\Node Modules\Steam Handlers\steam-user\node_modules\steam-session\dist\helpers.js:14:15) at AuthenticationClient.sendRequest (D:\Libraries\Repos\Node Modules\Steam Handlers\steam-user\node_modules\steam-session\dist\AuthenticationClient.js:242:46) at async AuthenticationClient.startSessionWithCredentials (D:\Libraries\Repos\Node Modules\Steam Handlers\steam-user\node_modules\steam-session\dist\AuthenticationClient.js:77:22) at async LoginSession.startWithCredentials (D:\Libraries\Repos\Node Modules\Steam Handlers\steam-user\node_modules\steam-session\dist\LoginSession.js:361:38) at async D:\Libraries\Repos\Node Modules\Steam Handlers\steam-user\components\09-logon.js:439:26 { eresult: 5 } Handle logon response (InvalidPassword) Disconnecting without sending logoff [W1] We wanted to end connection, but it's not connected or connecting error: InvalidPassword

No publicly-known method.

You're probably getting IP rate limited.

You can't, neither of these work anymore.

Sounds like your proxies aren't standards-compliant HTTP proxies.

The GC just isn't sending any data for those values.

That's probably a bug in your code. steam-user does not attempt to login again if the error event is emitted.

If steam-user emits the error event, it's no longer attempting login. You can consider the error event to indicate a fatal error that has resulted in steam-user ceasing all operations unless you call logOn again.

Either listen for steamcommunity's sessionExpired event and then call webLogOn(), or set up a timer to call webLogOn() periodically. Hourly works good for me. webSession is the correct way to listen for new cookies. The Steam backend doesn't proactively send you new cookies when your session expires; it's up to you to request new ones.

I'd need to see the actual error message to help you, but my suspicion is that you need to update node.

You can do this with steam-session (see example), but not with steam-user only.