triggerTimeoutCurrent: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - " *\| *([Cc]omments|COMMENTS|Game|[Gg]ame [Nn]ame( +[0-9])?|Game [Vv]ersion( +[0-9])?|Game Version \(number surrounded by NO SPACES\)|Arguments in MP|MP[Aa]rg|Multiplayer Arguments( \("local" or "global"\))?|Effects|Execution|Effects...) |
Lou Montana (talk | contribs) m (Text replacement - " <h3 style='display:none'>Notes</h3>" to "") |
||
| Line 24: | Line 24: | ||
}} | }} | ||
<dl class='command_description'> | <dl class='command_description'> | ||
<!-- Note Section BEGIN --> | <!-- Note Section BEGIN --> | ||
Revision as of 15:16, 18 January 2021
Description
- Description:
- Returns current timeout of the given trigger or -1 if countdown is not in progress.
- Groups:
- Triggers
Syntax
- Syntax:
- triggerTimeoutCurrent trigger
- Parameters:
- trigger: Object - trigger object
- Return Value:
- Number - time remaining before trigger activation.
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.