Skip to content
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

Bad handling with L30 accounts for status 0. #2396

Open
urinella opened this issue Dec 13, 2017 · 0 comments
Open

Bad handling with L30 accounts for status 0. #2396

urinella opened this issue Dec 13, 2017 · 0 comments

Comments

@urinella
Copy link

Right now we have two stages while accounts are getting banned.
First the account is totally blind and causes bad scans. After a lot of scans the account gets temporary banned. Normal scanning can escape from this first stage with --max-empty.

But L30 accounts only get's "status 0" and try to encounter again and again.
There was an error encountering Pokemon ID XY with account XXXXX: 0.

Expected Behavior

If an account from the L30 pool getting status = 0, ignore this account in the current pool and try to reencounter the Pokémon with the next L30 account.

Current Behavior

Stage 1 banned accounts getting status = 0 and trying to encounter all Pokémon until the account is fully temp banned.

Possible Solution

Modify the exception handling to reencounter a Pokémon and kick status = 0 accounts out of the pool.

Steps to Reproduce (for bugs)

  1. Encounter enough Pokémon for 24h
  2. Wait
@urinella urinella changed the title Bad handling with L30 accounts Bad handling with L30 accounts for status 0. Dec 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants