The infamous IDLE issue. Today i did an experiment to tr y and pinpoint the problem and find a solution for the community. Some of us receive it and theres many hypothesis on how to fix it and what exactly it is. I believe its a softban due to how its remedied and what exactly occurs during this event. From the pictures i took when an account is in IDLE mode no pokestops show up and no pokemon show up, the symptoms of a softban. The fix also points to a softban as it requires you do something else for a while or just run another account for 30-60 minutes. (note: mods ask you to clear bags and delete settings folder as well as add an anchor point which may work for some: Pics included 2 different accounts in the same location, one with the IDLE issue one without Pic 1:softbanned pic 2: second account same location same time NOTE: nothing appears in pic one at all no stop no mon no nearby (pics were edited for safety) TLDR: idle is sometimes a softban, bot safer or do something else if it happens
Yes i believe we have been explaining this to a few people. Also if you log in and out to fast (like 2 or 3x in 5 min or test settings or anything) you will get hit with a login captcha and same thing happens. You have to go to your game to fix it as it doesn't show up on Pokefarmer it does what he is talking about above (has happen to me now a few times). ^^
@Mods want to clean this up and sticky it or add to faq?I know you have the team looking into it for a future release but this among other things get posted daily. As well as special characters in the passwords currently/ soft and from bags full also did not upload the pictures unless it's because of mobile attempt 2 Imgur: The most awesome images on the Internet Imgur: The most awesome images on the Internet
That is not the symptoms of a softban. Softban they both still show up, you just get the 'Try again later' message when you spin a pokestop, and pokemon will flee after the first catch attempt.
There are two types of softban, this one and the one you're talking about. The one you're bringing up is due to moving too fast. This one is due to input commands I'm guessing as well as catching and spinning more than a certain amount per set amount of time
