Jump to content
McKay Development

Vizzy

Member
  • Content Count

    4
  • Joined

  • Last visited

  1. is there no other way? I feel like other unhandled errors might put the application in an unsafe state whereas a casual rate limit isn't as big of a deal, or would I just check for the specific error (and is there a list of errors that crash the application somewhere)?
  2. Hi, I'm running a couple of steambots but when one of the bots receives an error like TooManyRequests or LogonSessionReplaced the application crashes. I would like it not to crash, as I have a couple of other bots running as well (process.exit() is being used in the modules?). How can I stop this from happening?
  3. Huge facepalm right there, I even remember reading about it on the docs. Thanks, that's it, I never initiated anything to trigger the event.
  4. Hi, I'm trying to forcefully kill the cookies so that it will trigger the sessionExpired event. However, this does not seem to happen. I cannot get the sessionExpired event to trigger and after some digging around I'm unsure what I could have done wrongly. Code // Scripts const config = require('../config'); // Modules const fs = require('fs'); const SteamCommunity = require('steamcommunity'); const SteamTotp = require('steam-totp'); const TradeOfferManager = require('steam-tradeoffer-manager'); const SteamUser = require('steam-user'); // States let community = new SteamCommun
×
×
  • Create New...