Dr. McKay

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.

You would retrieve the other user's inventory and use addTheirItem to add their items to the offer.

Collecting credentials from users is a very bad idea, no matter how good your intentions are. I won't support that.

No, sadly that's not possible. There are some browser extensions out there that will make this work with a single item only, by appending &for_item=appid_contextid_assetid (like for_item=730_2_123456789) but that's only if the user has one of those extensions installed, and isn't using the Steam client.

Are you re-retrieving the user's inventory the second time? Maybe the fact that you're manipulating the response object is what's causing your problem.

Here is where that plugin came from: https://forums.alliedmods.net/showthread.php?p=1850358 There are only a select few commands that the server can force the client to execute, and quit is not one of them. In fact, that plugin doesn't actually support running client-side commands, it only supports "fake" client commands. Meaning, it makes the server think that the client ran a command. So it's only going to work on commands that run server-side, like "kill".

You can't do offer.addMyItems(item.amount = 1) You need to do it like this: item.amount = 1; offer.addMyItem(item);