triggerTimeoutCurrent: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\{\{( *)Important( *)\|" to "{{$1Feature$2|$2important$2|") |
Lou Montana (talk | contribs) m (Text replacement - "\| *((\[\[[a-zA-Z0-9_ |()]+\]\],? ?)+) * \}\}" to "|seealso= $1 }}") |
||
| Line 21: | Line 21: | ||
|x1= <code>[[private]] _remaining = [[triggerTimeoutCurrent]] _trigger;</code> | |x1= <code>[[private]] _remaining = [[triggerTimeoutCurrent]] _trigger;</code> | ||
| [[triggerTimeout]], [[setTriggerTimeout]], [[waypointTimeoutCurrent]] | |seealso= [[triggerTimeout]], [[setTriggerTimeout]], [[waypointTimeoutCurrent]] | ||
}} | }} | ||
Revision as of 00:05, 17 February 2021
Description
- Description:
- Description needed
- Groups:
- Triggers
Syntax
- Syntax:
- Syntax needed
- Parameters:
- trigger: Object - trigger object
- Return Value:
- Return value needed
Examples
- Example 1:
private _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
- 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.