SpacePumpkin

Thanks, yeah I just wanted a second opinion on if I've missed the boat on this. I have a lot and didn't want to manually authenticate them with an email code and potentially risk a temporary trade restriction for a "new device". Looks like this will be what's needed.

I was hoping to be able to login using my old sentryfile through steam-session and then grab a JWT for use going forward but it looks like requests made with the sentryhash are still triggering a steamguard email code. Anything obvious I'm doing wrong here? I know Steam are phasing out sentry files, maybe I'm too late to do this. This sentry file works on an old Steam client from 2022 ```ts function readSentryFile() { const sentry = readFileSync(argv.sentry) let hash = createHash('sha1'); hash.update(sentry); return hash.digest(); // buffer contains a Buffer } async function getAuthToken(accountName: string, password: string) { let session = new LoginSession(EAuthTokenPlatformType.SteamClient) let startResult = await session.startWithCredentials({ accountName, password, steamGuardMachineToken: readSentryFile()}) console.log(startResult) } ``` is still returning with ``` { actionRequired: true, validActions: [ { type: 2, detail: 'gmail.com' } ] } ``` EDIT: node-steam-user had been happy with the sentry file up until about a week ago (17th October I predict). The bot was using an out of date version of node-steam-user and was seemingly just hanging on login attempt, after updating to the last v4 version it prompted for a steam code (although I see in the documentation you've removed support for this). I was just hoping node-steam-session might help me migrate away from the sentryfile for good

In my experience it seems to be 10 loads and then you're ratelimited for over 6 hours. I have tried with 1 request per 5 minutes and 1 request per 1 minute, both of those got ratelimited on the 11th request. I'm using a count of 75 (to mimick the browser). Still trying to figure out how long this ratelimit is, last night I waited 14 hours and the ratelimit had disappeared (but previous tests of only 6 hours failed - so its somewhere between 6 and 14 hours). Also worth noting that the limit seems to be rolling, that is, if you make a call 6 hours after getting limited, your cooldown resets and you have to wait the full time again (much like how the Steam Login cooldown works)

Have you noticed that the ratelimits are different for these calls? We're currently facing very aggressive ratelimiting on the new api so it would be nice to have a backup thats on a different ratelimit system