Should I add a new event or add actions in same event?

Get help using Construct 2

Post » Tue Aug 08, 2017 8:58 am

mekonbekon wrote:You don't need to move those conditions. they should stay where they were before. You only need to move the on destroyed condition and its associated actions to be a main event.

heh ok @mekonbekon
I don't understand because I think this event is under another and inherits everything. So as I move, I will not inherit those conditions (trigger once, live, type).
There is many ways to move it:

I'm not very smart at this hierarchy.
Posts: 229
Reputation: 2,571

Post » Tue Aug 08, 2017 9:45 am

Are your enemies destroyed in any other event where lives are not <=0 or Type is not <=1? If not then it doesn't matter that the "on destroyed" event isn't nested and the other conditions aren't needed.

If you have more than one type of enemy, or enemies are also destroyed in other events where their live value is greater than one then I'd use something like this:

Enemies|On destroyed:
>Lives <=0:
>>Type <=1: Do A
>>Type =2: Do B

>Lives >0:
>>Type <=1: Do C
>>Type =2: Do D

The "On Destroyed" condition would be a top level event. Exactly how you order the rest of the hierarchy is dependent upon the conditions you have set up for destroying the different enemies: you may want to switch it instead to have the Lives conditions nested under the Type conditions.

What you definitely don't need is the "trigger once" condition with the "On Destroyed" condition, as "On Destroyed" will only trigger once per enemy that is destroyed anyhow.
Posts: 515
Reputation: 4,472


Return to How do I....?

Who is online

Users browsing this forum: j1elliott and 1 guest