Dr. McKay

https://github.com/DoctorMcKay/node-steam-user/issues/384

You're not actually logged on until the loggedOn event fires.

It looks like Steam doesn't want to send rich presence data when you use getPersonas, so requestRichPresence is the proper way to request that data. Your lack of a callback was a bug which is fixed in v4.20.2.

This should make the displayed game "Idling Hours", but sometimes Steam can be temperamental when it comes to custom game names. bot.gamesPlayed(['Idling Hours', ...this.games])

newOffer shouldn't take longer than 30 seconds. It should be pretty much instant if you passed a SteamUser instance to TradeOfferManager. You might try outputting TradeOfferManager's debug output to see if anything is amiss: _manager.on('debug', (msg) => { console.log(`[TradeOfferManager Debug] ${msg}`); });

The arguments are still domain, callback, lastCodeWrong on 3.29.3 as well.

The promptSteamGuardCode option was removed in v4. The prompting is now automatically disabled when you add a steamGuard event listener. The arguments for the steamGuard event are domain, callback, lastCodeWrong. With the code you pasted, lastCodeWrong will always be truthy because that's actually the callback you should call with your new code.

https://github.com/DoctorMcKay/node-steam-user#steamguard

Either you'd use the steamGuard event or the twoFactorCode property when you call logOn.

It's not really a bug, per se. friendRelationship is emitted when Steam sends down a message that a relationship changed. I guess Steam assumes that your local data is out of date if you try to add someone who's already your friend, so you get the friendRelationship notification to make sure that your client is aware they're already your friend. Nonetheless, I'll suppress friendRelationship and groupRelationship events for updates to our already-known relationship in 4.21.0.

You can't. Restarting a process necessarily drops your TCP connections, which means that you get disconnected and thus logged out.

The first argument to the webSession callback is sessionID, not cookies. My guess would be that you have a handler for SteamCommunity's sessionExpired event that calls client.webLogOn(), which it's continually doing because it never receives valid cookies.

You'd have to use node-globaloffensive for that.

You probably need to set the Referer header.

Interesting. Are you trying to download a manifest that isn't the latest? The beta Steam client has indications that Valve might start restricting that.

Please double-check the version in node_modules/steam-user/package.json. cdn.js line 155 is blank in the latest version.

A SteamID object is an object, not a string containing the 64-bit SteamID. See info here from the SteamCommunity docs. The SteamID returned when you retrieve the user's profile from their vanity URL is indeed correct: > const SteamID = require('steamid') > let sid = new SteamID() > sid.universe = 1 > sid.type = 1 > sid.instance = 1 > sid.accountid = 117631762 > sid.getSteamID64() '76561198077897490' If you have the SteamID e.g. from passport-steam, then this is how you'd call getSteamUser: const SteamCommunity = require('steamcommunity'); let community = new SteamCommunity(); community.getSteamUser(new SteamCommunity.SteamID('76561198077897490'), (err, user) => { // . . . }); That said, if all you're doing with node-steamcommunity is retrieving users' profile details, you're far better off using the WebAPI for that.

Yep, seems like you understand it.

Sorry, I misled you. You need to pass a request instance with the proxy set on it to SteamCommunity, like so: const Request = require('request'); const SteamCommunity = require('steamcommunity'); let community = new SteamCommunity({ request: Request.defaults({proxy: 'http://1.2.3.4'}) });

What version?

Wireshark might help

If you pass a SteamCommunity instance to TradeOfferManager, then it inherits it.

The fromitemid asset id should disappear, and the amount of the toitemid should increment by however much the amount of the fromitemid was.

I've never used it myself. I'm sure you can figure it out. I'm going to assume that you pass the asset ID of the stack you want to put onto another one as fromitemid, the asset ID of the stack you want to put items onto as toassetid, and the amount of items you want to move as quantity.

You need to set httpProxy on the SteamCommunity instance too.