Looting Pokestops Failed Only in New Update
In the past, I've seen the weird, " looting pokestops ...(insert random combination of characters and numbers). Trying again." error message. But it happened only once every so often. But with this new build, I all of a sudden got this error like 6 times in a row at different pokestops. (please see attached log file, "2016-09-06_T19_14_07.txt ") I saw on one post that someone with that error turned out to be soft banned. So I went and tried the old 126 version from a few days ago instead. (this log file is titled "2016-09-06_T15_45_29") Besides a paras that ran at the first ball, the bot was able to catch about 5 pokemon successfully in the first few seconds of starting the program. Then, the bot successfully looted 4 pokestops so 126 showed that I wasn't soft banned and everything was good. I'm not sure why version 128 has these problems.
I decided to switch to version 126 because of 2 other problems I saw on 128. On 128, if a pokemon escaped, the bot within 1 second could throw 6 pokeballs at the pokemon (which does not look normal at all and definitely makes it look suspicious) and every single time I logged in, the bot would say something like "pokemon hatched from egg" ( please see this attached 2016-09-06_T19_14_07.txt file) although there wasn't even an egg that was currently being incubated. So I felt 128 was a little weird.
These are the three issues that I've noticed with this new update so I'm currently sticking to version 126 until a new update, unless I'm told these issues are actually not bad. Should I put this in the requests subforum as well? I really hope that I can hear a reason/solution for why the bot failed to loot the pokestops because I'm afraid of the bot making me more likely to be banned.
Thanks in advance!
View attachment 2016-09-06_T19_14_07.txtView attachment 2016-09-06_T15_45_29.txt
In the past, I've seen the weird, " looting pokestops ...(insert random combination of characters and numbers). Trying again." error message. But it happened only once every so often. But with this new build, I all of a sudden got this error like 6 times in a row at different pokestops. (please see attached log file, "2016-09-06_T19_14_07.txt ") I saw on one post that someone with that error turned out to be soft banned. So I went and tried the old 126 version from a few days ago instead. (this log file is titled "2016-09-06_T15_45_29") Besides a paras that ran at the first ball, the bot was able to catch about 5 pokemon successfully in the first few seconds of starting the program. Then, the bot successfully looted 4 pokestops so 126 showed that I wasn't soft banned and everything was good. I'm not sure why version 128 has these problems.
I decided to switch to version 126 because of 2 other problems I saw on 128. On 128, if a pokemon escaped, the bot within 1 second could throw 6 pokeballs at the pokemon (which does not look normal at all and definitely makes it look suspicious) and every single time I logged in, the bot would say something like "pokemon hatched from egg" ( please see this attached 2016-09-06_T19_14_07.txt file) although there wasn't even an egg that was currently being incubated. So I felt 128 was a little weird.
These are the three issues that I've noticed with this new update so I'm currently sticking to version 126 until a new update, unless I'm told these issues are actually not bad. Should I put this in the requests subforum as well? I really hope that I can hear a reason/solution for why the bot failed to loot the pokestops because I'm afraid of the bot making me more likely to be banned.
Thanks in advance!
View attachment 2016-09-06_T19_14_07.txtView attachment 2016-09-06_T15_45_29.txt
Last edited:
