vindisel

I'm writing a farm and I have about 50 steam accounts. At the moment, it looks like this: I made a store where I put each logged-in account, then I use the steamid to access the desired one and perform an action. const BotInstance = new Bot('login', 'password', 'shared_secret', 'identity_secret', 'steamid'); const newBot = await accountsStore.add('steamId', BotInstance); newBot.login(); const getBot = await accountsStore.get('steamId'); getBot.addFriend('friendSteamId'); How would it be more efficient to leave it as it is or implement it all through a cluster? what kind of power is needed to support such a large number of accounts? and won't I have a problem if they're all on the same ip?

Thank you. And how long do cookies live? And will sessionExpired be triggered when they die?

How do I log in now? I am using steam-session to generate jwt tokens, but when I try to pass the token to setMobileAppAccessToken(accessToken) , I get the following error: Error: Log in to steamcommunity before installing the access token to the mobile application. In this case, why not add a login using only refreshToken? Similar to oAuthLogin or logOn in node-steam-user.

Hello, receivedOfferChanged isn't triggered when offer is accepted and expects confirmation in mobile app. It works only if offer declined or canceled receivedOfferChanged. If I accept trade and then decline, the status will change from 2 to 7, but should from 9 to 7 if i right. this.TradeOfferManager.on('newOffer', (offer) => { console.log(`New offer: ${offer.state}`) }) this.TradeOfferManager.on('receivedOfferChanged', (offer) => { console.log(`Offer changed state: ${offer.state}`) // it works if offer.state !== 9 }) "steam-tradeoffer-manager": "^2.10.3" this.TradeOfferManager = new TradeOfferManager({ community: community, pollInterval: 5000, })