Construct tells them apart by using conditions to filter only the instances that met the event.
[quote:1ol6augh]Is it just like TGF's rather poor method of using Spread Values[/quote:1ol6augh]
You rarely, if ever, need to use spread values in Construct - have a look at the 'For Each Object' condition.
[quote:1ol6augh]collide with another object semi-automatic way that you must design your whole code around[/quote:1ol6augh]
I don't understand this, what's the specific problem you are talking about? Hazarding a guess, you might be interested in the advanced collision system condition, which allows you to choose which objects involved in the collision get picked in the event.
[quote:1ol6augh]I remember reading something somewhere saying that Construct has an unlimited amount of actives available and without any slow-down, is this true?[/quote:1ol6augh]
It's true that Construct supports an unlimited number of sprites, and you don't need to specify any limit. However, if you're drawing them all on the screen, there will of course be a slowdown. Construct isn't magic, if you have twice as many objects, it'll probably take twice as long to draw them all! We've worked hard to try and make it as fast as possible, though.
[quote:1ol6augh]if I wanted to, I could just code the whole game according to each seperate active object, using as many as I need to, correct?[/quote:1ol6augh]
I don't really understand... you want to code each instance separately? I wouldn't advise that. The best way to go is to use ordinary objects, use Families to group together the related ones (like Friendly and Enemy), and code your events around the families. You can use event sheet includes to have your family events affect the entire game, and it saves you repeating events.