Dr. McKay

Not with this module.

It's not possible to get the SteamIDs of players on a game server, no. You might be able to see what server a particular Steam user is on by getting their profile data from the WebAPI.

Looks like you're executing the JavaScript in the browser context and not in the Node.js context.

It's in the tags.

It is.

For the love of God, fix your indentation. loadPartnerInventory doesn't have a tradableOnly param, so don't pass one.

The object ID should be your trade offer ID, not the confirmation ID. You shouldn't use the newConfirmation event at all anymore.

Yes, try/catch + isValid is the way you're supposed to validate a SteamID (also check the universe and type if you care about those).

This is incredibly nooby but hey, we all start somewhere, right? Props for wanting to learn and not wanting everything just handed to you. You'd want to create an object and store it in a variable (e.g. let richPresence = {};), then loop over the array and set properties in that object (using bracket notation). So, this: let richPresence = {}; // create a new, empty object (sClient.users[sID].rich_presence || []).forEach((element) => { // Loop over the rich_presence array. If it happens to be missing, substitute it using || for // an empty array so we don't end up crashing by trying to reference forEach on undefined/null. richPresence[element.key] = element.value; }); console.log(richPresence.status); // Playing CS:GO

client.setOption('promptSteamGuardCode', false);

No.

You can't know until you try to login. If settings are left at their default, the module will prompt for the appropriate code from stdin. You can set promptSteamGuardCode to false and listen for the steamGuard event if you want, and that will also tell you what kind of code it needs.

Nope.

This is normal. Steam turns on Steam Guard automatically after you login via the client a few times.

I don't believe it's currently possible from this module to disable Steam Guard entirely.

steamLogin, steamLoginSecure, (only if logging in via web) steamMachineAuth, sessionid

Unfortunately not. I might have worked on reverse-engineering the Source protocol to join a game server, but to join any useful server you'd have to implement VAC which is just insane enough that I'm not touching it.

It executes once because you only told it to execute once.

Yeah, it only gets printed once because you never told it to do anything beyond that point.

You're doing something wrong in your code.

It's in owner_descriptions.

Those are for talking to the GC (which you can do). You can't join a game server.

You're most certainly doing something wrong, nothing "blocks code from executing".

You don't.

Not presently.