TuringBot - DailyMaxPokemon/Stops Killswitch! - Decrease ban chance! - Safest bot!

**iamthadjawi** · 08-15-2016

Note, I didn't make this, all credits go to the developper, I'm only sharing.

Info:

Hi guys,

With Niantic implementing the recent CatchFlee ban when you hit 1,000 Pokemon/2,000 Pokestops per day, I figured I'd take a look at implementing a killswitch and other improvements into a current bot (in this case Necro/MobBot). I then took it a little further and increased the humanization factor of the bot by adding varying walk speeds among other internal fixes. With these changes in place, I am hoping that the chances of bans are greatly decreased and that our accounts remain safe. This bot is NOT intended for users who want ridiculous exp/hr or to snipe all across the globe.

Note: I may or may not continue developing this depending upon user response and usage. If it's a hit, I will work on it further. If not, expect this to be the only release. I do not take any responsibility for banned accounts. While this bot is being worked on to help increase "AI", it is not a guarantee that you will not be banned.

Updates / features:

Humanized walking - The speed you enter in the config file now has a floating point! No more walking at the same exact speed. You don't walk at a consistent 20km/h when playing in person, so why should the bot? (ex. If you set 40km/h in the config, the bot will walk from Pokestop to Pokestop at a range of 32km/h to 48km/h)
Pokemon/Pokestop tracker - All Pokemon catches and Pokestop visits are logged at the top status bar. Keep an eye out for the thresholds of 1,000 pokemon/2,000 pokestops per day!
Killswitch - Going to be away from your computer? Set a killswitch value to have the bot close once a certain number of Pokemon are caught or Pokestops are looted.
Improvements to how Pokestops are chosen/traveled to - Hopefully this will give a boost (albeit minor) to exp/hr.
Minor text fixes

Useage suggestions:

Keep walk speed at or under 40km/h
IMPORTANT: Keep the killswitch set - Have the bot kill itself when 975 pokemon/1975 pokestops are reached. It does not work off of your current local timezone but rather the bots runtime, so if you kill the bot and restart it, you'll need to remember the amount of pokemon caught and pokestops visited from the previous run during the 24 hour timeframe and adjust the killswitch accordingly.
Do not snipe (at least on your main) - Users are reporting an increase of CatchFlee errors when changing locations quickly! You will need to turn off sniping in the configuration file as the compiled version I uploaded has it set to 'true'. This was oversight on my part and I apologize!

Virustotal:

https://www.virustotal.com/nl/file/a...4a6c/analysis/