so I'm trying out the tile movement for the first time today.
The pathfinding Grid movement for the "move to" action implements it both by simultaneously addressing both the x and y components resulting in diagonal movement when I want to make my sprite follow 'L' and 'S' paths.
EDIT: I forgot to include the problems I'm encountering:
- the pathfinding for this behavior seems to 'brute force' its way into an obstacle for lack of a better term. in the c3p file I provided, you'll notice clicking on a space behind a solid object the sprite will move along the path but stops as soon as it collides with a solid block instead of trying to find a way around it. this happens both for diagonal and adjacent movements.
There are 2 things I'm trying to do:
1. disable diagonal movement by setting it so the movement tackles X and Y components at a time
2. set a single function for movement that restarts when the condition 'not in position x,y' yet.
it sounds simple enough on paper but somehow I'm having a brain fart over this.
c3p link below: