Dr. McKay

Make sure everything is up to date and make sure your code doesn't create any timeouts with a timer of 2^31.

Steam doesn't slow any requests, it will only outright block you with 429. Your proxy just sucks.

It's spelled "length". And also itemsToReceive.

You're making too many requests. You need to limit your requests.

You would want to pass in a node-steamcommunity instance you've created and set the localAddress on.

If you could open an issue on GitHub that'll make me remember to add it.

For the moment you're going to need to scrape.

That's my bad. Update to 3.33.2 please. For future reference, if a module is throwing an error and crashing the application, that warrants opening a GitHub issue.

You can use node-globaloffensive.

All at once or on a delay?

This is a bad idea without some kind of limits and delay, or else if something breaks you'll just start DDoSing Steam.

Sure.

I don't see much of a need for separate forums right now.

Use the SteamID to pull their inventory from Steam to get the inspect link, then use that to get the wear.

That's more or less what you'd want to do.

https://github.com/DoctorMcKay/node-steamstore#redeemwalletcodewalletcode-callback

You should probably use offer.getExchangeDetails instead.

steam-tradeoffer-manager uses a steamcommunity instance for all its HTTP requests. If you pass in your own, then it'll respect that steamcommunity instance's options and such, and it will also set cookies on that steamcommunity meaning you don't need to do it yourself.

"Quit" and "relaunch" TF2.

Loop the array until you find what you're looking for.

https://github.com/DoctorMcKay/node-steamcommunity/wiki/CSteamGroup#joincallback

The removeFriend method will cancel/decline a friend request. You can't join groups through steam-user.

Private inventory.

It doesn't do what you think.

If you read the documentation a little closer, you'll see that all you need to do is give each a distinct logonID.