Home   Help Search Login Register  

Author Topic: min, max and mid....  (Read 466 times)

0 Members and 2 Guests are viewing this topic.

Offline bedges

  • Administrator
  • *****
    • OFPEC The Editing Center
min, max and mid....
« on: 20 Jan 2005, 20:15:53 »
can anyone explain just what the max, min and mid terms are for in the 'countdown' part of a trigger? i realise it's for waiting a predetermined amount of time after the trigger conditions are met, but what are the values for, and how does one use them?

i have looked in the tutes section btw :P

thanks meantime
b

Offline macguba

  • Former Staff
  • ****
    • macguba's operation flashpoint page
Re:min, max and mid....
« Reply #1 on: 20 Jan 2005, 20:23:50 »
The countdown fields of a trigger mean that there will be a delay between the trigger being fired (i.e. condition field satisfied), and the consequences occurring (i.e. on activation field exectuting.)

The trigger waits for a random time:  that time is more than min, less than max, and likely to be somewhere near mid.

If you toggle the field to Timeout instead of countdown, then it means that the trigger condition must be satisfied for that time before it fires.     This is rarely used, whereas Countdown is very common.

Confusingly, Waypoints have a field called Timeout which in fact operates like the Countdown in triggers.   At least I think it's all that way round.

Trigger countdown example:

Countdown     3     20     10
Condition:   testVar
On Activation:   hint "gotcha!"

When the variable testVar becomes true, a hint saying "gotcha" will appear.    The delay between the variable going true and the hint appearing will always be between 3 and 20 seconds, and will usually be around 10s.
Plenty of reviewed ArmA missions for you to play