I couldn't tell you exactly what's going wrong there, but from the looks of it Construct might be getting confused that there's so many "Enemy"s running around. The problem's probably in picking instances of it. I have trouble with that myself, so I'll save us all the headache of me trying to offer a solution.
i'm not sure, but i believe it's the order of your events for the animation.
you destroy the enemy, then you try to make reference to it, for spawning. i think you have to make your references first while it still 'exists', then destroy it. you can make it invisible while you do your spawning.
not sure exactly but feels like construct is not picking the right instance . Least that's what it seemed like when I recreated your example. But I did get it to double the way I expected by making each Spawn action a sub-event of the initial Event as a way to keep it picking the original if that helps. example .capx
Warning the example .capx makes a lot of sprites rather fast. onzephyr2011-10-08 03:26:07
I would say that the ordering and unspecific instructions are the problem, but I've tried with and without a For Each condition and it functions pretty much equally (I left it in though). I've placed the destroy event before and after the creation events, same thing.
So I changed it from the object itself spawning the new objects to simply creating them with the system create object action. what you can do with spawn object from object you can do with system create object, just better imo. I think there may be an issue with how c2 picks objects that are created by other objects. However, I'm just guessing.inkBot2011-10-08 09:52:35