Dr. McKay

The tag for accepting needs to be allow, not accept.

Don't call parentalUnlock until the callback of setCookies fires Don't try to send an offer until the callback of parentalUnlock fires

Yes, although you don't need to connect the CMClient before you log on with SteamUser. Just call client.bind(ip); and then you can immediately do user.logOn(details);

Not presently, no. If you want your own name and stuff, you can use the GetPlayerSummaries WebAPI method.

That's just how Valve does it. The classid/instanceid can also include some hidden data that isn't displayed in the actual item data, so you'll just have to live with whatever duplicates you get.

https://github.com/DoctorMcKay/node-steam-client#bindlocaladdress-localport

Yes, there is.

403s indicate that Steam has blocked your IP due to excessive requests. You need to slow down your request rate, or distribute it between multiple IP addresses.

You could try Codecademy to learn JavaScript, and Stack Overflow to ask your general JavaScript questions.

You can't just call webLogOn(), you need to call it as a method of a SteamUser object.

Show your code please.

You can't increase the "amount" of a non-stacked item. If you want to add multiple cases, you need to call addItem for each individual case object.

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

Sorry, but I'm not here to teach you JavaScript.

The region will be fixed when there's time to fix it.

There are pretty much two things you can do. Cancel unknown offers in unknownOfferSent and hope that the user doesn't accept it before you can cancel it (and if they do, fix it manually) Include some kind of internal identifier in the trade offer message and use that to track offers instead of (or in addition to) the offer ID

You're calling offer.accept for every incoming offer. You need to add some checks there to make sure it only accepts offers you want to accept.

Would you mind PMing me how you make this happen?

https://en.wikipedia.org/wiki/Indentation_(typesetting)

No, polling uses the WebAPI which isn't IP rate-limited. Hitting steamcommunity.com is what gets you limited (e.g. inventories).

Steam will automatically block your IP if you hit them too often, yes.

Use http://is.steam.rip/api/v1/?request=GetAllRegionData and ignore region 6.

You'll still get crashes if you aren't checking whether you're actually connected to Steam. Your socket hang up error is indicative of network issues on your end.

Your original code, which I sure hope has indentation.

That error is because your bot got disconnected from Steam and you tried to call webLogOn, which only works if you're connected.