Difference between one and all objects

[LB]

It works because you are using a condition from the object itself (so it generally selects the related objects) and not compare two general values (doesn't select objects).

[FlinkGigitty]

Can you give an example from the very same event except this time it compares two general values?


PS: What is ABS? I remember something about the number always being positie.. Does it mean the cordinates always goes positive on each side?

[LB]

Abs stands for Absolute, eg Abs(-2) is 2. In math this looks like |-2|

"Compare two general values" it the name of a condition under the special object:


And it lets you compare one value/string to another value/string:


It looks like this in the event editor:


It does not select objects.

[FlinkGigitty]

Okay.. I was hoping you were refering to something else, because this condition is something I have never ever used..

I have been reading and researching a lot about this, but I have not found an absolute rule. So far, it really looks like all depends on how the event is looking. Sometimes, the order of what is overlapping what is important, and sometimes the use of flag or values are important. I guess all I can hope for is a later update with a button "all objects" or "individual object" or something..

[LB]

No, that won't happen. I have taken the time to explain everything to you. There is no rule. You simply have to learn what does and doesn't select objects, and how the object selection system works.

[FlinkGigitty]

You are right.. And I really did not mean to sound ungrateful! Ok Im gonna try again and see the important part.

Here is the image I linked earlier:



This did not work correctly. The result was every box was destroyed, and every place were a box was placed, a fastloop was created.

Earlier today, I did a new try of copying the working event from my previous game, and this time I succeed. Here is the working event:



(The transparent events are something I have added later, and is totally unrelated to the issue I had).

...

I did a test, to check if it was the group that made the difference, but for some weird and annoying reason, the event works now with just the box. Unless I was very tired and unfocused yesterday, I can swear to God I had the exact same event back then, and not working. Let me just ask.. If you would decide if these events should work or not, would you say that the first image wont work, and the second will do just fine?

This post got a little messed up because I did a double check and I fell a little out of my main subject..

[LB]

Neither should work. On both, all object should be destroyed and also it won't work for when you have more than one object. I'll make a quick example showing a way that should work every time regardless of the setup or qualifiers.

EDIT: OK here is the example. http://mfa.aquadasoft.com/view/1279658894-BreakEnemies

[Dynasoft]

Yeah, we've said before that the "start loop" action screws up other actions in the same event so that they can happen on the wrong (e.g. all) objects.

You must have missed us saying that...

[FlinkGigitty]

Well, no, I didnt miss that.. But as I said, the second picture works, even with a "start loop".


Wow, thanks! So this "ForEach" object is to prevent the reset in the "start loop" ?

[LB]

No, the ForEach object just runs a loop for every object that was selected when you used the action. It select one objct at a time and lets you do actions to it that way.