Skip to content
This repository has been archived by the owner on Jul 30, 2020. It is now read-only.

Bot keeps catching after 998 pokemons #37

Closed
petpetpetvm opened this issue Sep 9, 2016 · 13 comments
Closed

Bot keeps catching after 998 pokemons #37

petpetpetvm opened this issue Sep 9, 2016 · 13 comments
Labels
Milestone

Comments

@petpetpetvm
Copy link

I saw the bot tried to catch pokemons after 998 pkms (as my setting)
I saw it said pkm catch : 999/998 and after that is whole list of catch flee but not stopping
I couldn't copy the note (because i turned it off asap)
Anyway, its seem like a bug that we need to work on
Thanks

@Silph-Road
Copy link
Contributor

post your config and log.
Follow the template provided

@Silph-Road Silph-Road added this to the Issue Needs Verification milestone Sep 9, 2016
@LobsterX
Copy link

LobsterX commented Sep 9, 2016

check your logs. its there..... paste it here and let us review it for you.

normally when i hit the 998thj pokemon, i'll let the bot rest for 4-8hrs hrs. then i delete the PokemonTS and PokestopTS files and run necro again. these 2 files are the ones keeping track of the no. of pokemon caught and pokestop farmed.

but if your main error is the catch flee, even when you use a real device and try to catch pokemon and it flees, it means you're soft banned.

Stop playing that account and login-ing in to see for a few hours....

@petpetpetvm
Copy link
Author

It's not in the logs :/ i couldn't find it, but i'm sure that it was...
for the config, i use really fast config and it runs only 1hr every 15hrs

@petpetpetvm
Copy link
Author

1

@petpetpetvm
Copy link
Author

maybe there is a bug on counting, it keeps saying 999/998 over and over again

@petpetpetvm
Copy link
Author

@LobsterX so i will have to keep delete those files everyday ?
Thanks

@hardknoxni69a
Copy link
Contributor

is this bug verified dont want to update if its catching past limit

@petpetpetvm
Copy link
Author

I think it's the problem on counting only

@LobsterX
Copy link

@petpetpetvm i do not see any catchflee errors in your SS.

the counting's faulty. just delete the 2 files.

@petpetpetvm
Copy link
Author

petpetpetvm commented Sep 10, 2016

It's not in this one, it happened again, thats why i screenshoted this one
Maybe the other one is real catching ban
however, i dont think the bot will actually stop when there are 998 pokemons catched (in 2 different sessions in same day), maybe it's the reason i got catch flee

@mo0ojava
Copy link
Contributor

I have fixed this but saw that there were merge conflicts that I have to solve. Not at home atm but will likely have some time later today.

@mo0ojava
Copy link
Contributor

#42

@CreativiTimothy
Copy link
Contributor

CreativiTimothy commented Sep 10, 2016

It happens to me too. Steps to reproduce: Wait 1470 minutes (or whatever you set it to) after having caught 989 Pokemon, and then it then the counter will show up like that 998/998

@mo0ojava mo0ojava mentioned this issue Sep 10, 2016
mo0ojava added a commit that referenced this issue Sep 11, 2016
@ghost ghost modified the milestones: Completed, Issue Needs Verification Sep 12, 2016
Lord-Haji pushed a commit to Lord-Haji/NecroBot-1 that referenced this issue Apr 26, 2017
Furtif added a commit to Furtif/NecroBot that referenced this issue May 20, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants