failed to login ptc
failed to login ptc
whats the new speed to use to avoid being banned?
I been running 8 for 2 hours, then 10 for 2 hours, now 15 for 2 hours... I heard 50 might be the max but IMO 20 might be the max.
Also I disable "catch out of range pokemon" idk if that is sniping or not but I believe it will increase your chances of soft/perma bans
Well one thing i can confirm is:
i used this bot for around 5 hours last night
all options ticked apart fromn (camping at lures & evolving)
25 KM/H
50-60k Per Hour
I got IP banned multiple times, but im using a VPN, so i just changed country of VPN, still going...
----
Going to try and see the parameters for the IP ban and try 20KMH for a while
that akward moment when you change the transfer rules to IV, but forget to change the '200' ****
Okay so here is my findings:
Running this bot so far for 2hr25m
Switzerland VPN
All ticked but camping at lures and evolving
15km/h
35k per hour xp
Running in a park in london (balbasaur spawn)
DO NOT TRY TO RUN MORE THAN 1 ACCOUNT PER IP, ITLL AUTO IP BAN YOU AFTER ABOUT 30MIN
Any additional info needed, feel free to ask
Going out now with bot left on, see what happens
Last edited by Chrisizzle; 08-13-2016 at 07:55 AM.
15km/hr is a ban too
Currently testing 10km, working for 2hours no issues so far @ 36k XP PER HOUR
i think should config < 30 exp/h.and <10 km/h
Something programmed into this bot is causing catch flee ban, running 6hours30min, no other ban than the catch flee ban, poke stops still working, catching Pokemon however is an issue...
We need to find out the issue
Other than this I can confirm catch flee doesn't seem Perm as my first account got in catch flee banned
Last edited by Chrisizzle; 08-13-2016 at 06:56 PM.
7KM/H Seems to be the optimal, ran it for 7hours nearly, no issues....
XP/H was only 20k but it worked...
To devs: change up the catch luck and make it so its not 210XP everytime for a catch
Edit: around 10 hours of running = catchflee ban... pretty sure its the 210XP catch thing
Last edited by Chrisizzle; 08-14-2016 at 08:01 AM.