Mission objective success for protecting an AI aircraft

[Billsponge1972]

  In mission 2 of my Escape mini campaign, I wanted to create a mission success by protecting the stationary 190d9 Dora from attacking aircraft. I'm able to get a "mission failed" if the attacking aircraft destroy it but cannot figure out how to get a mission success if it survives the battle.

  Is there a way to do this? I'm unsure of how the "cover" command works but maybe that's my answer?

I'm hoping to upload a final version.

 

 Thanks ahead of time for any guidance on this. I'm still pretty new to the mission editor.

 

[Sketch]

So you're going to need a win condition...

 

Do the players win after a certain amount of time?

 

Do the players win if they destroy all the enemy planes?

 

Or is there some other win condition?

 

Once you know how the players can win then you can set up that logic.

 

[AEthelraedUnraed]

Exactly that. In terms of mission logic, this win condition could be a set timer MCU, a counter MCU triggered by the OnKilled events of enemy aircraft, a CheckZone detecting when all enemies have left the area, a ComplexTrigger detecting when the player lands, or any other requirements or combinations thereof. Then simply link that logic to an objective succeeded trigger.

Edited March 10, 2023 by AEthelraedUnraed

[Billsponge1972]

Thanks for the replies.

My objective setup is;

 

1: A secondary success for destroying all 5      of the attacking aircraft.

2: A primary mission failed if the Dora is          critically damaged.

  The issue arises when the attacking aircraft are destroyed and the Dora survives. If the Dora is destroyed, and I have destroying the five attacking aircraft as a primary objective, then the mission is a success when the Dora was destroyed. ?

Which is why I made destroying the attacking aircraft a secondary objective.

  I thought about a complex trigger with a "object finished stationary and alive" but can't object link it to the Dora. 

 What exactly is "finished" in the complex trigger? Is that when you use a "mission end" MCU? I don't understand the complex trigger. ?

 

 

 

 

 

 

 

[AEthelraedUnraed]

5 hours ago, Billsponge1972 said:

Thanks for the replies.

My objective setup is;

 

1: A secondary success for destroying all 5      of the attacking aircraft.

2: A primary mission failed if the Dora is          critically damaged.

  The issue arises when the attacking aircraft are destroyed and the Dora survives. If the Dora is destroyed, and I have destroying the five attacking aircraft as a primary objective, then the mission is a success when the Dora was destroyed. ?

Which is why I made destroying the attacking aircraft a secondary objective.

Nope, that won't work. To get a mission success, you need a primary objective. 

The proper way to do this is to use a Disable MCU to prevent triggering the mission success when the Dora is destroyed.

 

So, you've got something like this:

Dora OnKilled -> Mission Failed

Logic -> Counter MCU -> Mission Success.

 

Just add a Disable MCU that you trigger from the OnKilled event, and target-link it to the Counter MCU.

[Billsponge1972]

Thank you very much!

I will try that tonight after work and post back.

[Billsponge1972]

So I'm a little confused. Do you mean trigger deactivate? I don't see a disable MCU. 

 

 

[JimTM]

4 hours ago, Billsponge1972 said:

So I'm a little confused. Do you mean trigger deactivate? I don't see a disable MCU. 

 

 

 

Yes, I believe AEthelraedUnraed is referring to the deactivate trigger MCU.

[Billsponge1972]

Thanks to the both of you!

Still haven't been able to work on it but I'll let you know how it goes.

[AEthelraedUnraed]

Sorry, I meant the Trigger:Deactivate MCU indeed.

 

This is the setup I would use to do what you want:

 

If you know something of boolean algebra, programming, electronic gates, or logic in general, it can help to look at a Trigger:Counter MCU as an AND or OR gate, and a Trigger:Deactivate MCU as a NOT gate. It's easy to construct these gates:

 

AND:

Output is triggered when both Input 1 or Input 2 have been triggered.

 

OR:

Output is triggered when either Input 1 or Input 2 are triggered.

 

NOT:

Output is triggered when Input 1 is triggered, but not if Input 2 was triggered earlier.

 

NOT (other version):

Output is triggered when both the Trigger (i.e. a timer that goes off when you want to check this) and Input 1 have been triggered, but not if Input 2 was triggered earlier.

Edited March 11, 2023 by AEthelraedUnraed

[Billsponge1972]

  I can't thank you enough AEthelraedUnraed! 

  Not only for your skills but also for your willingness to help out noobs like me!

  I probably spent 2 hours or more goofing with the logic with no joy.

  I pretty much copied exactly what you posted and I'm trying it out now.

Learning all the time thanks to people like you on this forum. ?