triggerTimeoutCurrent: Difference between revisions
Jump to navigation
Jump to search
Killzone Kid (talk | contribs) (note -> informative) |
m (template:command argument fix) |
||
| Line 20: | Line 20: | ||
| [[Number]] - time remaining before trigger activation. | | [[Number]] - time remaining before trigger activation. | ||
|= | |RETURNVALUE= | ||
|x1= <code>_remaining = [[triggerTimeoutCurrent]] _trigger;</code>|= | |x1= <code>_remaining = [[triggerTimeoutCurrent]] _trigger;</code>|EXAMPLE1= | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| [[triggerTimeout]], [[setTriggerTimeout]], [[waypointTimeoutCurrent]] |= | | [[triggerTimeout]], [[setTriggerTimeout]], [[waypointTimeoutCurrent]] |SEEALSO= | ||
| |= | | |MPBEHAVIOUR= | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
}} | }} | ||
Revision as of 10:38, 7 April 2019
Description
- Description:
- Returns current timeout of the given trigger or -1 if countdown is not in progress.
- 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.