TEMPEST.114 Posted April 21, 2024 Posted April 21, 2024 (edited) With these new CONDITIONS, you would use them to group up a collection of conditions that must be met for it to pass, BUT you are able to have multiple OR and conditions after, that will have this collection applied to them. e.g. TRIGGER CONDITION ACTIONS ONCE COLLECTION START FLAG ON ("InCountryAltitudeBusted") PART OF COALITION IN ZONE(BLUE, HOSTILE_TZ, AIRPLANE) FLAG IS FALSE ("HornetFlightSafe") FLAG IS FALSE ("HornetFlightDetected") COLLECTION END UNIT'S AGL ALTITUDE HIGHER THAN (TEMPEST, 1500) OR UNIT'S AGL ALTITUDE HIGHER THAN (MAVERICK, 1500) OR UNIT'S AGL ALTITUDE HIGHER THAN (PHOENIX, 1500) OR UNIT'S AGL ALTITUDE HIGHER THAN (ROOSTER, 1500) This means that for every CONDITION underneath the 'COLLECTION END' everything from COLLECTION START to COLLECTION END is applied to each of them, without the need for duplicating all of those conditions inside each 'OR'. It is of course, possible to have two triggers, one for the collection to set a flag, and the other trigger with all of the UNIT's AGL OR statements, but then you have to add the newly created flag to each of them and duplicate that. This way, you cut down on needless duplication and also one extra unnecessary trigger. Of course, you might have a more elegant solution... ETA: Of course, if you added 'GROUP' level altitude conditions, then this example wouldn't be required, but there are many times that you need to do something like this. Edited April 21, 2024 by Elphaba
Recommended Posts