-
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
Bot fails to recognize the new type of softban #3902
Comments
We're working on this. Decent amount of the current work is avoiding the softban altogether, but hopefully we can get some PRs in to detect the variety of new bans. |
2016-08-14 10:31:54,484 [PokemonGoBot] [INFO] [api_error] Session stale, re-logging in. is part of their new technics to get bots down right ? One each quarter of hour. |
I have a different ban type, bot is able to spin the fort, although It doesn't receive any items |
Forget about what I've said, It seems a inventory-related bug |
Should be detected now. Please reopen if you notice it is not. |
I found sth interesting, I am soft banned today(Can spin fort, but pokemon vanished after first toss), but only for less than an hour, maybe even shorter(I didn't try during that time), compared to yesterday, which lasted for more than 10 hours, it might have sth to do with the bot keeps running even it can't catch any pokemons, because last time I was letting the bot running all night, while this time I terminate the bot right after I found it was banned, the bot keeps running even it can't catch any pokemon is obvious not a human behavior, can we fix that? Maybe log out and re-login after an hour or so
Expected Behavior
Bot is able to recognize the new ban, and logout/terminate, re-login after a customize time period
Actual Behavior
The bot failed to recognize the new type of ban, and keeps running even can't catch any pokemon, which might extend the softban time.
The text was updated successfully, but these errors were encountered: