Dr. McKay

Yes, those codes will work anywhere you sign into Steam.

Déjà vu.

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOffer#properties itemsToReceive

My mistake. I've updated those release notes. Get rid of the curly braces inside your SteamUser constructor: new SteamUser(steamclient). If you do it properly, all communication SteamUser does with Steam goes over the proxy.

The user event will be emitted anytime someone's persona data changes (e.g. they go online/offline or start/quit a game). Also, at any time the users property contains the current persona data for everyone we know about.

It's setHttpProxy, not setHttpSocket.

Your IP got temporarily banned, yes. That's what 429 means.

https://httpstatuses.com/429 Slow down.

Yes, it's printing "Error: Logon failed, Invalid Password or playing in the account." because you're printing that unconditionally when an error occurs.

offer.getExchangeDetails(function(err, status, tradeInitTime, receivedItems, sentItems) { console.log("Trade status is " + status + ", init time " + tradeInitTime + ", and we received " + receivedItems.length + " items and sent " + sentItems.length + " items."); });

You need to wait for this event: https://github.com/DoctorMcKay/node-steam-user#friendslist Also, the problems I see with your code are that err doesn't exist, and that you're only sending back the friends list if it's falsy (which would never result in sending back the friends list).

Is the bot online?

How to buy what, a bot? Nobody is selling bots here.

Doesn't look like TradeOfferManager is defined. In the future, please include any error messages and stack traces.

You can't.

Experiment and find out. 2-3 seconds should probably be enough but I'm not positive off the top of my head.

It will recheck it automatically to see if its status changed. There's no way to specify that something should happen if its status doesn't change after a certain time; you'll need to handle that yourself.

No need to regenerate your secret; just stop using the phone.

Try again later, and listen for receivedOfferChanged to see if it goes accepted later.

This code should work if you aren't using two devices, yes. You need to never try to load confirmations on your phone or elsewhere or else there will be problems. Specifically, there's a device ID that's sent to Steam when loading the confirmation list and if Steam sees different device IDs, then it has problems.

You can use this; it tells you how many items you have for each inventory.

Yes, that's a problem. Confirming trades on two separate devices makes them randomly not appear.

10,000, 1,000, and variable.

Are you saying that you have the secret on your mobile device as well, in addition to on the server?

It doesn't look like you're renewing your web session. You need to call client.webLogOn() when it expires (listen for sessionExpired on your SteamCommunity). It also doesn't hurt to call it periodically, say every hour.