-
Posts
3545 -
Joined
-
Last visited
Everything posted by Dr. McKay
-
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.
-
CSteamUser's "getUserInventoryContents" gives "err" as undefined.
Dr. McKay replied to Larry's topic in node-steamcommunity
Get rid of the parenthesis with arguments in them. You're calling offercase(), not passing it as a function reference. -
trade offer with null id?
Dr. McKay replied to Mr Game and Watch's topic in node-steam-tradeoffer-manager
Your second example doesn't have a return after you check err. Is there just an error message above it that you're missing? -
How exactly does the SteamGuard code work in changePassword()?
Dr. McKay replied to Jack's topic in node-steam-user
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.
-
Question How to avoid http 429 (Too Many Requests) in marketSearch() ?
Dr. McKay replied to Samfcs's topic in node-steamcommunity
Make fewer requests or get more IPs. -
Is polling for trades in tradeoffer-manager
Dr. McKay replied to nightfuryninja's topic in node-steam-tradeoffer-manager
They're two separate things. steam-tradeoffer-manager polls for trade offers using the API, which is not deprecated and works well. steamcommunity polled for confirmations by scraping the confirmations page, which is deprecated due to very strict rate-limits Valve imposed on that page. If you want to send or accept trade offers in which your bot loses items, you'll need to use both. steam-tradeoffer-manager will let you detect incoming offers and accept them or send offers, while you need to use steamcommunity to accept any confirmations that are generated by doing so.- 1 reply
-
- node.js
- node-steam-tradeoffer-manager
-
(and 1 more)
Tagged with:
-
emailInfo still null (not updating) when logOn is called
Dr. McKay replied to Jack's topic in node-steam-user
You aren't waiting until it's emitted. It's emitted after login, not before login. -
Yeah you're trying to read it before you're logged on.
-
There is no alternative. You'd need to get Valve to add your app and depot to the anonymous sub.
-
Did you turn on the enablePicsCache option?
-
Steam does strange things sometimes. You just need to try again later.
-
Yeah, that doesn't work because anonymous users only get a license for sub 17906.
-
No need to censor the appid/depotid/manifestid, what are they?
-
Question How to use skipStateUpdate
Dr. McKay replied to MrPotato's topic in node-steam-tradeoffer-manager
offer.accept(true, (err, status) => { // do things }); -
https://github.com/DoctorMcKay/node-steam-user#promptsteamguardcode
-
It's all in the docs. offerList gets emitted whenever the offer list is retrieved, no matter what queried for it. Including polling.
-
There is no mechanism in steam-tradeoffer-manager to automatically cancel incoming offers, because there's no real technical need to do that since there's no limit on incoming offers like there is for sent offers. You'd need to implement it yourself, ideally using the offerList event to watch for a list of offers and declining those that are too old for you.
-
Accept/confirm problem for large offers
Dr. McKay replied to NxtChg's topic in node-steam-tradeoffer-manager
This is normal. When a trade is completed, the Steam backend makes two HTTP requests to the item server per item, and those requests aren't quick (something in the ballpark of 500ms per item I think). So if you're doing a really big trade, the request in which it's completed (if the offer recipient is only receiving items, the request to accept the offer, otherwise, the request to confirm it) will timeout after 30 seconds, but the trade will keep committing on the server. And it seems that while a trade is committing the rest of the API gets cranky for your account, probably because it doesn't feel like playing ball while a trade is in progress.