Bot should take a break after being softbanned (all pokemons run away)

[hobbes3]

Short Description

After running the bots for hours, the bot gets softbanned and all Pokemon runs away.

Possible solution

Although the bot can still spin Pokestop, the bot should stop and take a break for a few hours since I have a theory that Niantic records how much a player keeps playing after being softbanned (to issue a permaban later).

How it would help others

I believe less bots will be permabanned.

[ScriptKiddiez]

I can confirm this. I've had 3 accounts now be banned for running hours on end with encountering pokemon, but not catching any of them. I've also noticed that sometimes they will erase everything in your inventory and the console will spew out the message, "No usable pokeballs found.". After running for several hours without catching anything, they obviously know who is and isn't botting.

Update: I'm botting an account right now and this is what's happening:

2016-08-21 22:29:27,180 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Dimensional Cube Façade - 0.06km
2016-08-21 22:29:30,150 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Dimensional Cube Façade - 0.05km
2016-08-21 22:29:31,778 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Dimensional Cube Façade - 0.05km
2016-08-21 22:29:33,230 [ SpinFort] [INFO] [spun_pokestop] Spun pokestop Dimensional Cube Façade. Experience awarded: 50. Items awarded: {u'Ultraball': 1, u'Pokeball': 2}
2016-08-21 22:29:36,096 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Stockton Tunnel - 0.08km
2016-08-21 22:29:37,398 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Stockton Tunnel - 0.07km
2016-08-21 22:29:38,828 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Stockton Tunnel - 0.06km
2016-08-21 22:29:40,015 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Stockton Tunnel - 0.05km
2016-08-21 22:29:41,563 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Stockton Tunnel - 0.04km
2016-08-21 22:29:44,384 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Stockton Tunnel - 0.04km
2016-08-21 22:29:45,729 [ SpinFort] [INFO] [spun_pokestop] Spun pokestop Stockton Tunnel. Experience awarded: 50. Items awarded: {u'Potion': 1, u'Pokeball': 2}
2016-08-21 22:29:48,766 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Ritz Carlton SF - 0.10km
2016-08-21 22:29:50,446 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Ritz Carlton SF - 0.09km
2016-08-21 22:29:52,026 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Ritz Carlton SF - 0.08km
2016-08-21 22:29:53,480 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Ritz Carlton SF - 0.07km
2016-08-21 22:29:56,066 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Ritz Carlton SF - 0.06km
2016-08-21 22:29:57,131 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Ritz Carlton SF - 0.06km
2016-08-21 22:29:58,700 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Ritz Carlton SF - 0.05km
2016-08-21 22:30:00,651 [CatchLuredPokemon] [INFO] [lured_pokemon_found] Lured pokemon at fort Ritz Carlton SF (ad3fc23803874c7ba432dd76c6cd0d30.12)
2016-08-21 22:30:00,881 [PokemonCatchWorker] [INFO] [pokemon_appeared] A wild Ekans appeared! [CP 262] [NCP 0.32] [Potential 0.78] [A/D/S 9/15/11]
2016-08-21 22:30:09,013 [PokemonCatchWorker] [INFO] [threw_pokeball] OK Curveball throw! Used Pokeball, with chance 43.22 (3 left)
2016-08-21 22:30:09,197 [PokemonCatchWorker] [INFO] [pokemon_vanished] Ekans vanished!
2016-08-21 22:30:14,461 [ SpinFort] [INFO] [spun_pokestop] Spun pokestop Ritz Carlton SF. Experience awarded: 50. Items awarded: {u'Potion': 1, u'Pokeball': 2}
2016-08-21 22:30:17,466 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Notre Dame Des Victories - 0.12km
2016-08-21 22:30:19,167 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Notre Dame Des Victories - 0.11km
2016-08-21 22:30:20,562 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Notre Dame Des Victories - 0.10km
2016-08-21 22:30:22,118 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Notre Dame Des Victories - 0.10km
2016-08-21 22:30:23,352 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Notre Dame Des Victories - 0.09km
2016-08-21 22:30:24,615 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Notre Dame Des Victories - 0.08km
2016-08-21 22:30:26,233 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Notre Dame Des Victories - 0.07km
2016-08-21 22:30:27,378 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Notre Dame Des Victories - 0.07km
2016-08-21 22:30:28,951 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Notre Dame Des Victories - 0.06km
2016-08-21 22:30:32,065 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Notre Dame Des Victories - 0.06km
2016-08-21 22:30:33,561 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Notre Dame Des Victories - 0.05km
2016-08-21 22:30:35,028 [ SpinFort] [INFO] [spun_pokestop] Spun pokestop Notre Dame Des Victories. Experience awarded: 50. Items awarded: {u'Potion': 1, u'Pokeball': 1, u'Greatball': 1}

It's like a new type of softban, in which you can still receive items from the pokestop throughout its duration. I think it's their way of tricking the bots that would normally fix that type of softban. Idk how softbans are currently detected; But if you could add a bit of code that would spin a pokestop 50 times or so after 'x' amount of pokemon fleeing, that would be great.

Update 2: I'm not very familiar with python, more of a c++ man myself, otherwise I would write the bit of code necessary to fix this. I believe the portion of code listed below, which is located in the handle_softban.py file is responsible for this.

        if forts[0]['id'] in self.bot.fort_timeouts:
            del self.bot.fort_timeouts[forts[0]['id']]
        return WorkerResult.RUNNING

From what I can see, it is currently detecting by whether or not a reward/xp is received from spinning the fort. If no reward/xp is detected, it checks and sees if it is just on cool down, if not, it is considered a fort timeout as seen below, in which the softban fix begins. I would personally recommend adding a feature in which after 3 vanishes back to back, it will automatically try and fix the softban at a "human-like" rate.

[hobbes3]

Currently I have to manually check to see if my bot is still catching Pokemons. If I see a bunch of vanishes then I manually stop the bot and restart it a few hours later...