Dr. McKay

I have no idea what's up with the crafting event, but unless you're emitting it yourself you shouldn't be using it. You don't need to specify any appid or contextid (there is no such thing as a contextid outside of the Steam econ server). node-tf2 knows what TF2's appid is. You need to pass an array of item IDs to craft.

You only need to set up your trading code to not accept overstocked items.

https://httpstatuses.com/429

Why are you editing the library's code? Don't do that.

The documentation is pretty clear about how to add an item by assetid: https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOffer#addmyitemitem

You can't try to send the offer until the callback of webSession. Please read up on asynchronous JavaScript and callbacks.

There are some examples in the examples directory that may help: https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/tree/master/examples

I don't provide Steam support. I suggest that you take some JavaScript lessons, as I'm only here to help with library integration questions, not with JavaScript basics. You may want to look at Array.prototype.map perhaps.

That's up to you. Look at the contents of backpack and find what you're looking for.

The assetids are available in your backpack.

The order of your inventory and err arguments is wrong. Order matters. Also, you might try printing the error if one occurs for more insight.

This may help: https://sporto.github.io/blog/2012/12/09/callbacks-listeners-promises/

Have you added a phone number to your account?

Yes, and no.

Yes, that looks correct enough, minus the secrets.

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.