-
Notifications
You must be signed in to change notification settings - Fork 15
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
follow_path: loitering option #23
Comments
Thanks for bring this back @ukos-git. I've yet to look through the issues that @anakin5 was trying to solve when he changed the loiter feature, seems like it might not be possible now. I agree that the loiter feature should allow bot to walk if users chooses, but let's not blame @anakin5 for thinking that loiter doesn't move, since the word I suggest we add the old loiter back, and at the same time improve on our docs to tell users clearly that the bot will behave differently based on what task arrangement they have. |
Agreed. Maybe the term loitering is to blame, I'm not native in English so it may have connotations I didn't expect. By the way, in master loitering with a polylinewalker doesn't work properly, I'm trying to find out what's wrong. |
I was just using the term blame because of the git blame command which is btw one nice feature. No offense. |
+1 for changing the name to 'wander'. |
It is ok for me as well. We just have to return Success instead of running. |
repost of the lost issue PokemonGoF/PokemonGo-Bot#5416
brief summary:
There is a misunderstanding of the use of the loitering functionality.
@alexyaoyang, myself and the original author of the loitering option wanted to use it to let the bot handle other running tasks. current master has this functionality. It is also explained in the docs.
In dev the loitering was changed to really do nothing at all besides catching pokemon etc. so the running task was held further active.
The newly changed behaviour should also be the case if no running task at all is added after the loitering. Therfore I would like to revert the old loitering behaviour if @anakin5 agrees who's to blame.
Any thoughts maybe from @janpascal
The text was updated successfully, but these errors were encountered: