Dr. McKay

Do you know where exactly that error is coming from?

You likely do need to set the proxy on your steam-user instance as well.

Unfortunately, the data received from the GC (what you get via node-tf2) is incredibly messy and there's like a dozen conditions you need to check to see whether an item is untradable/uncraftable. It's probably not worth your time doing and you should probably just pull that data from the web instead, but if you really want to, a starting point is that a few conditions that determine uncraftability is a flag in the flags field, an "achievement" origin, a "tradable after date" attribute, and a "never tradable" attribute. That's not an exhaustive list though.

That looks correct, just uncomment your "community": community line.

You're rate limited. You're making too many requests somewhere.

That's a good point on the already logged on error, although for the others I don't really think it's worth being concerned about. It should not be possible to be missing a CM list since it's retrieved from the WebAPI and the library falls back to a bundled list if that fails. I'll see about making it possible to handle the already logged on error.

received = received.filter(offer => offer.state == TradeOfferManager.ETradeOfferState.Active)

Just filter the list to only active offers.

manager.on('sentOfferChanged', (offer, oldState) => { // This is the callback // offer.id is the ID of the trade offer that changed });

No, that kind of thing would be a trade secret I'd imagine.

Sure, have fun with that.

If you're already keeping track of offer IDs paired with discord user data, then you should just have one sentOfferChanged handler and check the offer.id inside of that callback.

Sounds about right.

Call the accept method.

You should only have one sentOfferChanged handler. You should not add a new handler every time you send a trade.