Dr. McKay

Protos.SteamDatagramTicket.decode(body.slice(4)).data

Skip the first 4 bytes, and this schema will decode it: message SteamDatagramTicket { message DataWeCareAbout { message NamedInteger { optional string name = 1; optional fixed64 value = 5; } message LoneInteger { optional fixed64 value = 16; } optional fixed32 unknown1 = 1; optional fixed64 steamid = 2; optional fixed32 unknown3 = 3; optional fixed64 server_steamid = 4; optional fixed64 unknown5 = 5; optional int32 app_id = 7; repeated NamedInteger arguments = 8; optional fixed32 unknown9 = 9; optional int32 unknown10 = 10; optional bytes unknown11 = 11; optional LoneInteger steamid_again = 12; optional LoneInteger server_steamid_again = 13; } optional fixed64 unknown2 = 2; optional DataWeCareAbout data = 3; optional bytes unknown4 = 4; } This was produced by reverse-engineering. The field names are definitely not the same as what Valve uses.

You shouldn't increase the limit. You should figure out why you're attaching so many listeners to friendRelationship.

What do you get if you call buffer.toString('hex')?

Valve is utterly incompetent and as a result Steam is complete garbage. It is extremely common for random endpoints to give failure responses even if Steam as a whole is "working".

e is an Error object. Calling JSON.stringify on an Error object returns {}.

I don't believe it's currently possible to embed an image into chat using steam-user. You could always upload it to imgur or something and send a link to it though.

If I had to guess, I'd say that community isn't an instance of SteamCommunity.

The documentation is slightly out of date. I'll update it.

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.