Nealius Posted January 23, 2022 Share Posted January 23, 2022 Trigger ONCE, Condition "Part of coalition in zone," commands the Action (signal flare, smoke, etc.) at mission start. Trigger SWITCHED CONDITION, the Action fails even when the Condition is met. So far the only solution I've found is to use "Unit in zone" and add every. Single. Bloody. Unit. Manually. Link to comment Share on other sites More sharing options...
toutenglisse Posted January 23, 2022 Share Posted January 23, 2022 24 minutes ago, Nealius said: ...Trigger SWITCHED CONDITION, the Action fails even when the Condition is met... By opposition to "once" or "at mission start", this trigger does work when condition does switch (from no units to part of coalition in zone). If part of coalition is already in zone at start, the trigger won't detect a switch of condition. (If I understand correctly the case you describe) Link to comment Share on other sites More sharing options...
Nealius Posted January 23, 2022 Author Share Posted January 23, 2022 (edited) That might make sense, as the trigger zone is on two BLUE units, with the action (signal flare) also on that unit. Is there a way to get it to ignore the unit(s) already there? Edited January 23, 2022 by Nealius Link to comment Share on other sites More sharing options...
toutenglisse Posted January 23, 2022 Share Posted January 23, 2022 10 hours ago, Nealius said: That might make sense, as the trigger zone is on two BLUE units, with the action (signal flare) also on that unit. Is there a way to get it to ignore the unit(s) already there? No, as long as these units are blue. They would be ignored if from grey/neutral coalition, but would become non-combatant. A scripted function could be tailored for whatever is required, as a laborious option. Link to comment Share on other sites More sharing options...
Nealius Posted January 24, 2022 Author Share Posted January 24, 2022 Sounds like a scripted function is more laborious than adding each unit with an OR clause in the conditions. Link to comment Share on other sites More sharing options...
Flappie Posted January 24, 2022 Share Posted January 24, 2022 @NealiusPlease attach a mission file showing the issue. Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Nealius Posted January 25, 2022 Author Share Posted January 25, 2022 On 1/24/2022 at 4:46 PM, Flappie said: @NealiusPlease attach a mission file showing the issue. Issue is user error, or so it seems. The trigger zone associated with "part of coalition in zone" was placed over units of that same coalition, causing the trigger to fire at mission start. Link to comment Share on other sites More sharing options...
Flappie Posted January 25, 2022 Share Posted January 25, 2022 Oh, I see. Thanks for your feedback. Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Recommended Posts