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

Auto Walk doesn't properly handle onLostControl #943

Closed
leijurv opened this issue Feb 24, 2019 · 3 comments
Assignees
Labels
Milestone

Comments

@leijurv
Copy link
Member

@leijurv leijurv commented Feb 24, 2019

  1. be auto walking
  2. be freecamming
  3. do .b come
  4. notice that it just stops and doesn't come
  5. notice that you have to do .b come again for it to do it
@ZeroMemes

This comment has been minimized.

Copy link
Member

@ZeroMemes ZeroMemes commented Feb 24, 2019

CustomGoalProcess has a higher priority than AutoWalkProcess this is an interesting one.

@ZeroMemes ZeroMemes added this to the 4.6 milestone Feb 24, 2019
@leijurv

This comment has been minimized.

Copy link
Member Author

@leijurv leijurv commented Feb 24, 2019

Btw this works fine for auto mine, doing .b come stops it and makes it come over, only auto walk needs to be told twice

@ZeroMemes

This comment has been minimized.

Copy link
Member

@ZeroMemes ZeroMemes commented Feb 24, 2019

Fixed by Leijurv in 4.6

@ZeroMemes ZeroMemes closed this Feb 24, 2019
@leijurv leijurv modified the milestones: 4.6, 4.5 Feb 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.