exec: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
No edit summary
m (Some wiki formatting)
 
(72 intermediate revisions by 20 users not shown)
Line 1: Line 1:
[[Category:Scripting Commands]]
{{RV|type=command
[[Category:Scripting Commands OFP 1.97]]
[[Category:Scripting Commands OFP 1.46]]
[[Category:Scripting Commands ArmA]]


back to [[Scripting_Reference#E|COMREF]]
|game1= ofp
|version1= 1.00


<h2 style="color:#000066"> '''''argument'' exec ''script'''''</h2>
|game2= ofpe
|version2= 1.00


|game3= arma1
|version3= 1.00


'''Operand types:'''
|game4= arma2
|version4= 1.00


'''argument:''' [[Any Value]]
|game5= arma2oa
|version5= 1.50


'''script:''' [[String]]
|game6= tkoh
|version6= 1.00


'''Type of returned value:'''
|game7= arma3
|version7= 0.50


[[Nothing]]
|gr1= Program Flow


'''Description:'''
|descr= Execute a script using (the deprecated but still available) [[SQS Syntax]]. [[SQF Syntax]] (and [[execVM]]) is the most recent scripting language.<br>
The magic variable [[Magic_Variables#time|_time]] used within the script contains the elapsed time in seconds since the script started.
{{Feature|informative|To see the active SQS scripts currently in the scheduler, use [[diag_activeSQSScripts]] command.}}


Execute script.
|s1= argument [[exec]] script


Argument is passed to script as local variable '''_this'''.
|p1= argument: [[Anything]] - the argument passed to the script through the [[Magic_Variables#this|_this]] variable. To pass multiple arguments, use an [[Array]].


Script is first searched for in mission folder, then in campaign scripts subfolder, lastly in global scripts folder.
|p2= script: [[String]] - the file path to 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.


|r1= [[Nothing]]


'''Example:'''
|x1= <sqs>[player, _jeep] exec "getin.sqs";</sqs>


[ [[player]], jeepOne] '''exec''' "getIn.sqs"
|seealso= [[execVM]] [[call]] [[spawn]] [[execFSM]]
}}

Latest revision as of 00:55, 11 July 2022

Logo A0.png1.00ofpe logo.png1.00Logo A1 black.png1.00Logo A2.png1.00A2 OA Logo.png1.50tkoh logo small.png1.00Arma 3 logo black.png0.50
Hover & click on the images for description

Description

Description:
Execute a script using (the deprecated but still available) SQS Syntax. SQF Syntax (and execVM) is the most recent scripting language.
The magic variable _time used within the script contains the elapsed time in seconds since the script started.
ⓘ
To see the active SQS scripts currently in the scheduler, use diag_activeSQSScripts command.
Groups:
Program Flow

Syntax

Syntax:
argument exec script
Parameters:
argument: Anything - the argument passed to the script through the _this variable. To pass multiple arguments, use an Array.
script: String - the file path to 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

See also:
execVM call spawn execFSM

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
Retrieved from "https://community.bistudio.com/wiki?title=exec&oldid=325305"