exec: Difference between revisions
Jump to navigation
Jump to search
Killzone Kid (talk | contribs) (see also) |
m (template:command argument fix) |
||
Line 12: | Line 12: | ||
Alternatively use [[execVM]] command in combination with .sqf syntax.<br> | Alternatively use [[execVM]] command in combination with .sqf syntax.<br> | ||
Learn more about scripts under [[Script|Scripts]]. <br><br> | Learn more about scripts under [[Script|Scripts]]. <br><br> | ||
To see what SQS scripts are currently in the scheduler, use [[diag_activeSQSScripts]] command.|= | To see what SQS scripts are currently in the scheduler, use [[diag_activeSQSScripts]] command.|DESCRIPTION= | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| argument '''exec''' script |= | | argument '''exec''' script |SYNTAX= | ||
|p1= argument: [[Any Value]] - the argument which should be passed to the script. To pass multiple arguments, use an array. |= | |p1= argument: [[Any Value]] - the argument which should be passed to the script. To pass multiple arguments, use an array. |PARAMETER1= | ||
|p2= script: [[String]] - the name of the script. It should be given relatively to the mission folder, campaign scripts subfolder or global scripts folder and is searched there in the same order. <br>If you refer to a script packed together with an addon, the path should look like this: "\ADDON_PBO_NAME\script.sqs" where ADDON_PBO_NAME is the name of the addon's *.pbo file without extension. |= | |p2= script: [[String]] - the name of the script. It should be given relatively to the mission folder, campaign scripts subfolder or global scripts folder and is searched there in the same order. <br>If you refer to a script packed together with an addon, the path should look like this: "\ADDON_PBO_NAME\script.sqs" where ADDON_PBO_NAME is the name of the addon's *.pbo file without extension. |PARAMETER2= | ||
| [[Nothing]] |= | | [[Nothing]] |RETURNVALUE= | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
|x1= <code>[player, _jeep] [[exec]] "getin.sqs"</code> |= | |x1= <code>[player, _jeep] [[exec]] "getin.sqs"</code> |EXAMPLE1= | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| [[execVM]], [[call]], [[spawn]], [[execFSM]] |= | | [[execVM]], [[call]], [[spawn]], [[execFSM]] |SEEALSO= | ||
}} | }} |
Revision as of 14:39, 7 April 2019
Description
- Description:
- Execute a script using (the deprecated but still available) .sqs syntax. The argument is passed to the script in the "_this" variable, and magic variable "_time" within the script contains the time in seconds that the script has been running.
Alternatively use execVM command in combination with .sqf syntax.
Learn more about scripts under Scripts.
To see what SQS scripts are currently in the scheduler, use diag_activeSQSScripts command. - Groups:
- Uncategorised
Syntax
- Syntax:
- argument exec script
- Parameters:
- argument: Any Value - the argument which should be passed to the script. To pass multiple arguments, use an array.
- script: String - the name of the script. It should be given relatively to the mission folder, campaign scripts subfolder or global scripts folder and is searched there in the same order.
If you refer to a script packed together with an addon, the path should look like this: "\ADDON_PBO_NAME\script.sqs" where ADDON_PBO_NAME is the name of the addon's *.pbo file without extension. - Return Value:
- Nothing
Examples
- Example 1:
[player, _jeep] exec "getin.sqs"
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
Bottom Section
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint version 1.00
- Operation Flashpoint: New Scripting Commands
- Operation Flashpoint: Scripting Commands
- Command Group: Uncategorised
- Scripting Commands OFP 1.99
- Scripting Commands OFP 1.96
- Scripting Commands OFP 1.46
- Scripting Commands ArmA
- Command Group: Program Flow
- Scripting Commands ArmA2
- Scripting Commands Arma 3
- Scripting Commands Take On Helicopters
- Notes: Improper Formatting