Script File: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\[\[SQF[ _]syntax" to "[[SQF Syntax") |
Lou Montana (talk | contribs) m (Text replacement - "{{Feature | Informative | " to "{{Feature|informative|") |
||
(7 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{TOC|side}} | {{TOC|side}} | ||
A [[{{PAGENAME}}|script file]] is multiple commands and arguments defining wanted behaviour from the game, all grouped together in a textfile. This code does a specific task handled by the game engine. The common extensions for Arma scripts are '''.sqf''' and '''.sqs''', depending on the used syntax: [[SQF Syntax|SQF]] or (deprecated) [[SQS | A [[{{PAGENAME}}|script file]] is multiple commands and arguments defining wanted behaviour from the game, all grouped together in a textfile. This code does a specific task handled by the game engine. The common extensions for Arma scripts are '''.sqf''' and '''.sqs''', depending on the used syntax: [[SQF Syntax|SQF]] or (deprecated) [[SQS Syntax]]. | ||
{{Feature | | {{Feature|informative|See [[:Category:Community Tools#Code Edition|Community Tools - Code Edition]] for recommended text editors.}} | ||
== Syntax == | == Syntax == | ||
In [[:Category:Operation Flashpoint|{{ofp}}]], scripts are limited to [[SQS | In [[:Category:Operation Flashpoint|{{ofp}}]], scripts are limited to [[SQS Syntax]]. | ||
* See [[exec]] | * See [[exec]] | ||
The already existing ({{ | The already existing (since {{ofp}} v1.85) [[SQF Syntax]] was introduced for scripts in [[:Category:ArmA: Armed Assault|{{arma1}}]]. [[SQS Syntax]] is still usable but is considered deprecated since. | ||
* See [[execVM]], [[spawn]] | * See [[execVM]], [[spawn]] | ||
[[ | [[File: Script_Execution.png|frame|right||Script Execution Diagram<br>'''Executing Instance:''' script, [[Function|function]] or game engine]] | ||
== Execution == | == Execution == | ||
Line 28: | Line 28: | ||
; exec | ; exec | ||
: [[exec]] starts a thread for a script in [[SQS | : [[exec]] starts a thread for a script in [[SQS Syntax]]. | ||
; execVM | ; execVM | ||
Line 40: | Line 40: | ||
{{Feature | Informative | | {{Feature | Informative | | ||
* [[execVM]] is almost like using | * [[execVM]] is almost like using <sqf inline>[] spawn compile preprocessFile</sqf>. | ||
* [[spawn]] and [[execVM]] both add the thread to the [[Scheduler]] and provide a [[Script | * [[spawn]] and [[execVM]] both add the thread to the [[Scheduler]] and provide a [[Script Handle|script handle]] which allows you to check if the spawned script is done (using [[scriptDone]]).}} | ||
Line 49: | Line 49: | ||
* [[:Category:Syntax|Syntax]] | * [[:Category:Syntax|Syntax]] | ||
** [[SQF Syntax]] | ** [[SQF Syntax]] | ||
** [[SQS | ** [[SQS Syntax]] | ||
* [[Statement]] | * [[Statement]] | ||
[[Category:Scripting Topics]] | [[Category:Scripting Topics]] |
Latest revision as of 21:42, 16 May 2024
A script file is multiple commands and arguments defining wanted behaviour from the game, all grouped together in a textfile. This code does a specific task handled by the game engine. The common extensions for Arma scripts are .sqf and .sqs, depending on the used syntax: SQF or (deprecated) SQS Syntax.
Syntax
In Operation Flashpoint, scripts are limited to SQS Syntax.
- See exec
The already existing (since Operation Flashpoint v1.85) SQF Syntax was introduced for scripts in Armed Assault. SQS Syntax is still usable but is considered deprecated since.
![](/wikidata/images/a/a9/Script_Execution.png)
Script Execution Diagram
Executing Instance: script, function or game engine
Executing Instance: script, function or game engine
Execution
Scripts can be executed from several points in the game:
- Other scripts
- Other functions
- Init fields and (de)activation triggers in the Mission Editor
- Event Handlers in addon config files
The commands to execute scripts are:
- exec
- exec starts a thread for a script in SQS Syntax.
- execVM
- execVM preprocesses and compiles a SQF Syntax script file and starts a thread for it.
- call
- call adds provided Code to the stack and wait for it to execute, then returns the code's last returned value.