Dr. McKay

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOfferManager https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity https://github.com/DoctorMcKay/node-steam-totp https://github.com/DoctorMcKay/node-steam-user

If you want the steamGuard event to work, you need to set the promptSteamGuardCode option to false.

If you remove it then you may see the memory usage decrease, but you're correct that the item objects would no longer have details like the item's name. Still though, this kind of memory usage shouldn't happen on the latest versions and you're the only person to report it...

Did you supply a language to the constructor?

Are you up to date?

It just happens. Steam does weird things. You'll just need to retry.

You can do this as of v3.35.0. https://github.com/DoctorMcKay/node-steam-user/blob/master/doc/AppAuth.md#getauthsessionticketappid-callback

Not possible, and never will be.

What would you suggest? An environment variable holding a path to a config file, or a config file in your home dir (based on HOME env var)?

using http

That's not possible, sorry. What's your use for that?

I don't believe so.

You can only set it in the constructor.

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

Are you talking about steamcommunity or steam-user?

If it's cached, then it's cached by Steam.

You would need to set up a request object with the proxy option: https://www.npmjs.com/package/request#proxies And it would apply to all requests, not just one.

No, and that will never be possible though node-steamcommunity.

No, if one party has the mobile authenticator enabled for a week then theirs will be 0 and the other might be 15. Whichever is larger becomes the result for that trade.

No.

Get rid of the parenthesis with arguments in them. You're calling offercase(), not passing it as a function reference.

Your second example doesn't have a return after you check err. Is there just an error message above it that you're missing?

If you don't have a mobile authenticator enabled, you should call requestPasswordChangeEmail first to get an email sent to you. If you do have a mobile authenticator enabled, you should skip the email entirely and just use a 2FA code when you call changePassword. You mentioned a "prompt comes up", is it the "Steam Guard App Code: " or "Steam Guard Code: " prompt? If so, that's not the prompt for changing your password, it's the prompt for logging in. If you don't disable the promptSteamGuardCode option then if you don't supply a Steam Guard code in logOn it will prompt for one from stdin. And since you can't use mobile authenticator codes twice, if you do have a mobile authenticator enabled you need to supply a code to login, then wait 30 seconds before trying to change your password so you'll get another code.

Sounds like Valve's tired of people creating spam bots.

#2 is all I'm aware of that works. And yes, you need to own CS:GO.