Check vars when instances of same object collide?

cacotigon

le sigh. this is C2 weakest part. The fact that events are not bound to an object. I know in standard programming for objects. They all have there own functions. oh well :P we will work around it :)

ChrisAlgoo: me? Try this link

I was referring to vee41, but thank you!

I was referring to vee41, but thank you!

Fixed it, shows pretty much the same thing people posting after me did :)

Thanks everyone! I think we can all agree that working around this requires some hella inelegant stuff. I'll ask Ashley to do... something to make it easier. I'm not sure what, but he's the genius programmer here so hopefully he can find something!

Actually, once you've done the variable check, how do you tell C2 which Sprite you want to do work on? (Destroy, or adjust variable, or etc)

The same of your other topic, you can use instance variables, pick by UID or other stuffs doing the same.

scirra.com/tutorials/361/understanding-uid-iid-health-cards-and-rocket-smoke-trail

I'll work on a sample for you today (21:00 GMT +3), hoping to help, because this was an issue on my life when I began here too.

Thank you so much!

ChrisAlgoo, I've noticed that this type of question seems to come up every once in a while on the forums, so I've written a tutorial to hopefully clarify the confusion.

Understanding Picking with Respect to Families

The tutorial not only covers how to distinguish between identical objects within single events, but why it's important from a modular design standpoint.

That was extremely awesome, thank you.

dl.dropboxusercontent.com/u/47035927/Samples/IDs/sample2/index.html

dl.dropboxusercontent.com/u/47035927/Samples/IDs/sample2/filtering_IDs.capx

Ignore the messy coding in the event sheet. There's some kinks I need to iron out. i think it's because I started out with limited variables and started adding more i got confused so the information that shows up are wrong and the variable assigning is screwed up as well.

You may noticed that sometimes a smaller object > bigger object (so big is destroyed)

but you get the idea (i hope)

https://dl.dropboxusercontent.com/u/18773252/VarCheck.capx

i'll try to fix it later.

ChrisAlgoo

You're very welcome. I also added a new section to the bottom of the tutorial where I discuss the performance aspects and advantages of Family to Family collision detection.

As I was searching the forums for a solution I found this thread, and I was wondering if this lack of a simple solution regarding families colliding with families happens only in Construct 2 or in other programs too as it is sort of a programming quirk?

Solomon

Only Construct has this because it follows a different pattern to other programming languages. Namely Construct uses object lists that you filter with events, so if you want to pick one particular instance you'll have to filter the list down. Other programming languages only deal with only one instance at a time so you'd end up using lots of loops to compare instances with instances.

Personally I like using families to pick a different instance of the same type and I wouldn't mind seeing a way to do it in events without the need to setup a family beforehand. In my mind I'd like an overhaul of the event system so it's easier to learn and more powerful, but the exact details of such a proposal will have to wait till I've ironed out all the details, but in such a design I'd make something like this situation more trivial.