exec: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (_time, exec is normal for OFP)
m (Text replacement - " |r1=[[" to " |r1= [[")
(40 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{Command|= Comments
{{RV|type=command
____________________________________________________________________________________________


| ofp |= Game name
|game1= ofp
|version1= 1.00


|1.00|= Game version
|game2= ofpe
|version2= 1.00


|arg= global |= Arguments in MP
|game3= arma1
|version3= 1.00


|eff= local |= Effects in MP
|game4= arma2
____________________________________________________________________________________________
|version4= 1.00


| Execute a script using (the deprecated) .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.<br>
|game5= arma2oa
'''It is not recommended to use this command in any game other than [[OFP]].''' Instead, the [[execVM]] command should be used.<br>
|version5= 1.50
Learn more about scripts under [[Script|Scripts]]. |= Description
____________________________________________________________________________________________


| argument '''exec''' script |= Syntax
|game6= tkoh
|version6= 1.00


|p1= argument: [[Any Value]] - the argument which should be passed to the script. To pass multiple arguments, use an array. |= Parameter 1
|game7= arma3
|version7= 0.50


|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. |= Parameter 2
|gr1= Program Flow


| [[Nothing]] |= Return value
|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.}}
|x1= <pre>[player, _jeep] exec "getin.sqs"</pre> |= Example 1
____________________________________________________________________________________________


| [[execVM]], [[call]] |= See also
|s1= argument [[exec]] script


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


<h3 style="display:none">Notes</h3>
|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.
<dl class="command_description">
<!-- Note Section BEGIN -->
VBS2 VTK: To execute a script with no arguments that will run during the start of a mission, add this to the
initialization line of one of your objects:


[ ] exec "script_name.sqs"
|r1= [[Nothing]]


I had some trouble getting this to work at first; the key is to have a space between the brackets.
|x1= <code>[<nowiki/>[[player]], _jeep] [[exec]] "getin.sqs"</code>


 
|seealso= [[execVM]], [[call]], [[spawn]], [[execFSM]]
IMPORTANT: not reccomended for use with .sqf scripts! line breaks will cause problems if you do - use execVM for those
}}
<!-- Note Section END -->
</dl>
 
<h3 style="display:none">Bottom Section</h3>
 
[[Category:Scripting Commands|EXEC]]
[[Category:Scripting Commands OFP 1.96|EXEC]]
[[Category:Scripting Commands OFP 1.46|EXEC]]
[[Category:Scripting Commands ArmA|EXEC]]
[[Category:Command Group: Program Flow|EXEC]]
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]]

Revision as of 23:34, 7 August 2021

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:
execVMcallspawnexecFSM

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=291771"