Dr. McKay

Yes, that's what the setCookies method is for.

You're using the automatic confirmation checker, which has had this notice on its documentation page for 3.5 years:

There is no timeout for connection attempts because when Steam goes down, it can stay down for a while and we want to be able to reconnect automatically. Add this and you can get some more descriptive output: client.on('debug', (msg) => console.log(msg));

https://github.com/DoctorMcKay/node-steamcommunity/wiki/CSteamUser#commentmessage-callback

id and assetid are the same thing, both property names are used for convenience. To identify an item, you'd need to check the appid + contextid + assetid combo. See also:

The error event is only emitted (in this module) when you get disconnected from Steam, and the module will not attempt to auto-reconnect. Handling the error event isn't going to act like handling the uncaughtException event; it's not going to prevent crashes for other errors besides Steam disconnects.

Connection errors are communicated through the error event. If you don't handle error on an EventEmitter, then Node.js will terminate the process.

No, the only way you can tell if an item is currently in a trade is to pull your list of active trade offers and see if it's in there. There is no indication in the inventory that an item is in an active trade offer.

No idea, that's entirely up to the game's developer.

Presently the only way I'm aware of to handle that is to scrape and parse that page.

steam-user will automatically reconnect when it can if Steam goes down. Once it reconnects it will automatically renegotiate its web session. It will still be necessary to refresh your web session with webLogOn from time to time, but not as a response to Steam outages.

You shouldn't be using relog when your web session expires. Just call webLogOn and webSession will get emitted again.

steam-tradeoffer-manager does not presently support promises (async/await), although that's planned for the near future. In the meantime, you'll need to wrap the call in a Promise.

Yes, you'd need to request both inventories separately.

It's possible. You could try deleting the local cache. On Windows, delete the entire folder %localappdata%\doctormckay\node-steam-tradeoffer-manager

Your Steam Community inventory is AppID 753, ContextID 6. So replace 730 with 753 and 2 with 6.

Wait, why are you looking at rawJson? Of course the item description wouldn't be in there.

Use 'english' as the language.

Sorry, I have no experience with the Steam datagram relay.

Let me see your constructor code.

Yes, you would want to use NetHook (and NetHookAnalyzer) to inspect the traffic going to and from the GC when you do a trade-up if you wanted to implement it yourself.

Unfortunately no, Steam doesn't tell the client what its SteamID is until you successfully log on.

Check the users property to see if you already have their info cached, and if you don't, use getPersonas. The URL to the image is available in the resulting object as avatar_url_icon, avatar_url_medium, and avatar_url_full.

OpenID doesn't do what you think it does. It doesn't log you into Steam; it allows third-party sites to verify you are who you claim you are on Steam. So yes, you'd need to implement the whole login flow to get a session cookie.

Not at the moment, no.