-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possibly searching too often all the time #3990
Comments
I've been getting this too since last Friday. I think one of my account is flagged and it does this quite often. Whereas the other one is fine. They are running on different IP. |
Please use the issue template so that we can help you. I only see one occurrence of the "Possibly searching too often" and you haven't provided configs or any other detail for us to help at all. |
{
} |
Expected BehaviorDone Actual BehaviorDone Your config.json (remove your credentials and any other private info)Done even though you left your gmap key in there Steps to ReproduceOther InformationOS: Also, can you provide a longer log, as there was only one instance in your OP - This is far from a bot issue |
I had this earlier as well. It happened once. But then everything worked fine since then. Maybe it was some network issue. I was logging in and terminating the app pretty fast. |
Could be something softban related. How long did you run the bot before you noticed the issue? |
I can confirm that this issue is a new soft ban. Information I collected
@k4n30 I would suggest here a soft ban enhancement to stop the bot if "pokestop_searching_too_often" triggers 3 or 5 times in a row. This is 100% the indicator for this soft ban. Config I used for the test's
|
It's an IP ban. I have to change my IP everytime this 'searching too often' error. |
If you're running multiple bots, this will cause this issue, or if your heartbeat is set to low (newer commit) |
Today after last "git pull" CONFIG`{
} LOG
|
@k4n30 UPD |
Got this error on latest release commit: 3bf3138. Changing IP works for me again. Have to change it twice. I'm only running 1 bot account and heartbeat is set to 10 |
Expected Behavior
spinning the pokestops
Actual Behavior
Moving to the pokestops and says: possible searching to often. But it catches pokemon
2016-08-15 12:51:40,384 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Verschlungen - 0.05km
2016-08-15 12:51:42,278 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Verschlungen - 0.05km
2016-08-15 12:51:45,237 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Verschlungen - 0.04km
2016-08-15 12:51:47,098 [ SpinFort] [INFO] [pokestop_out_of_range] Pokestop Verschlungen out of range.
2016-08-15 12:51:47,102 [ SpinFort] [INFO] [pokestop_searching_too_often] Possibly searching too often, take a rest.
2016-08-15 12:51:47,309 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Struktur - 0.06km
2016-08-15 12:51:50,826 [PokemonCatchWorker] [INFO] [pokemon_appeared] A wild Pidgey appeared! [CP 76] [Potential 0.42] [A/D/S 5/10/4]
2016-08-15 12:51:53,641 [PokemonCatchWorker] [INFO] [threw_pokeball] Used Pokeball, with chance 68.91 (65 left)
2016-08-15 12:51:53,901 [PokemonCatchWorker] [INFO] [pokemon_caught] Captured Pidgey! [CP 76] [Potential 0.42] [5/10/4] [+210 exp]
2016-08-15 12:51:54,147 [PokemonCatchWorker] [INFO] [gained_candy] You now have 624 Pidgey candy!
2016-08-15 12:51:59,194 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Struktur - 0.05km
2016-08-15 12:52:00,838 [TransferPokemon] [INFO] [future_pokemon_release] Releasing Pidgey [CP 76] [IV 0.42] based on rule: CP < 500 AND IV < 0.8
2016-08-15 12:52:01,118 [TransferPokemon] [INFO] [pokemon_release] Exchanged Pidgey [CP 76] [IV 0.42] for candy.
2016-08-15 12:52:02,887 [MoveToFort] [INFO] [moving_to_fort] Moving towards pokestop Struktur - 0.05km
The text was updated successfully, but these errors were encountered: