Dr. McKay

It's a velocity rate-limit. Something like 20 or 30 requests per minute it seems. I'm not sure about specific numbers. Yes, you should absolutely cache inventories on your end. The actual duration is up to you, and it really depends on what you're using the inventories for. Pretty much just find someone who sells cheap VPSes with cheap IP addresses No, I've tried several things and requesting from the client isn't possible without some kind of user script or browser extension

Looks like Steam isn't updating the WebAPI data quickly enough now. Are you getting that error every time, or just sometimes?

If you're using the mobile authenticator (which you should be for trading) there isn't a new device cooldown.

You'll get double callbacks.

Yes, that should work.

Is your clock right?

Round peg, round hole.

Yes.

No, but there's no reason not to.

http://stackoverflow.com

Yes, Steam changed it some time ago so that you can't get more than I think 5000 or so changenumbers behind. I suppose I should update that documentation.

Use update. That will update the offer from the API. offer.update(function(err) { if (err) { console.log(err); } else { // now the offer is fresh from the WebAPI } });

readFile gives you a Buffer, not a string. You need to stringify it using toString('utf8').

That's normal. As of version 3 (if I remember correctly), npm flattens dependencies by putting them all in the first-level node_modules where possible. This both helps to avoid duplicate installations, and prevents issues where paths get too long.

I don't believe you could do that without editing the module's code directly. If you run the bot and send an offer manually, it'll trigger unknownOfferSent.

It might be a better idea to throw a more descriptive error, but the behavior is pretty much undefined for calling any method (except for offline ones like settings and logon) while logged off.

You should use the API to get details about trade offers. Scraping the sent offers page is asking for trouble. Also, there's a getOffersContainingItems method in the latest version anyway.

Why are you scraping your sent offers page?

If you're getting a "Not Logged In" error, then you're not logged in and you should relog.

The only way I was able to reproduce this was by trying to log off without first being logged on. Please make sure you aren't doing that.

Yes.

You can either use steam-totp with your shared_secret to provide the code to logOn as twoFactorCode, or you can use a loginKey. Both of these are documented on the readme.

Sure, add a bad item to the offer.

Send and receive offers using what? steam-tradeoffer-manager?