-
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 seems to wander aimlessly #1619
Comments
Do you have evolve_all set to "all"? If so, might be related to #1586 |
@mrseeker I do not, I have had these defined as This is happening to me since I updated just now to the latest Edit Doesn't it usually say how many objects it found in the area? it just says |
What's your config? |
|
its km/h not m/s maybe thats the reason ? |
Correction: It is related to #1586, posted a possible fix there. |
@Philipp59 I haven't changed that value since the beginning (also I'm from the netherlands so I work with km/h too) 4.16km/h seems like walking speed to me? |
you are right i set the speed up to 40 km/h and resulting to this: [13:49:41] Arrived at Pokestop [13:50:02] Arrived at Pokestop [13:50:23] Arrived at Pokestop [13:50:44] Arrived at Pokestop [13:51:04] Arrived at Pokestop [13:51:27] Arrived at Pokestop [13:51:52] Arrived at Pokestop [13:52:16] Arrived at Pokestop so its ignoring move settings ? |
@mrseeker yours is actually walking to a fort though, mine isn't (I know the pattern of how the bot should be walking, plus I'm kinda in the middle of nowhere so there arent a lot of pokestops nearby either). It's just walking.. to nothing |
Guys, please check #1586, I am calling this a duplicate... |
@xorinzor And if you turn evolve_all off, will that change behavior? For me it had the same issue when it booted up... It started going north in a very slow pace due to the evolve_all being constantly triggered. EDIT: At at 0.1km/h pace, before it found a pokestop in its vicinity and then started to walk towards it. |
@mrseeker again, it's not related since yours is moving to a fort, mine isn't. it seems to not even detect any objects in my area. Also I set |
i have same problem, |
I let it run for a while, and it took 4 minutes for the bot to detect objects in the area, now it walks back towards them and seems to function as intended again. Not sure what is going on in the meanwhile during those 4 minutes, but it doesn't seem to be good. |
Mine walks to one pokestop, then starts moving to another and suddenly decides to switch to the previously visited pokestop...
|
Okay, just let me get facts straight here:
If thats the case, then its most likely Niantic having network issues. If not, then it might be that your location is too far from a pokestop (I don't know the maximum range for a pokestop to be visible). |
@mrseeker no, it wasnt in range of a pokestop, the pokestop was south of the bot and it just started walking north, then after 4 minutes it detected the fort and started walking back towards it. Right now it seems to be working though, so it may indeed have been some external factor causing it to wander aimlessly. |
Expected Behavior
To walk towards pokestops and catch pokemon in the meanwhile
Actual Behavior
Very, very slowly it just walks north, but isn't actually going to a pokestop
Steps to Reproduce
Just run the latest dev build
Other Information
OS: Win 10 x64
Git Commit: c548334
The text was updated successfully, but these errors were encountered: