Dr. McKay

Looks like maybe there was a condition which ended up in your Steam client connection being disconnected just before your web session was negotiated.

You should use the WebAPI to check if a user is in a group.

What do you mean by "proxy isn't valid"?

As you discovered, calling client.on('friendMessage#' + variable, ...) only creates a listener for the SteamID contained in variable at the time the listener was added. If you need to change the SteamID you're listening for, you need to just listen for friendMessage and check the SteamID in the event.

You shouldn't install steamcommunity globally. Install it locally in the directory where your project lives.

If you just use node-steamcommunity without any special parameters, it will act as if it's a mobile login.

Use node-steamcommunity.

If you're asking what kind of device Steam thinks logged in, it's a client.

Not at the moment.

What?

Everything is going to be rate-limited, but the least rate-limited endpoint is: https://steamcommunity.com/inventory/[steamid]/440/2

Check the item's tags.

Yes.

The count parameter is how many comments to return in the response. You could probably change it and it would work.

Yup.

You're setting the amount property on an array of CEconItem objects. It needs to be set on the objects themselves.

Please double-check the docs. Argument 2 to getProductInfo is an array of packages, not the callback. Pass an empty array if you don't care about any packages. Also, it doesn't return the data; the data is passed to the callback.

For the API and profile, Steam ignores apps in sub 0 unless they have playtime on record. If your account has played TF2, you can make it show up in the WebAPI by passing include_played_free_games=1. I assume you're asking if there's a way to get only the AppIDs of games that are granted by a sub other than sub 0. You'll need to go through your licenses array, ignore sub 0, get product info for each package granted by a license, and see what AppIDs the package grants.

When using Steam in-home streaming, network communication is encrypted with the auth secret. It's called a pre-shared key because it's an encryption key that is shared with both parties (in this instance, the machine the games are getting streamed from and the machine they're getting played on) by Steam, before the in-home connection is established.

https://github.com/DoctorMcKay/node-steam-user#getproductinfoapps-packages-incltokens-callback

I assure you that it doesn't.

Make sure the privacy settings allow people to view games.

Looks like that account owns these apps, beyond the basic ones everyone owns: 730 - CS:GO745 - CS:GO SDK236390 - War Thunder (free on demand)238960 - Path of Exile (free on demand)304930 - Unturned (free on demand)311730 - Dead or Alive 5 Last Round (free on demand)355840 - Survarium (free on demand)438100 - VRChat (free on demand)624820 - CS:GO - General763700 - Smart Mummy817760 - The Castle Disaster

It's not, you're doing something wrong.

ByteBuffer is a layer over Node's regular Buffer which adds some nice things. Basically what's happening here is that you're allocating 16 bytes + however many bytes you need to represent your name string + 1 more byte, then you're filling in those bytes with the values shown (the name tag ID in 64 bits, the item ID in 64 bits, the name as a string, and a 0 byte at the end to represent the end of the string). I'm unsure why that dash is being added. We might have missed a field, maybe. Try adding buffer.writeUint8(0); before the writeCString.