Quick answer: Construct 3 Pathfinding behavior frozen after a Recalculate action? Recalc cancels active movement; you must call Move Along Path on the completion trigger.

An enemy chases the player, sees a moved obstacle, calls Recalculate, then sits still. The recompute fired but didn’t restart movement.

Recalc Plus Move

The flow: call Find Path or Recalculate. On the On path found trigger, call Move Along Path. Recalc doesn’t imply movement.

Path Found Trigger

Wire your event sheet: Enemy on path found -> Enemy: Move Along Path. Otherwise the path is computed and discarded.

Cell Size Tuning

Pathfinding cell size affects perf. Smaller cells = more accurate path = more compute. Match cell size to your gameplay grid.

Diagonal Movement

Behavior settings include diagonal allowance. Toggle on for natural 8-direction movement.

Verifying

Recalculating mid-chase resumes pursuit on the new path immediately — no idle frames.

“Recalculate isn’t start. Move Along Path follows on the success trigger.”

Group “Find + Move” into a single function script in event sheets — calling it from anywhere is reliable.