destroy on collision and count objects = bug?

I have 6 fruits on screen, and a platform player.

When collisioning with a fruit, I destroy it, and checking to see if the Count is 0. However, I never reach Fruits.count = 0 sub-event when it's nested under the "on collision" trigger. When I put the Fruits.Count = 0 outside (every tick), this works just fine.

Doesn't work (actually the Text value in the trigger is one behind. If I had 6 and destroyed one, it will still show 6):

Works:

Any ideas? Is this expected?

It's expected since when you destroy an object it's not removed till the next toplevel event.

So right below event 25 in the first image, or right below event 23 in the second.

Yea R0J0hound is right. Easiest fix. Create a global variable called "count" or somithing.

On collision

->set Count to 1

in a new top leve event,

Count = 1

-> set text to Fruits.Count

-> set count to 0

Thanks, both of you, bummer I have to create another event at the top instead of its appropriate logic place

You don't have to place it at the top of the event sheet. Top-Level event means it's not a sub event.

Fruits.count = 1, works, because the destroy is uncontional.

In fact, it is Fruits.count - 1 = 0, accounting for the not actual destroyd one yet, since it is a sub event.

tunepunk, yeah, I meant top level

99Instances2Go, that's cool, already albeit awkward. Question is: can I ABSOLUTELY count on it that it will be 1? I COULD check < 2, so if by any chance it's a 0....

< 2 is fine for that 1 time on 600 biljon trys it might be zero. Afraid you still dont understand why though, so by next revision of your code it might be 9.