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

**META** Stuck between two forts / Moving to 2 forts at the same time / Constant Loop #3308

Closed
cmezh opened this issue Aug 9, 2016 · 13 comments
Labels

Comments

@cmezh
Copy link
Contributor

cmezh commented Aug 9, 2016

Edited by moderator

Please keep all discussions about being Stuck between two forts / Moving to 2 forts at the same time / Constant Loop in this issue only, do not create new issues or they will be closed without warning.

At this stage it's hard to tell if the issue is related to the hard / soft ban waves happening or if it's an actual issue with the bot

Other current META issues:

#3682 - META Server busy or offline issues
#3308 - META Stuck between two forts / Moving to 2 forts at the same time / Constant Loop
#3700 - META Soft bans - Try again spins / Pokemon vanishing
#3746 - META Banwaves - Permanent Bans

@designer2k2
Copy link

walk is to high, for me the same if i put it anything above 20

@cmezh
Copy link
Contributor Author

cmezh commented Aug 9, 2016

But I don't think it's normal behavior, even with high walk.

@wearysky
Copy link

wearysky commented Aug 9, 2016

Same thing happens to me, my walk is set to 4.16.

@binaryn3xus
Copy link

Yeah, two of my accounts keep just walking and catching pokemon but they don't seem to collect pokestops.

@gorcsev71
Copy link

gorcsev71 commented Aug 9, 2016

kepernyofoto 2016-08-10 - 1 32 18

same happens to me. it approaches pokestop "A", then while it is getting closer, all of a sudden it aims to another one (pokestop "B"), then it navigates exactly between these two pokestops (equal distance from both) and gets to an infinite loop: one step towards pokestop "A", then one step towards pokestop "B". It never ends.

@takenek
Copy link

takenek commented Aug 11, 2016

Same here :-(
I upgrade to newlatest version from git and still same problem.
Bot can`t choice between 2 Pokestops because there is this same distance....

Other Information

OS: Debian SiD
Git Commit: d7cb7df
Python Version: Python 2.7.12

Best Regards
TaKeN

@RedViper9
Copy link
Contributor

Hey folks, if any of you are still having this problem, try one of the changes suggested in #3646 . Let me know how it goes.

Forcing a manual location change by deleting the cached location file in data will get you out of the jam, if nothing else...

Related: #3394

@binaryn3xus
Copy link

Yeah this helped me. You can also just change the location in your config file as well. I use coordinates so i just change the last decimal number and restart.

@accident12123
Copy link

I can't speak for ban behavior but I get stuck where i'm standing with forts when there is 2 or more lured pokemon. It just stands there.

It starts to move again one of the following happens:

  • only 1 lured fort pokemon remain (sometimes)
  • It's able to catch enough without moving to get back to 1 lured fort pokemon remaining
  • something else starts me moving again, like movetomap and a new priority pokemon appeared somewhere.

i'm also 90% positive that I've probably spun these forts that have a lured pokemon and the fix might be to allow walking to a already spun fort if there is a lured pokemon detected and don't spin it.

@k4n30
Copy link
Contributor

k4n30 commented Aug 14, 2016

@accident12123 what commit are you on? A lot of the issues that were causing this have now been / are being fixed through rewrites and refactoring of the logic

@designer2k2
Copy link

Having this also! d6c5bb3

constantly getting stuck between 2 lured forts:

2016-08-14 18:46:57,739 [CatchLuredPokemon] [INFO] [lured_pokemon_found] Lured pokemon at fort Heilige Notburga (24e5c7fd0bf3427c8459c09461988813.16)
2016-08-14 18:46:57,740 [CatchLuredPokemon] [INFO] [lured_pokemon_found] Lured pokemon at fort Dom Statue (f97020b24084439aa0719b1099bc2b85.11)
2016-08-14 18:47:00,411 [CatchLuredPokemon] [INFO] [lured_pokemon_found] Lured pokemon at fort Heilige Notburga (24e5c7fd0bf3427c8459c09461988813.16)
2016-08-14 18:47:00,413 [CatchLuredPokemon] [INFO] [lured_pokemon_found] Lured pokemon at fort Dom Statue (f97020b24084439aa0719b1099bc2b85.11)
2016-08-14 18:47:01,914 [CatchLuredPokemon] [INFO] [lured_pokemon_found] Lured pokemon at fort Heilige Notburga (24e5c7fd0bf3427c8459c09461988813.16)
2016-08-14 18:47:01,915 [CatchLuredPokemon] [INFO] [lured_pokemon_found] Lured pokemon at fort Dom Statue (f97020b24084439aa0719b1099bc2b85.11)
2016-08-14 18:47:04,792 [CatchLuredPokemon] [INFO] [lured_pokemon_found] Lured pokemon at fort Heilige Notburga (24e5c7fd0bf3427c8459c09461988813.16)
2016-08-14 18:47:04,793 [CatchLuredPokemon] [INFO] [lured_pokemon_found] Lured pokemon at fort Dom Statue (f97020b24084439aa0719b1099bc2b85.11)
2016-08-14 18:47:07,266 [CatchLuredPokemon] [INFO] [lured_pokemon_found] Lured pokemon at fort Heilige Notburga (24e5c7fd0bf3427c8459c09461988813.16)
2016-08-14 18:47:07,266 [CatchLuredPokemon] [INFO] [lured_pokemon_found] Lured pokemon at fort Dom Statue (f97020b24084439aa0719b1099bc2b85.11)
2016-08-14 18:47:09,730 [CatchLuredPokemon] [INFO] [lured_pokemon_found] Lured pokemon at fort Heilige Notburga (24e5c7fd0bf3427c8459c09461988813.16)

@sffetlio
Copy link

I have this problem on fd9d7e3

@mjsaber
Copy link

mjsaber commented Aug 15, 2016

One workaround is to disable CatchLuredPokemon.

@k4n30 k4n30 closed this as completed Aug 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests