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.

Sign up for GitHub

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

Jump to bottom

Wrong move in fights #36

Closed
FastFrench opened this issue Nov 23, 2012 · 1 comment
Closed

Wrong move in fights #36

FastFrench opened this issue Nov 23, 2012 · 1 comment
Assignees
@FastFrench

Comments

@FastFrench
Copy link
Member

Even in fights, the truncation of the path to CurrentMP steps max doesn't work.
Will be fixed on my next commit/push

But we should also handle GameMapNoMovementMessage message, and avoid to update the position when GameMapNoMovementMessage is received (meaning that the path is refused for some reason).
@ghost ghost assigned FastFrench Dec 7, 2012
@FastFrench
Copy link
Member Author

Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@FastFrench FastFrench

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@FastFrench