Dr. McKay

You would need to download the game files from the CDN, parse items_game.txt, unpack the vpks, and figure out how to attribute texture files correctly to given items. Have fun.

None of those messages are going to work for your needs, since they're only for requesting the logged in user's inventory. You can't request other users' inventories that way. Using the HTTP endpoint is pretty much the only way.

You would need to also bind the local address on node-steamcommunity and additionally pass that community instance to the steam-tradeoffer-manager instance in the constructor.

Well, you're logging in twice and only once with an auth code. Of course the login attempt without a code is going to fail.

The transfer requests are just to set cookies on all the Steam domains, so logging in on community also logs you in on store and vice versa. But it's the same cookies on all domains.

I guess you're not using the correct shared secret. I don't know why you'd need to instantiate that sid variable, but that input format is correct regardless.

I would just look at what node-steamcommunity does to login: https://github.com/DoctorMcKay/node-steamcommunity/blob/master/index.js#L57

If there's no release date in the data returned from getProductInfo, then that data wasn't put into that system. The only other way to get the release date would be to scrape it from the game's store page.

Your first screenshot is an error event. If you don't add a listener for the error event and it gets emitted, it will crash your app. It looks to me like the Steam server you connected to exploded... has this happened frequently?

It's game_server_ip and game_server_port in the user event.

That data comes from the game server directly, not from Steam. You'd want to use something like this for that.

You'll get 1200.

I don't believe it does, but I don't know why you'd want to call that very frequently in the first place.

Do not use prefix-underscored methods. They are internal to the module and could change at any time.

https://github.com/DoctorMcKay/node-steamcommunity/blob/master/examples/edit-group-announcement.js#L17

It doesn't look like you ever passed cookies to your steamcommunity instance. You'd want something like this: client.on('webSession', (sessionID, cookies) => { community.setCookies(cookies); });

Which line is that occurring on?

In theory yes, but steam-user is not the best way to determine if some other user owns a particular app. You'd want to use the WebAPI's GetOwnedGames method, or ideally the publisher CheckAppOwnership method.

Yes, but: You shouldn't relog your client connection if your web session expires. Just call webLogOn() Calling logOff() in the error event listener is going to cause an error; if error gets emitted you're already disconnected (same applies to the disconnected listener) steamID is never going to be null in the disconnected event listener

The profile data is cached for some time, you should try requesting again after a little while.

The first argument to the webSession event is sessionID, not cookies.

Yes.

Yes, it will come up once and then you should get logged back in. It's fine to go ahead and call getExchangeDetails in the callback of offer.accept.

steamcommunity doesn't know that the session expired until it gets back a "Not Logged In" response. In other words, it's the "Not Logged In" response itself that triggers the sessionExpired event.

Unfortunately that's not possible.