On a side note, this is the one thing I dislike most about Construct. I personally find the event system hard to use when you have many of the same object, such as in this instance. You used a family to solve this problem, but why did it work? If I needed to do this myself, I would have ended up doing it the way I told you above, and resulted in a crash. Next, I'd try all kinds of craziness with private variables and whatnot, but some things in Construct just don't seem intuitive to say the least.
This coming from an old Gamemaker user, so needless to say, I'm used to each object working independently without having to work out which ones will be affected by the global event sheet. Construct is so much better in so many ways, but manipulating individual instances is hard for me to wrap my head around with the event system controlling everything.
I switched form GM in mid January so slightly a head of the curve from you.
I found it hard to switch but see the power. And still find GM scripting easier, but can not do so many things in GM that I can do in Construct, so hang in there.
Try this to understand Families:
http://sourceforge.net/apps/mediawiki/c ... e=Families
But also look at Containers:
http://sourceforge.net/apps/mediawiki/c ... Containers
They will make you sprite life easier
The other important thing that will make you project much easier to handle is using event sheets and including them.
Oh and start small and grow. You will learn faster that way.