Dr. McKay

Set up a timer, and call gamesPlayed with the next string in the rotation each time it fires.

Per the documentation, the emailInfo property is updated after all emailInfo event listeners fire.

getReceivedItems can only be called when the offer is accepted and confirmed.

As an update, I've gotten very basic support working in the v4 branch. Hopefully I'll be able to finish up v4 soon, at which point new chat support can be fleshed out further.

You're correct that you want to use the user event. If you don't want to receive further updates for the user event, you can use removeListener.

That top one looks kind of like you got a corrupt chunk. All your connect timeouts are likely due to CDN servers being down/slow to respond. Just retry. File checksum mismatch is weird, that means the decompressed/decrypted data in the chunk didn't match the sha1 we expected. And all the "Fail" errors is just Steam being Steam.

Yep, that's planned. Just haven't gotten around to starting work on it (though now that it's out of beta, I don't have much reason to wait anymore).

Yes, but that's a bit like cutting off your leg because you got a cut.

One of the files in your local cache appears to be corrupted. I'll push a fix to handle this case.

Without knowing exactly what depot you're trying to download, all I can tell you is to check each file entry in the manifest to see if flags & EDepotFileFlag.Directory.

There aren't any plans for this, primary due to spam concerns.

This is unlikely to ever be added to steam-user.

Not presently.

"Cannot download a directory" means that you tried to download a directory as if it were a file. You can't do that.

Don't believe so.

Yeah, that's still the only way.

Are you up to date?

Not with any publicly-available libraries I'm aware of.

GetOwnedGames returns playtime.

No, that's not going to be possible.

Oh, you meant in the node module. Open a GitHub issue and someone will get to it at some point, presumably.

It should already work with an API key.

They updated webchat with the new system. It doesn't go through the API anymore. Now the browser connects to the same servers as the Steam client does, which is what steam-user is designed to do. So if you want to do chat, you need to do it through there now.

Like when you're logging in? Check the error event.

You're not running code in the Node.js context.