processInitCommands: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\[\[Category:[ _]?Scripting[ _]Commands[ _]Armed[ _]Assault(\|.*)]]" to "{{GameCategory|arma1|Scripting Commands}}") |
Lou Montana (talk | contribs) m (Text replacement - "\[\[Category:[ _]?Scripting[ _]Commands[ _]Arma[ _]2(\|.*)\]\]" to "{{GameCategory|arma2|Scripting Commands}}") |
||
| Line 37: | Line 37: | ||
[[Category:Scripting Commands OFP Elite |{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands OFP Elite |{{uc:{{PAGENAME}}}}]] | ||
{{GameCategory|arma1|Scripting Commands}} | {{GameCategory|arma1|Scripting Commands}} | ||
{{GameCategory|arma2|Scripting Commands}} | |||
[[Category:Scripting Commands Take On Helicopters|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands Take On Helicopters|{{uc:{{PAGENAME}}}}]] | ||
Revision as of 09:38, 9 January 2021
Description
- Description:
- Process statements stored using setVehicleInit. The statements will only be executed once even if processInitCommands is called multiple times.
For security reasons, the command was disabled in Arma 3.
For remote execution, see Arma 3 Remote Execution, remoteExec and remoteExecCall. - Groups:
- System
Syntax
- Syntax:
- processInitCommands
- Return Value:
- Nothing
Examples
- Example 1:
processInitCommands;
Additional Information
- See also:
- setVehicleInitclearVehicleInit
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