StrongHarm Posted July 27, 2022 Posted July 27, 2022 I have a feeling I'm doing a Rube Goldberg with this method, so could someone adept with the mission editor kindly check me please? I'm working on an Apache mission (Israeli Defense - Seek and Destroy) with a couple dozen voice acted radio transmissions/text messages. Mission has a lot of randomness Under certain circumstances Radio Messages are getting stepped on by new Radio Messages To prevent overlap of message triggers I created trigger with TYPE:SWITCHEDCONDITION / CONDITION: Time Since Flag (13,62) / ACTION: Flag Off (13) In all of my message triggers TYPE:ONCE / CONDITION: FLAG OFF (13), &otherConditions / ACTION: FLAG ON (13), &otherActions This method successfully prevents a message type trigger from going off until 2sec(minimum) after a running message finishes. Question: Am I missing something? Is this message overlap prevention trigger even necessary? Am I Rube Goldberging this to death? Thanks for the assist. It's a good thing that this is Early Access and we've all volunteered to help test and enhance this work in progress... despite the frustrations inherent in the task with even the simplest of software... otherwise people might not understand that this incredibly complex unfinished module is unfinished. /light-hearted sarcasm
Recommended Posts