[BEHAVIOR] EasyStar.js pathfinding for tilemap

Don't worry, that make a lot of sense. However, implementing it correctly will be your next challenge !

Magistross: thank you for this fine pice of code.

I'll use it iwith my new project and it works very well.

Really nice, thanks!.

Just updated ! Check out the first post.

when i enable easystar, i found the cpu usage is very high.

Well to be fair, pathfinding is a cpu intensive operation. You have to keep it in mind when implementing it, and use it in such a way that actual pathfinding operations are done in an optimized way.

All I get is this error when I try to pathfind between two sprite coordinates:

https://drive.google.com/file/d/0Bz86oQ ... sp=sharing

I'm sorry, but without more details on how the behavior was used, I won't be able help you much. The only wild guess I could make right now is that you would get this error if you added the behavior to a non-tilemap object.

Wait I'm supposed to apply it to the tilemap? I was under the impression the objects that use it to move need to have it. I guess I didn't look at your example closely enough.

Note that this is not a movement behavior per say, it's a pure pathfinding one. The movement can be done with another behavior, like moveTo from rexrainbow, or directly through events.

Hi ! I recently stumbled upon this neat little API for pathfinding and thought it would be cool to wrap it up inside a plugin/behavior for C2. I thought a behavior extending the official tilemap made the most sense for this so here goes :

live example (Drag and drop the blue/green square, and right-click to add/remove obstacle.)

example capx

behavior files

easystar demo done in C2 (need moveTo behavior)

live version

The behavior is rather straightforward, just hook it up to a tilemap, define walkables tiles with the appropriate actions and you're set. It uses a tag system so you can make multiple find path calls simultaneously, and EasyStar.js allows for asynchronous calculation if need be. Just try it out !

edit: corrected links, added another demo

New behavior files v1.01

v1.01 has an updated core (now using EasyStar 0.2.3, slightly modified to accommodate C2)

Key features are an optimized algorithm, possibility to add specific costs at tile coordinates, option to enable/disable corner cutting when moving diagonally

Does the example work properly with the updated files? Doesn't seem to draw the route properly?

Can anyone show me an example of how to make a character move to a tile using moveto? I've been studying the second example, and can't quite figure out how to simply make a sprite move through the nodes to a tile?

EDIT: Found one:

Is it possible to make a character move to the nearest walkable tile if you click on an unwalkable tile?

EDIT: got that one too!

Magistross is there a way of smoothing nodes so the tiles dont cause a gridded/quantized motion? I think it's possible, if i'm not mistaken, using lerp?

Hey, Magistross, I'm absolutely loving this plugin! A problem I found, however, was that tiles were unable to be manipulated past a certain point in the layout. Maybe you could shed some light and give a little input on why this doesn't work? <img src="{SMILIES_PATH}/icon_e_confused.gif" alt=":?" title="Confused">

https://www.dropbox.com/s/5se7tp187v9vj ... .capx?dl=0

Oops! I needed to override the "setTileAt" function from the tilemap plugin so EasyStar could track changes made to the tiles. However I mixed up height and width somewhere along the way on the array "overflow" check. Once you reach a width greater than the height, it won't do anything (and vice versa).

Try redownloading the latest file, it should work now.