triggerTimeoutCurrent: Difference between revisions
Jump to navigation
Jump to search
m (GVI 1.06 --> 1.08 http://dev.arma3.com/post/spotrep-00016) |
Killzone Kid (talk | contribs) No edit summary |
||
| Line 25: | Line 25: | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| [[triggerTimeout]], [[setTriggerTimeout]] |= SEEALSO | | [[triggerTimeout]], [[setTriggerTimeout]], [[waypointTimeoutCurrent]] |= SEEALSO | ||
| |= MPBEHAVIOUR | | |= MPBEHAVIOUR | ||
Revision as of 20:15, 7 November 2018
Description
- Description:
- Returns trigger timeout or -1 if countdown is not in progress. Note: The trigger could be local or remote but the result returned by this command will be for the trigger condition set up locally on the client that executed the command. See createTrigger for more info.
- Groups:
- Uncategorised
Syntax
- Syntax:
- triggerTimeoutCurrent trigger
- Parameters:
- trigger: Object - trigger object
- Return Value:
- Number - time remaining before trigger activation.
Examples
- Example 1:
_remaining = triggerTimeoutCurrent _trigger;
Additional Information
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
Notes
- Posted on November 26, 2013
- Killzone_Kid
- Triggers have their own schedule. If you create a trigger with timeout and try to read triggerTimeoutCurrent immediately it will return -1. This is because the countdown will not start until the next scheduled trigger check is due, and this could take up to 0.5 seconds.