I have a few things to say. If that is ok, without been called a pain.
https://www.dropbox.com/s/3rkurb2i4y2u3 ... .capx?dl=0
1/ The property 'rotation speed' in the pathfinding behavior is rather slow. Since it has to rotate 180 degrees before it is able to move at all, it has a very slow start. The property 'Rotation object' is set to 'no', so, it seems like nothing is happening. In reality, the behavior is lining up with 180 degrees at the given 'rotation speed'.
I rotated that object 180 degrees in the layout, so you can see the difference. Now it dont have to rotate before moving.
2/ That generated obstacle map is ready the next tick. Not in the same tick as you use that regenerate action. So, you have to wait till the next tick before initiating that 'find path' action.
To do this, one possibility is (since one expects the events to run top-down) to use a boolean and place a pathfinding action in an event that checks that boolean above the event that contains the regeneration action.
Now you would think ...
This tick ....
Boolean is true ? ... find path (gets skipped, because boolean is not yet true)
On enter pressed ... regenerate and set boolean
Boolean is true ? ... find path (it runs now because the boolean is now true) And it will find a path that accounts for the obstacles -, because the obstacle map is build in the previous tick.
But that is not what going to happen at all. The 'on keys pressed' is a trigger. And keyboard triggers happen (once) at the start of a tick. So, the 'On enter pressed' will happen before the 'Boolean is true ?', yet the ''On enter pressed' event is in the event list placed after the 'Boolean is true ?'
Lesson: Be very careful with triggers when the logic depends on the order of the events.
That is why i changed the trigger to a non-trigger in my example.