Killing 1 enemy destroys everything?

So here's this glitch that is really bothering me. Sometimes, when I kill an enemy, almost every other enemy dies. But that's the problem. Almost.

I'd understand if all the enemies would die, because the code looks like this:

https://www.dropbox.com/s/3ew3mfr4ziw3x ... emcode.png

(There's also an hpMissile variable, which is basically deducted from when you hit something with a missile, but I didn't use it.)

And it's easy to assume that in the action, C2 thinks that it needs to destroy all the instances of the "Hurtables" family, and not the one that was specified in the condition, aka got its health to less than 0. But in this case, only a select few die, while some enemies are still alive (huge success?), which makes no sense. Here's a video:

Thank you.

What is the 'hpMissle' variable for, what other events change that?

Otherwise, try adding a for each. I doubt it would work for something like this, but it might if your 'Hurtables' have different hp values.

Also, here's the capx (All the basic enemy hp code is located in the "Common Sense" group).

https://www.dropbox.com/s/nwnozh79qnucu ... er085.capx

Sumyjkl

The hpMissile variable is there for times when I want to create an enemy that is impossible to kill with regular weapons, but dies from 1 missile shot, aka hp=9999999, hpMissile= 1.

I'll try the For Each now.

The for each seems to work, not sure why since it only seems to be instance problems when it does the same thing to everything.

[attachment=0:1wel0gaw][/attachment:1wel0gaw]

The For Each helped! I didn't include the hurting itself into the loop, though.

But it's really strange the glitch even occurred, So umm, Ashley ? This might be interesting.

Your events are wrong: 'hp <= 0 or hpMissile <= 0' is true every tick, and 'Wait' does not block the events. So if it waits for 1 second, it will be true every tick for 1 second (about 60 ticks). That means it queues up 60 waits and executes 'Destroy' 60 times. I guess executing 'Destroy' repeatedly is not what you're after.

Ashley the Wait is usually and in this case 0 seconds. Does that still cause glitches?

I'm not sure, why would you want to wait at all before destroying it? Since it's a variable wait time, when it's nonzero you'll still see that problem. It's just not a pattern of events that you should be using.

Thank you very much.