triggerTimeoutCurrent: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<dl class="command_description"> <dt></dt>" to "<dl class="command_description"> <dt></dt>") |
Lou Montana (talk | contribs) m (Text replacement - " \| *(([^=\| ]+)('''|\[\[)([^=\| ]+)) * +\|p1=" to " |s1= $1 |p1=") |
||
| Line 13: | Line 13: | ||
{{Feature | important | The trigger could be [[local]] or remote but the result returned by this command will be for the current trigger timeout local to the client that executed the command. See [[createTrigger]] for more info.}} | {{Feature | important | The trigger could be [[local]] or remote but the result returned by this command will be for the current trigger timeout local to the client that executed the command. See [[createTrigger]] for more info.}} | ||
| [[triggerTimeoutCurrent]] trigger | |s1= [[triggerTimeoutCurrent]] trigger | ||
|p1= trigger: [[Object]] - trigger object | |p1= trigger: [[Object]] - trigger object | ||
Revision as of 00:28, 13 June 2021
Description
- Description:
- Description needed
- 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.