Dr. McKay

Need a lot more information. What are the specs of your machines? How many IPs do they each have? What will your bots be doing specifically?

If you're using the mobile authenticator then logging in from a new device doesn't have any trade cooldowns.

If you want some debug logging, then add: community.on('debug', console.log);

Always post the code. Nobody can help you with just that output.

Set a language and the objects in the arrays of items (itemsToGive and itemsToReceive) will have names in them.

Please post your code.

Probably, but I don't see what the use of that is.

You can confirm them automatically with https://github.com/DoctorMcKay/node-steamcommunity/wiki/Steam-Confirmation-Polling

Are you terminating the script between when you get the captcha URL and when you enter the solution? You can't do that, you need to prompt for the solution and then log on with the same SteamCommunity instance.

https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity#getconfirmationstime-key-callback

You can get the assetid of the item pre-trade from just the trade offer's data (the itemsToGive and itemsToReceive arrays). That data doesn't change ever. You can get the assetid of the item post-trade from getReceivedItems. There isn't any way to link specific items together between these arrays. You could use the market_name but if you for example have two items with identical names in a trade, there's no way to know which is which and so they can potentially get mixed up.

steam-tradeoffer-manager doesn't login to Steam, so consequently it doesn't have a sentry file. How are you logging into Steam?

You're absolutely sure that sentOfferChanged isn't being emitted? Is pollFailure being emitted every time debug is?

Just make a simple script that does console.log(SteamTotp.getAuthCode(shared_secret)); or something.

Polling is automatic, yes. It polls every 30 seconds. Can you add this and see what the output is? offers.on('debug', console.log);

Are you up to date?

Do you know which requests are triggering that event with those errors?

Check out the storehouse examples on GitHub.

16 is the only one I've seen that means that the offer is being accepted but is taking a while. As far as I know, once you try to accept it and you get that code, you can't decline it. FYI, autoRetry will be going away in v2. I'm also working on fixing accept error.

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?