Why does the killswitch goes back to 1 in count when i ran it. I've changed the killswitch value to 900 pokemons but when it reaches 99/900. it suddenly goes back to 1/900. so it means the count will be not verified? -_-
Why does the killswitch goes back to 1 in count when i ran it. I've changed the killswitch value to 900 pokemons but when it reaches 99/900. it suddenly goes back to 1/900. so it means the count will be not verified? -_-
i got softbanned too, that i can't get any items on pokestop. got sotbanned loop twice. i try off the bot for 1-15minutes, then starting again, it works. but seems the new API easily detected. and so often API throttling calls been showed almost three times. avoid use bot , it's monday, the staff is on working and monitoring us.
I think the problem with the walkingspeed is just a problem with the calculation. I think the bot is calculating the distance directly from A to B but the bot is not going directly from A to B ... I get around 6800/h with 6.16 km/h.
It's better to go slow but without ban (no ban with this account within one week).
It should calculate the time needed for distance using the route details from Google Maps. Maybe still using the old way of calculating distance and time.
id is banded.. :gusta: just on for around 2-3 hours/day ..need to play a new and clean acc for now..![]()
Just checked a walking road on googlemaps to compare with what the bot says and the results:
Bot : 272sec 704m
Google maps: 600sec 800m
Google map uses about 5kph My config uses about the same. Google maps info was right in my case and bot wasn't.
The bots actual runtime is equal to the google map predictions
Anyone getting this pretty often?
[18:05:12] (ERROR) Pokemon Servers might be offline / unstable. Trying again...
[18:05:13] (ERROR) Error: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at System.Collections.Generic.List`1.get_Item(Int32 index)
at PoGo.NecroBot.Logic.Tasks.FarmPokestopsTask.<Execute>d__4.MoveNext() in E:\Projetos\CSharp\NecroBot\PoGo.NecroBot.Logic\Tasks\FarmPokestopsTask.cs:line 89
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotificat ion(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at PoGo.NecroBot.Logic.State.FarmState.<Execute>d__0.MoveNext() in E:\Projetos\CSharp\NecroBot\PoGo.NecroBot.Logic\State\FarmState.cs:line 68
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotificat ion(Task task)
at PoGo.NecroBot.Logic.State.StateMachine.<Start>d__3.MoveNext() in E:\Projetos\CSharp\NecroBot\PoGo.NecroBot.Logic\State\StateMachine.cs:line 57
Also I can see that its not always taking a logic road for the pokestops. Sometimes just passes(ignoring) one to go to one more far. I can see this happening with NecrobotVisualizer.
Last edited by cheater007; 08-21-2016 at 11:17 AM.