Accounts Permanently Banned...What went wrong?
- Thread starter mawro2016
- Start date
friesendeichkind
New Member
- Joined
- Sep 15, 2016
- Messages
- 17
- Reaction score
- 0
But when i didn't snipe, just "walking" in one city, and never use 3rd party software, only the bot?
friesendeichkind
New Member
- Joined
- Sep 15, 2016
- Messages
- 17
- Reaction score
- 0
I "think" it happend between .171 and .173, i can't follow the path at the moment.
There was the new update by Niantics, then the bot was down and a short time later (23h) the bot was up again.
If i follow discord, the first update .170 was incorrect, so .171 followed very quick - for me at night =) so i didn't use .170.
Then at morning we updated the bot to .171 and started farming again - following by update .172, .173 and .174.
A short time later we recognized server issues. Actually we can't connect to that accounts any more, by bot or by phone.
In my opinion, the update release of .170/.171 was to fast, because of the changings of Niantic, there must be an quiet call back to them.
The safety run of the bot was not given because of to less time in "testmode" by the dev's.
After that, i think it was better, to wait - and actually to stop the bot for everyone.
There was the new update by Niantics, then the bot was down and a short time later (23h) the bot was up again.
If i follow discord, the first update .170 was incorrect, so .171 followed very quick - for me at night =) so i didn't use .170.
Then at morning we updated the bot to .171 and started farming again - following by update .172, .173 and .174.
A short time later we recognized server issues. Actually we can't connect to that accounts any more, by bot or by phone.
In my opinion, the update release of .170/.171 was to fast, because of the changings of Niantic, there must be an quiet call back to them.
The safety run of the bot was not given because of to less time in "testmode" by the dev's.
After that, i think it was better, to wait - and actually to stop the bot for everyone.