Is it a feature that "For Each" iterates through instances selected by the event?

[Blizna]

I just noticed that and I am not sure whether that is the intended behavior (and I hope so as it makes sense, yet I cannot find any documentation):

If an event selects objects (like Enemy collides Enemy), the ForEech enemy only iterates through those two enemies.

If the object is not selected by the event (like Timer>0), then all Enemies are iterated with ForEach enemy.

I ask as I have seen so many answers where people state "it goes through all instances".

[zip2kx]

I would suppose so, since you are scoping down to the ones colliding it has no reason to go further than those two objects.

[marbenx]

If an event selects objects (like Enemy collides Enemy), the ForEech enemy only iterates through those two enemies.

If the object is not selected by the event (like Timer>0), then all Enemies are iterated with ForEach enemy.

Yeah the for-each loop will only run on the two objects affected by the collision (or whatever objects were scoped down by the initial conditions).

If you wanted to go outside that scoping but still have the event trigger from something like a collision (e.g. when two objects collide you wanted *all* of those objects to be destroyed, not just the two individual objects), you could separate it out to a regular fast loop in a separate line which will ignore the scoping

[BartekB]

Yes, that's the intended effect.
Since For each loops are actions within an object. Only those currently scoped will execute it.

E.g. Event that doesn't have any "Active 2" conditions. It is assumed that all "Active 2"s will be affected by given actions.
Event that does have conditions for "Active 2". Only "Active 2"s that pass that conditions will execute the actions.

[north]

Aww, is this stemming from my question? Flattered. For the longest time (until you showed me otherwise yesterday, actually), I assumed ForEach was just a more convenient way to fast-loop through objects...and I guess I assumed this because, like you said, it's not clearly documented anywhere I could find. It makes a lot of sense, in retrospect, but I'd definitely add it to any "tips and tricks" lists.

[Blizna]

Aww, is this stemming from my question? Flattered. For the longest time (until you showed me otherwise yesterday, actually), I assumed ForEach was just a more convenient way to fast-loop through objects...and I guess I assumed this because, like you said, it's not clearly documented anywhere I could find. It makes a lot of sense, in retrospect, but I'd definitely add it to any "tips and tricks" lists.

Indeed it is, I realized I was not sure whether the solution I suggested to your problem - although working well - is intended to be working that way. Happy to know it is.