I'm about to lose my mind!

Sorry Construct. Pathfinding behavior is a complete disaster. I'm disappointed.

https://dosya.co/5jdmqbup4anr/Test_Pathfinding.c3p.html

What about this?:

Hi.

I understand that you want the player to move at the click of the mouse, and the enemies are constantly approaching him.

I see that your enemies are able to attack at a distance, for this you made a distance check?

In general, I understood how to understand, there all simply periodically (every 0.5sec) all enemies look how far they are from the hero and if more than 100 then they go to him.

Download File *.c3p

The Enemy sprites behave very consistently with the way you prepared them. As far as I understand, when creating the event conditions, instead of running all events together, setting each as a sub-event of the other and creating an algorithm makes them behave more logically.

_________

What about this?:

I haven't seen a sprite get stuck in a wall yet with this method, they move fine. I like it but they go through walls.

This is all confusing to me. I've watched all the tutorials and read all the topics, but it seems like there's no one way to do somethin

True. Try adding the 8direction behavior to the enemy sprite. They can't go through walls with that.

The 8direction behavior doesn't seem to be the right choice for finding the path. It's not possible to make the enemies chase and escape in 8 directions.

I tried to combine the pathfinding behavior with the car or bullet behavior, of course it was very laborious and complicated. It didn't work the way I wanted.

The only way to make enemies chase me in complex terrain is through the pathfinding behavior, and it works terribly in Construct.

All my work went to waste because of the things I wanted to do but Construct couldn't.

The way Superxonic did it seems to work fine on my PC.

The enemies going through the wall is due to their rotate speed being slightly low. I had to set it to 500-600 and everything seems to work good.

The 8direction behaviour tip it's just so they dont go through walls. Seems to work fine on my side.

The 8direction behaviour tip it's just so they dont go through walls. Seems to work fine on my side.

Subscribe to Construct videos now

There is something I don't understand:

All events and actions remain the same. Just adding 8 direction behavior solves the problem of getting stuck in solids. Is that right?

8direction behavior tries to prevent them from colliding with solid objects, yes. But it's a workaround, not a solution to your problem. Your pathfinding grid is probably not configured correctly. See the official documentation:

construct.net/en/make-games/manuals/construct-3/behavior-reference/pathfinding