-
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
RuntimeError: Stopped at Pokestop and did not find experience #758
Comments
I can confirm this problem. It's happening on the latest Dev. |
Same problem experienced |
I would love to track down what this problem is. If anyone else has some insight, that would be very helpful. This message is triggered from here: https://github.com/PokemonGoF/PokemonGo-Bot/blob/master/pokemongo_bot/cell_workers/seen_fort_worker.py#L102 |
The bot no longer walks. We get soft banned because it's teleporting itself too quickly. |
I don't think thats the problem because restarting the script immediately lets it start working again. |
Hmm. That may be the problem. Working on some math. |
Let us know. I'll decrease my speed |
same here |
Fix: #762 |
I can confirm kaise's problem. It is literally teleporting. That's gonna fuck us FAST. |
#762 fix didn't worked here. |
#721 doesn't work either. |
Was this pull request tested before it was merged? I had the issue appear on the 2nd pokestop it visited. |
Please switch to master branch. We're still working on fixing this issue. |
@TheSavior I think your last merge solved that issue ? can you confirm ? |
I believe it should have fixed this. Please reopen if that is not the case |
as title says
"RuntimeError: Stopped at Pokestop and did not find experience, items or information about the stop cooldown. You are probably softbanned. Try to play on your phone, if pokemons always ran away and you find nothing in PokeStops you are indeed softbanned. Please try again in a few hours."
my account just fine but keeps getting kicked out by bot after updating c5a7109 to 586a0dc
The text was updated successfully, but these errors were encountered: