Navigation
Options
Post Reply
Username:
Verification:
Subject:
Message: [quote author=Nameless Voice link=msg=72645 date=1404093441] NVRelayHaltTimerOnOn / NVRelayHaltTimerOnOff Kills any existing timer (delayed message) when the trap is activated/deactivated. The same fail chance applies to both activation and deactivation. It can fail to send the trigger. Float. They count towards the max trap activation count (NVRelayTrapCount), but not the max trigger activation count (NVRelayTrapTCount). Basically, it builds up a list of all the links, adding each link to the list the number of times specified in its weight. It then picks a random link from that list. NVRelayTrapOn="TurnOn"; NVRelayTrapOff="TurnOff"; NVRelayTrapTOn="TurnOn"; NVRelayTrapOff="TurnOff"; NVRelayTrapDelay=0; NVRelayTrapDelayMax=0; NVRelayTrapOnDelay=0; NVRelayTrapOnDelayMax=0; NVRelayTrapOffDelay=0; NVRelayTrapOffDelayMax=0 There can be multiple delayed messages waiting at the same time. Normally, a delayed message should fire at that number of milliseconds after it was activated, regardless of other messages. Note that I think I noticed a bug with ExclusiveDelay today - it doesn't work as expected if an object has multiple relay trap scripts on it which use delayed messages. I suspect repeating won't work reliably either. (e.g. values relating to timers and repeats are shared amongst all script instances, so an exclusive delay on one will kill timers on another.) It will use the most specific param specified. The code is shared for all of this functionality, there are no separate code paths with more/less features. [/quote]
Back to topic
Legal stuff