Panp858

Thanks for the response. When I login into my steamaccount I can sometimes switch between accounts without providing a new mobile code. Is this some kind of bug? Its a bit annoying to provide a code every time a bot with 2fa is logging in.

Thanks mate, that helped!

Hello community, after a long time, I had to switch from my old sentry-like to the new machineAutoToken approach. Since I've tp update my bots anyway, I start switching from old and unsupported libraries like node-steam or steam-weblogon to steam-user. After I did my changes and also implemented my own data store which is basically a different and more persistent location on my system I wasn't able to login a single time. Each time, I entered an steam guard code from email which is required for first time login, the process crashed with: UnhandledPromiseRejectionWarning: Error: AccountLoginDeniedThrottle at SteamUser._handleLogOnResponse (E:[...]\node_modules\steam-user\components\09-logon.js:792:17) I noticed that I first misused the read and write functions of the data store in my first run because I was expecting only the machineAuthToken to be saved. However, the current actions called are: [STEAM] Storage Read Called. [cm_list.json] --> Successfull [STEAM] Storage Read Called. [cellid-xxx.txt] --> Failed [STEAM] Storage Read Called. [machineAuthToken.XXX.txt] --> Failed -> Steam Guard Code Request with manual imput... [STEAM] Storage Read Called. [cellid-xxx.txt] --> Failed [STEAM] Storage Read Called. [machineAuthToken.XXX.txt] --> Failed -> App crashes with "AccountLoginDeniedThrottle" So nothing except of the cm_lost.json has been written into the local store. I am not sure if the data store is really related to Error 87 of steam. But if I run the old code on a different machine with a different IP, the login process with old sentryFile still work on all accounts but I am not able to receive cookies for further interactions (so switching back is not an option). Am I missing something? Edit: After some period, I was able to test again. However, I noticed that for accounts with mobile steam guard, no machineAuthToken is generated and stored. Is this correct?

Hello! Any chance that you are sharing the solution? My bot uses tons of old libs with I fixed from time to time (e.g., steam-web-api-key, steam-weblogon, and steam-tradeoffers) but I am unsure how to fix this issue because the whole flow is now broken.