Script File: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\{\{( *)Informative( *)\|" to "{{$1Feature$2|$2Informative$2|") |
m (→Syntax) |
||
Line 9: | Line 9: | ||
* See [[exec]] | * See [[exec]] | ||
The already existing ( | The already existing ({{Since|ofp|1.85}}) [[SQF syntax]] was introduced for scripts in [[{{arma1}}]]. [[SQS syntax]] is still usable but is considered deprecated since. | ||
* See [[execVM]], [[spawn]] | * See [[execVM]], [[spawn]] | ||
[[Image: Script_Execution.png|frame|right||Script Execution Diagram<br>'''Executing Instance:''' script, [[Function|function]] or game engine]] | [[Image: Script_Execution.png|frame|right||Script Execution Diagram<br>'''Executing Instance:''' script, [[Function|function]] or game engine]] | ||
== Execution == | == Execution == | ||
Revision as of 09:54, 12 February 2021
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 (Template:Since) SQF syntax was introduced for scripts in Armed Assault. SQS syntax is still usable but is considered deprecated since.
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.