Dr. McKay

Well done, Valve. I'm not seeing that on my own inventory history page. Possible it's just a transient issue?

There is already an existing thread for this (and this isn't the right forum anyway).

Have you sent/accepted the offer already?

No, because having two clients logged into the same Steam account does trickery with your online status.

I think strictly speaking, the leading SteamID isn't part of the ticket. Some implementations just expect the SteamID to be sent preceding the actual ticket. Therefore, I don't believe I should be including that leading SteamID in the ticket I return.

What exactly is happening?

Thanks for the info. I've merged the pending pull request and published an update.

I don't really think this can be done with a bot. The bot would need to go online in order to receive chat messages, which would override your persona state from the proper Steam client.

You aren't logging into node-steamcommunity.

Good info, thanks.

I don't have any immediate plans.

You could add a function to that app.js file which returns the bot instance. Like exports.getBot = function() { ... }

You should provide the arguments as arguments, not as an object.

You'd have to reverse engineer it yourself.

It has never been tested to ensure that it actually returns well-formed tickets.

fs is not an npm module. It's built into Node.js.

Pretty much, yes.

That should work, but for robustness you should listen for the disconnected event then re-login after that gets emitted (but make sure you only call logOn in response to disconnected if you manually initiated the logoff; disconnected can also be emitted if Steam goes down, in which case it will automatically reconnect).

I don't believe this is currently possible (in node-steamcommunity; it will never be possible in node-steam-user).

getExchangeDetails.

You want to parse the URL? https://nodejs.org/api/url.html

Depending on what library you're using, there might be a method to get contexts. That said, it's likely any items you're interested in have a static, global context ID. For example, all current Valve games (TF2, CS:GO, etc) have a single context ID of 2. Steam Community items (emoticons, backgrounds, etc.) have a context ID of 6.

Sleeping won't work. You need to use setTimeout to delay asynchronously. Delaying synchronously breaks pretty much everything, always.

This is surprisingly difficult. You can't do it through node-steam-user at all, but you can do one of the following: Check the group members list XML to see if they're in thereCheck the user's profile XML to see if the group is listedBoth of these endpoints are deprecated, but neither has a replacement. Valve.