triggerTimeoutCurrent: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<dt class="note">([^<>]+) " to "<dt class="note">$1</dt> ") |
Lou Montana (talk | contribs) m (Text replacement - "\{\{( *)Important( *)\|" to "{{$1Feature$2|$2important$2|") |
||
| Line 11: | Line 11: | ||
| Returns current timeout of the given trigger or -1 if countdown is not in progress. | | Returns current timeout of the given trigger or -1 if countdown is not in progress. | ||
{{ | {{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 | | [[triggerTimeoutCurrent]] trigger | ||
Revision as of 03:12, 7 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
- See also:
- See also needed
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.