TuringBot - Necro Mod- DailyMaxPokemon/Stops Killswitch! Decrease ban chance!

[CH3ATO]

Hey, first of all thanks for the build. It's nice to see the spirit of botting still alive after Necro and a bunch of other people taking leave.

Some ideas for improvements to the bot in order to make us less detectable:

Altitude/GPS jitter:
Introduce jitter to altitude/gps coordinates in order to simulate handheld device more accurately OR get altitude data from GPX path and jitter around that data.

GPX Pathing priority:
A problem with Necrobot (and all other bots) that was never addressed - if using GPX pathing the bot will prioritize capture over movement along the path and eventually get stuck if in a high density pokestop/pokemon area. Bots should be able to continue along the path (and ideally move, probably slower) while carrying out capture instructions, as a human player would do if they were moving through an area.

Restart with saved coordinates on exception:
If an exception is thrown that results in a relog action for the bot, the bot's previous coordinates should be documented (and used on unexpected startup) so that we don't end up teleporting to the default start location when the bot resets. Either that, or provide an option for the bot to require user input before unexpected reset.

Alternatively, if the user cannot be present, the bot can calculate the distance between the last previously documented coordinate and the default start position and implement a login delay corresponding to the distance from the origin.

If possible I'd like to help you with your build/fork of Necrobot. I haven't taken the time to look at the code but I think I'd be able to help out a bit. I understand that for security/safety reasons that wouldn't be entirely possible publicly (what with Niantic's legal action against previous botters).

[swagjord]

I know this could be possible ban but how do I up the EXP/H and P/H caught?

[harryvn3294]

So the program closes?
Cause if it does, it's ez mode to start betting a different account in the mean time

i know, but it should be an option if i want only single account

[harryvn3294]

I know this could be possible ban but how do I up the EXP/H and P/H caught?

Raise move speed, decrease the delay. Choose a crowded location.

[babybash]

Bug

[alextm]

Hwork perfect thx boot 4 h and it,s perfect no ban nothing

[Ripper3]

The kill switch feature should be stop botting but keep the program running until 24h pass from the starting time. So that we could leave the bot totally do the work

This little batch file will autorestart your TuringBot.exe every 24h, so you get it fully automated. TuringBot.exe kills itself, once it hits the daily limits, and this .bat makes it restart every day

Either use this Mega download and drop it straight in your folder with the Turing. exe, or follow these simply instructions:

Manual instructions:
create 24restarter.bat inside the folder with TouringBot.exe.
Edit 24restarter.bat
Paste this inside:

:start
start TuringBot.exe
@echo Starting TuringBot.exe
timeout 86400
:loop
wmic process where (name="TuringBot.exe") get commandline | findstr /i "TuringBot.exe"> NUL
if errorlevel 1 (
@echo Restarting...
timeout /t 1
start TuringBot.exe

) else (
@echo "TuringBot.exe" is already running .
)
timeout 86400

goto :loop

Save

it should look like this:

Don't start the bot via TuringBot.exe, simply run 24hrestarter.bat. It will start TuringBot.exe immediately and then again every 24h, if it's not already running.

Enjoy

[logical0]

This little batch file will autorestart your TuringBot.exe every 24h, so you get it fully automated. TuringBot.exe kills itself, once it hits the daily limits, and this .bat makes it restart every day

Either use this Mega download and drop it straight in your folder with the Turing. exe, or follow these simply instructions:

Manual instructions:
create 24restarter.bat inside the folder with TouringBot.exe.
Edit 24restarter.bat
Paste this inside:

Save

it should look like this:

Don't start the bot via TuringBot.exe, simply run 24hrestarter.bat. It will start TuringBot.exe immediately and then again every 24h, if it's not already running.

Enjoy

this brought a tear to my eye

[zoldikzxz]

This little batch file will autorestart your TuringBot.exe every 24h, so you get it fully automated. TuringBot.exe kills itself, once it hits the daily limits, and this .bat makes it restart every day

Either use this Mega download and drop it straight in your folder with the Turing. exe, or follow these simply instructions:

Don't start the bot via TuringBot.exe, simply run 24hrestarter.bat. It will start TuringBot.exe immediately and then again every 24h, if it's not already running.

Enjoy

hello sir, how about if we want starting bot 3hours and then rest 1hour and start again?
like below??
:start
start TuringBot.exe
@echo Starting TuringBot.exe
timeout 14400
:loop
wmic process where (name="TuringBot.exe") get commandline | findstr /i "TuringBot.exe"> NUL
if errorlevel 1 (
@echo Restarting...
timeout /t 1
start TuringBot.exe

) else (
@echo "TuringBot.exe" is already running .
)
timeout 14400

goto :loop

thx

[dubz221]

can confirm bot is running great after 10h+

Screenshot by Lightshot

Please let me know if it will let you go past level 22. Currently that is the cut off I have and others have with various bots. Sometimes 21 sometimes 22 then you can't go further with the account.

[grobusto]

This little batch file will autorestart your TuringBot.exe every 24h, so you get it fully automated. TuringBot.exe kills itself, once it hits the daily limits, and this .bat makes it restart every day

Either use this Mega download and drop it straight in your folder with the Turing. exe, or follow these simply instructions:

Manual instructions:
create 24restarter.bat inside the folder with TouringBot.exe.
Edit 24restarter.bat
Paste this inside:

Save

it should look like this:

Don't start the bot via TuringBot.exe, simply run 24hrestarter.bat. It will start TuringBot.exe immediately and then again every 24h, if it's not already running.

Enjoy

'
Is it possible to include a delay?

Like 6 hours botting / 6 hours shutdown.

And what about a soft ban detector with some delay?

[Ripper3]

hello sir, how about if we want starting bot 3hours and then rest 1hour and start again?

The following would be an easier way of doing 3 hours of botting, 1 h rest, 3 h botting, and so on.
Just put that code into an .bat file in the folder with TuringBot.exe

:start
start TuringBot.exe
timeout /t 10800
taskkill -f -IM "TuringBot.exe"
timeout /t 3600
goto :start

[zoldikzxz]

The following would be an easier way of doing 3 hours of botting, 1 h rest, 3 h botting, and so on.
Just put that code into an .bat file in the folder with TuringBot.exe

oke thx u sir,

[Ripper3]

'
Is it possible to include a delay?

Like 6 hours botting / 6 hours shutdown.

Yes, that would be possible, but when would you want the delay? Right now, it works, because the TuringBot.exe kills itself, before hitting a softban automatically. If I were to kill the .exe prematurely, the pokemon&pokestop counter would reset, making this bot quite useless.

And what about a soft ban detector with some delay

I cannot include that. It would require bot modification. It cannot be done easily externally.

[grobusto]

Ok, your response to Zolsdikzxz is sufficient.

And is it possible to randomize delays? The bot will be more human! I think it will be an equivalent feature than random speed.