Dr. McKay

The way you've used it looks correct to me (although you probably want to console.log that err). I'd need to see more (like more of the error).

No, there is no error handling or timeout built into the module; you will need to handle that on your own. The async module may help you, specifically async.queue.

This may help you: https://dev.doctormckay.com/topic/365-cookies/

A few things: Colors are only useful in console.log output. You cannot and should not use them in offer messages. You should not be using the confirmation checker. I suspect you're being rate-limited because you're using it twice with a relatively low poll interval. Instead, use community.acceptConfirmationForObject as needed (in the callback to offer.accept(); check the status). It is not safe to start sending an offer until the callback to manager.setCookies fires.

If that's supposed to be an error, you've cut off most of the useful part of it.

No, and that probably never will be possible.

Read the docs; set a language in the constructor.

getExchangeDetails.

If your system clock is wrong, that will definitely cause errors.

Load your inventory and find an item with matching classid and instanceid, then add it to the offer.

There's a problem with your network.

It's not strictly necessary. It's (in my opinion) the best way to login to Steam and get cookies (and as a benefit you can easily appear online and get real-time trade offer notifications), but it's not the only way.

You don't, it happens internally.

The different modules are good at different things. steam-user only handles communication with the Steam CM servers. Confirmations don't go through those servers, so you need steamcommunity for that. In my opinion, you should use steam-user, steamcommunity, and steam-tradeoffer-manager for the most robust system.

If you're saying that your problem is that it isn't prompting for an email code and is instead logging directly in, that's on purpose. It saves the sentry file (which, if provided in logon [which it does automatically], you don't need an email code). If you need to prompt an email code request, you can delete the sentry file under %localappdata%\doctormckay\node-steamuser (on Windows).

There's a setMessage method as of v2.

Steam sends the data differently sometimes. Update to 2.8.1 and I've made the tags objects all be standard (that is, they have all the properties).

You need to update steam-client.

No, that's wrong. Don't call counter() more than once. Call it once and store the result in a variable.

Correct.

offer.counter() returns a new TradeOffer object. You need to perform your changes on that TradeOffer that it returns.

There's nothing in the module right now to parse comments.

No, I don't think it's possible to opt specific offers out of cancelOfferCount canceling.

If you only want the latest, you could get the keys using Object.keys, sort it (YYYY-MM-DD sorts alphabetically quite nicely), then pull the first/last element (depending on how you sorted it).

You can control cancelTime per-offer using the cancelTime data key: https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOffer#datakey-value