Skip to content
This repository was archived by the owner on Jul 22, 2019. It is now read-only.

Conversation

@rraumberger
Copy link
Contributor

Fixed issue:
Provides a possible workaround for most "my bot crashed after 2h for no reason" issues.

Changes made:

  1. Added exception-handler to Bot.kt
  2. BotService now registers an exception handler for all submitted bots
  3. BotService now restarts all bots which exceed the configured autoRestartThreshold
  4. replaced println-statements with proper Log.x calls

@ritsu
Copy link

ritsu commented Aug 12, 2016

When the bot restarts, does it go back to the starting lat/lon? Because if the last position was, say, 3km away from the starting position, then teleporting back to the starting position might result in a soft ban.

Maybe add a delay based on distance from starting position? I see there's an autoRestartPeriod setting that might suffice, even if it is just a fixed number. User could just configure the bot to never walk more than (60km/hr * autoRestartPeriod / 3600) km away from the starting location.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants