I'm encountering the same problem where it says I've timed out for 3 min and no server response.
I have a feeling the server has found us and are implementing softban on Ninjabot users.
We believe in you, though, MisterNinja! Keep the good stuff up!
cannot evo pokemon.
Screenshot_2.jpg
from yesterday i hav no problem at 4 m/s speed till morning, then i stopped. an update to pokemon go v33 came. it says it detects fast driving. on my observation when i tried again, i used 1.000 m/s speed and it works again when in logged says ranges 27-41 meters, but when it reaches 50 meters up ut happens again, maybe theres a clue in my observation about the problem now.
i tried 0.500 m/s to lessen the meters but the bot says it cant set it lower than 1.000. maybe if it can lowered then the bot is usable for a meantime while fixing the problem in new pokemon update.
maybe server? is this status down or something now?
now it runs smooth, i used the old v16. maybe there is something in v17 that is detectable by them? when i use v17 after some minutes like 5-10 it happens again, the no response from server thing.
edit 1: change to 3.000 m/s still runs smooth.
Last edited by ayamsupremo; 08-10-2016 at 10:54 AM.
its gives java problem how can i fix it
update java on your pc
Would it be possible to add the functionality that the bot will ignore Pokestops, if the bag is full?
From level 30 and above, I'm not really looking to add XP that much. Rather, I'm searching for specific Pokemons like Dratini's, but want to keep the bot running, without having to check if it has enough Pokeballs.
Also, a priority list for Egg's. Example; it will always auto-incubate 10k's first, then 2k and finally 5k
Last edited by YoungDaneCph; 08-10-2016 at 11:16 AM.