Dr. McKay

var client1 = new SteamUser(); var client2 = new SteamUser();

https://github.com/DoctorMcKay/node-steam-user#chatmessagerecipient-message-type

You'd need two of whatever you're using to login too.

No, I mean you need to do new TradeOfferManager twice.

No, you'd need to create two separate TradeOfferManager objects.

No, that shouldn't be possible.

offer.getUserDetails(function(err, me, them) { if (err) { throw err; } if (them.escrowDays > 0) { offer.decline(); } });

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

In the callback, provided it was successful, the offer's data will be updated and you can just run your logic there. But no, it won't arrive in newOffer again once it's emitted once.

You also realize that in order to join a VAC-secured server, you'll need to implement VAC? And that you'd be fully insane to try to implement VAC.

You realize that you'll need to implement the game server's protocol yourself, correct?

That is currently not supported. What do you need it for?

https://github.com/DoctorMcKay/node-tf2#backpack

You don't have to buy games. Just adding $5 to your wallet is sufficient.

You can use node-tf2 to get and craft your inventory.

You could use update.

You're saying that sometimes newOffer isn't emitted for an offer?

It's not really recommended to manipulate poll data. TradeOfferManager's job is to emit newOffer once per incoming offer. Errors can be frustrating but it's your responsibility to make sure that they're dealt with properly. You could use offerList to check for offers that should have already been accepted (probably want to keep a list of offers you've attempted to accept and the timestamp so you don't try to accept an offer too frequently).

Spamming threads won't get you (free) help any faster.

That's known as spam, and I won't help with it.

Up to you. Maybe make sure key and metal aren't 0.

You have two threads. Why?

You aren't assigning anything to BuyKey and FromRef1. forEach doesn't return anything. Also, further on down you're using = when you want to use ==

What's with the nested listeners on newOffer? And on separate emitters?

Why are you constantly using commas when you mean to use &&?