Add weights to nodes to influence search paths #151
Conversation
…arFinder to use the new weights. Weights above 1 (the default) make a node less desirable (cost more expensive) to use but not unwalkable. Weights less than 1 make a node more desirable (cost less expensive) to use.
|
Would love to see this merged as well as #100 |
|
It looks like this repo is not maintained anymore by Qiao. Can someone just fork this and the active community could rebase the project on this new repo ? I'd like to see lots of those pull requests merged too and this repo isn't evolving anymore since months. Otherwise just give sign of life please. |
|
I've just been using a fork for ages. It works for my needs and so I'm not too bothered by it. But yeah, sucks to see real improvements not getting merged. |
|
As far as I know, @imor was maintaining, he's had the latest commit to master. |
|
First of all apologies for not merging in the changes. I've been very busy with other priorities and can't and won't find time to maintain this repo. @qiao started this repo but I haven't seen him active either since a long time. If someone else is willing to maintain it please contant @qiao to know if he's willing to transfer the ownership of the repo. |
|
So? :) |
I added a weight value to each node. These weights are used in A* based finders and the Jump point base finder when calculating the next g value for a given node.
I did this because the finders tend to hug the walls of obstacles in the grid. This may not be the most desirable behavior so by using individual weights you can influence the paths the finders evaluate. This can encourage, but not require, the finder to stay a bit away from the walls when searching for a path.
For some reason my editor seems to have changed white space in some of the files which causes diff to think they are all different. Honestly this is only a few lines of changed code.