[๖ۣۜKamalu]

TuringBot Download:
Malu's Config & Bot Setup: (used in the 10 hour proggy) - Neil Tweak
V.0.2.0 https://mega.nz/#!oFE0mTwD!KVHrDBUev__Up...GI4AKauDc4

Latest Version of TuringBot: Includes CatchFlee Antiban - Original
V.0.2.1 https://mega.nz/#!hN1QCZaK!Gp6SfZlj8c4G2...a2ULxstk-k

Dev Notes:
Note from the TuringBot Developer: SeriousSensei

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.

Developer Recommended Usage Suggestions

Do NOT bot on your main! While I am trying my best to make this bot as humanlike as possible, there are NO guarantees. You could very well be banned. Only bot on accounts you don't mind losing.
Keep walk speed at or under 50km/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! Sniping is currently pretty buggy and I am not devoting as much time to fixing it as you'd probably prefer. Use other bots if you'd like to snipe for now!

Unique Features:
This is a Necrobot Mod so majority of the necrobot features remain.

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.
Catchflee ban checker and automatic shutdown - Once you string together X flee's in a row, the bot will close down as a safety precaution. This amount of flee's should never occur in a row otherwise, so I figured it was a safe number.
Config.json auto update - You may now edit your config.json while the bot is running. As soon as a change is made and the file is saved, the bot will recognize it and reload the variables from the config file.

Setup:
Safe Setup Config by Neil (BloggerXYZ), modified by Malu (Myself)
As always, you should try the Bot on a new PTC (Pokémon Trainer Club) account which you have never used to login on your mobile before. Use this Bot to level up until you reach your desired level and ONLY then login with it and start playing (through the Pokemon Go App). After you start playing, never run the Bot on that account again.

To setup this Bot, download the file and edit the "auth.json" and "config.json" files in the config folder. Input your PTC/Google credentials within the quotes, proxy information, and change your device id to something unique (you can input random letters/numbers). It is NOT recommended to change the config if you are unsure what you are doing.

Config Folder: The Malu Auth & Config files have instructions in the file as well to ensure you dont get lost 👍


Device ID: Change your device settings so each account is logged into a different device (change random letters/numbers).


Proxy Support: Use 1 proxy per account


Proof:
10 hour, 10+ account Proggy: 0 Bans


Killswitch: Set your killswitch number to something unique to you.
Example: If everyone stops catching pokemon after they catch their 899th for the day, this will build suspicion.



Follow My Progress:
8/21
Running about 15 accounts per 8 hour shift, this is my progress after one 8 hour shift per account.
(The low levels were running a sniping test instead of trying to get xp).
I use Go Manager to view stats since the "export stats" feature is gold on it. Of course, again with 0 bans and now 0 babysitting.
I trust the bot enough to go to sleep/work with it running.

[MrNacho123]

Very nice thread OP. Thanks for the info, will try it out!

[Bimmerguy]

Damn nice!

I'll test it out. Those xp are high and you have no problems?

[asero12]

thanks...testing it now for few hours

[KazerTheAmazer]

Thank you for your post OP, Looks decent; I will give it a try on one of my rigs.

[MauiBoi]

i hoppe this dont get us banned

[mariogitu]

if i stop this bot and tomorrow i wanna use again it will still work right ?

[AngryBird™]

Posting here for further use

[Sakamoto]

Posting here to keep this thread on my radar.

[๖ۣۜKamalu]

Running about 15 accounts per 8 hour shift, this is my progress after one 8 hour shift per account. (The low levels were running a sniping test instead of trying to get xp). I use Go Manager to view stats since the "export stats" feature is gold on it. Of course, again with 0 bans and now 0 babysitting. I trust the bot enough to go to sleep/work with it running.

[SL x TnT]

Running about 15 accounts per 8 hour shift, this is my progress after one 8 hour shift per account. (The low levels were running a sniping test instead of trying to get xp). I use Go Manager to view stats since the "export stats" feature is gold on it. Of course, again with 0 bans and now 0 babysitting. I trust the bot enough to go to sleep/work with it running.

I feel like I should mention this.

Those "Unique Features" of TuringBot, mine has (GoManager). I even went the extra step to keep track of the last 23 hours of pokemon / pokestop numbers. That way it should always have an accurate count.

I believe you start getting bans around the 25 level range. With your low amount of test accounts, you should see 0 to 2 bans. I'd put it more on the 0 side as you're trying to stay below the ban limits.
Some people have been testing what flags your account for bans with 500+ accounts at once.

[D3lud3d]

I feel like I should mention this.

Those "Unique Features" of TuringBot, mine has (GoManager). I even went the extra step to keep track of the last 23 hours of pokemon / pokestop numbers. That way it should always have an accurate count.

I believe you start getting bans around the 25 level range. With your low amount of test accounts, you should see 0 to 2 bans. I'd put it more on the 0 side as you're trying to stay below the ban limits.
Some people have been testing what flags your account for bans with 500+ accounts at once.

You got some data or a source for these people running 500+ accounts?

[Del Rey]

I started doing this!
Love ittttt

[๖ۣۜKamalu]

I feel like I should mention this.

Those "Unique Features" of TuringBot, mine has (GoManager). I even went the extra step to keep track of the last 23 hours of pokemon / pokestop numbers. That way it should always have an accurate count.

I believe you start getting bans around the 25 level range. With your low amount of test accounts, you should see 0 to 2 bans. I'd put it more on the 0 side as you're trying to stay below the ban limits.
Some people have been testing what flags your account for bans with 500+ accounts at once.

I'm running your bot, pokemob from herbert, and turingbot bro. With the lack of knowledge on bans, I figure I try 3 different bots with successfully reported configs each doing roughly 10+ accounts per 8 hour shift. This way I'll be able to narrow down what worked/didnt work this next ban wave. I posted TuringBot because of its success on other forums and that its not posted here. It might all be for nothing and everything gets banned, but hey its in the learning experience ✌

[zzz999]

Hey I change some settings to delay between catch, speed, etc with config.json opened in Notepad++ Then it override my seetings! Why the hell is always asking to reload config.json what kind of changes are made, on config.json?!

---

2 suggestions:
a) create LastPos.ini files
b) on Log files, write Location (lat/long) on (Caught) entries.