Nah, all 3 Path Movement Conditions have this problem sadly

I was under the impression that all Red Events would loop through Instances automatically ( like a collision Event does ).
Either that assumption is wrong or the Pathmovement is somewhat bugged or diverges from this ruleset for some other reason.

...
The only extencion-free method of doing this, apparently, is the way suggested by me and examplefied by BigHatLogan ( MultipleCollisionProblem3-1.mfa‎, five posts up ).
Although there is a seemingly random lag of 1 Frame... :I

I guess ill just submit and use the ForEach, it seems its the best and most stable option.
By using the ForEach i can drop the 'Damage Tokens' completly also.

Although it didnt work out quit the way i wanted to i got pretty close.
Man why do i waste my time on silly stuff like this, well im a bit smarter at least.
Thanks guys, for all the help!

https://dl.dropbox.com/u/3537859/InstantRedEvent.mfa
( Frame 1 contains the 'Animation has ended' method, while Frame 2 contains the flawed 'Active has reached the end of its path method' )