Hi!
You uploaded the file with the error, which helped speed up the process.
I took a few screenshots to explain my point.
First, I removed all the extra bee objects and left just one; this lets us change its settings, and whenever it spawns somewhere, those settings will always be the same.
I changed one parameter on the bee, and it flew away.
But I don’t like your spawn function—it’s a total clunker. Any looping function should happen instantly in a single frame; the fact that you added a delay simply interrupts it and restarts it. This isn’t standard practice—it’s a workaround that’s been around since Construct 2.
But we need a reliable solution, and we shouldn’t use any delays in the looping action.
I created a new function, and as you can see, during spawning, we configure the bee and start a timer.
Then, when each bee’s timer expires, it will find its path and start moving.
This is just one of the possible ways to spawn a wave of mobs.
Download the project file
fex.net/s/0ex1myf