Dr. McKay

If you use getConfirmations, the result will be an array of CConfirmation objects. The title contains the item's name, and the icon contains its image.

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

When an offer is countered, the original offer goes into state 4 and a new offer is created. You want to decline the new offer.

Call logOn.

Sounds like your steam-user isn't connected.

No.

Offers will disappear on their own after a while.

Memory usage is pretty normal on accounts with a lot of trade offers. The module caches asset descriptions in order to avoid slamming the API and using up your quota of requests on asset description retrieval. If you want to minimize memory usage, you need to omit a language in the constructor and keep track of whatever data you might need yourself.

Call acceptConfirmationForObject whenever you send a trade offer that needs confirmation.

You're right, the docs are wrong. I've fixed it. There is no way to retrieve the list of members in a chat room group, so I've added a method for how the Steam client does it.

Not via JavaScript, at the moment.

Confirmation polling (and therefore the newConfirmation event) is deprecated and won't be supported. But also no, you shouldn't use acceptConfirmationForObject with a confirmation ID. That won't work. You're supposed to use the offer ID. What I suspect is happening is that you're trading a bunch of items between bots. When you accept a confirmation for an outgoing offer in which both parties are losing items, it will be pretty quick. When you accept the confirmation for an incoming offer, the confirmation response won't come until all items have been moved. If you're moving a lot of items, this will take a while. There is no way to avoid this.

That's not necessarily what that means. What exactly that error means is pretty much unknown. The takeaway here should be that you need to catch and handle errors, or else your stuff will crash.

That's just Steam being Steam.

If the code you posted in your original post is that entire file, then that specific client is not logged on. You instead created a new one.

Did you ever log on with the client?

Once you join a chat room group, you're in it for good. There's no need to join it every time you log in. You can check which groups you're in using getGroups.

Check error.

Without seeing exactly how parseMessage is called, all I can suggest is that maybe you want that if to be if (!message || !message.startsWith('!'))

I'm pinning this thread again because of numerous recent questions about changes made in v4.

It was removed in v4 because it no longer works.

As far as I'm aware, that's the only bbcode that works in chat. Everything else is a /command or an :emoji:.

That SteamID (like all 64-bit SteamIDs) is too big to be represented as a JavaScript number. It's being rounded. Wrap it in quotes.

You need to use bbcode: [mention=accountid]@name[/mention]