-
Posts
3573 -
Joined
-
Last visited
Everything posted by Dr. McKay
-
If you print the stack trace from the error, we can see exactly which request failed. There's a few involved in fetching a manifest.
-
This might have to do with manifest request codes. Try supplying the branch name to getManifest, like so: let result = await client.getManifest(730, 731, latestManifestId, 'public');
-
addFriend returns a normal eresult. You can see all eresult values at https://steamerrors.com As for which specific codes it's possible to receive, that's not really known.
-
Because scraping the website to send and receive trade offers is dumb.
-
You need to spend $5 to access the API, which is necessary for steam-tradeoffer-manager.
-
I'm assuming you're running multiple instances, so here's a way to keep track of them: let accounts = {}; function loginAccount(accountName, password, twoFactorCode) { if (accounts[accountName]) { throw new Error(`Account ${accountName} is already created`); } let user = new SteamUser(); accounts[accountName] = user; user.logOn({ accountName, password, twoFactorCode }); } function logoutAccount(accountName) { if (!accounts[accountName]) { throw new Error(`No SteamUser for ${accountName}`); } accounts[accountName].logOff(); accounts[accountName] = null; }
-
You can supply a Steam Guard code to logOn by passing it as twoFactorCode. If you listen for the steamGuard event, the "Steam Guard App Code" prompt is suppressed. You could create your own prompt if you wanted. Probably something like this: user.logOn({ accountName: 'example', password: 'example', twoFactorCode: require('fs').readFileSync('appcode.txt').toString('utf8').trim() }); Just call logOff on the appropriate SteamUser instance.
-
I dunno, could be just Steam being Steam.
-
I don't understand the question.
-
Steam sucks. You should either wait a little while before crediting/deducting user balances, or ignore offers that go into state 3 twice.
-
That's just par for the course when it comes to Steam, unfortunately.
-
Is it possible to delete SteamGuard authenticator with the secret?
Dr. McKay replied to Tati's topic in node-steam-user
https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity#disabletwofactorrevocationcode-callback -
Is it possible to delete SteamGuard authenticator with the secret?
Dr. McKay replied to Tati's topic in node-steam-user
Not as far as I'm aware. The Steam Mobile app uses the R code to disable mobile authentication. -
The first argument to updatePrice is which currency you want to get prices in. It seems that the docs are wrong on this, so I've updated them.
-
Steam Community tokens seemed to be linked to IP address
Dr. McKay replied to BreadEater's topic in General
I'm not aware of any way to share cookies between multiple IPs. -
The only way to avoid rate limits is to make requests from multiple IP addresses.
-
Correct.
-
Yes, this is the case. You need to use a loginKey for passwordless authentication; the sentry file is used to remember your machine for Steam Guard (and probably is also necessary when logging on with a loginKey). I don't know where the real client stores the loginKey; I've looked for it briefly in the past but I didn't find it. It might be stored somewhere encrypted.
-
It's basically just a record of trade offer IDs that TradeOfferManager has seen and the last-seen state they were in, so that you don't get newOffer emitted for every trade offer every time you restart your bot. If you're okay with that happening, you don't need to save and restore poll data. Also, it's where data you set on a trade offer with the data() method is stored.
-
All the data you need would be in the item schema, but deciphering it can be a challenge.