-
Notifications
You must be signed in to change notification settings - Fork 317
Add clearance detection and option in search method - #45
Open
wibimaster wants to merge 3 commits into
Open
Conversation
jorbascrumps
commented
Mar 1, 2017
Have you been able to improve accuracy on this, @wibimaster?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
To move character bigger than 1x1 tile, I had to write a clearance detection.
The clearance of each Node is stored at the Graph init, and we can use a "clearance" value in the search options.
This script works for 2x2 tile for example, but isn't very accurate for 2x1 or 1x2 sized character.
Maybe someone can help me to optimize this a little more too ;)