correct as is "Random" condition constantly evaluated

[Bungle_uk]

When setting random as a condition for trigger, it is constantly re-evaluated as if it were a continuous action even though the trigger is set to "once"

In the mission and track provided, there are 2 triggers:

First is set to "Once" "Time more, 10 seconds" and "Random, 1%" with an action of message to all 1

Second is set to "Once" "Time more, 20 seconds" and "Random, 1%" with an action of message to all 2

What happens is a message of "2" appears around the 2 minute mark and a message of "1" at about 2:20

This suggests to me that the conditions are constantly evaluated instead of just once at that time.  Reading the manual, that's not how it should work it seems
"RANDOM. The Random condition allows you to set a percentage chance of action(s) assigned to the trigger from happening. Use the left and right arrows or type directly into the field to adjust the value. Values can range from 0 (no chance) to 100 (certain) as a percentage. The most common action you will use this condition with is Activate Group. This will allow you to set a random appearance of units in a mission."

testrandom.miz random.trk

[Rudel_chw]

21 minutes ago, Bungle_uk said:

When setting random as a condition for trigger, it is constantly re-evaluated as if it were a continuous action even though the trigger is set to "once"

Correct, the trigger type "once" means that the action part of the trigger is executed only once, the trigger disappearing from the execution flow afterwards. But that doesn’t mean that  the condition part of the trigger is evaluated just once .. it will be evaluated once per second, until it becomes true or the mission ends.

[toutenglisse]

47 minutes ago, Bungle_uk said:

...This suggests to me that the conditions are constantly evaluated instead of just once at that time...

Your issue (and also mine as I used to think like you) is that "time more than" is not "at that time", and it means that this condition is true from "the time" and after that, just waiting for random to be reached (eval. 1/s) to do the action. If you want a rondom evaluation at a precize time only you need other condition (example "mission start", only true at mission start, or, less simple, time > 10s - activate flag / time 1s since flag - deactivate flag / flag true and rondom - message)

24 minutes ago, Rudel_chw said:

Correct, the trigger type "once" means that the action part of the trigger is executed only once, the trigger disappearing from the execution flow afterwards. But that doesn’t mean that  the condition part of the trigger is evaluated just once .. it will be evaluated once per second, until it becomes true or the mission ends.

100%

[Bungle_uk]

I see.  Looks like I need to find another way then.  I have done some experimenting with the percentage value on the unit itself which seems to work better for my needs.  Thx for the responses.   Its more clear to me now.

 

Edited April 4, 2022 by Bungle_uk