triggerTimeoutCurrent: Difference between revisions
Killzone Kid (talk | contribs) (Please remove nwiki tags) |
Lou Montana (talk | contribs) m (Some wiki formatting) |
||
| (41 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{RV|type=command | |||
|game1= arma3 | |||
|version1= 1.08 | |||
| | |arg= global | ||
| | |gr1= Triggers | ||
| Returns trigger | |descr= Returns current timeout of the given trigger or -1 if countdown is not in progress. | ||
| | {{Feature|important| | ||
The trigger could be [[Multiplayer Scripting#Locality|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. | |||
}} | |||
| | |s1= [[triggerTimeoutCurrent]] trigger | ||
| [[ | |p1= trigger: [[Object]] - trigger object | ||
|= | |r1= [[Number]] - time remaining before trigger activation. | ||
|x1= < | |x1= <sqf>_remaining = triggerTimeoutCurrent _trigger;</sqf> | ||
| [[triggerTimeout]] | |seealso= [[triggerTimeout]] [[setTriggerTimeout]] [[waypointTimeoutCurrent]] | ||
}} | |||
| | {{Note | ||
|user= Killzone_Kid | |||
|timestamp= 20131126121600 | |||
|text= 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. | |||
}} | }} | ||
Latest revision as of 10:15, 1 September 2025
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:
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 Nov 26, 2013 - 12:16 (UTC)
- 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.