processInitCommands: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Remove BIS_fnc_MP mention)
(Add example)
Line 11: Line 11:


{{Feature arma3|For security reasons, the command was disabled in Arma 3.<br>
{{Feature arma3|For security reasons, the command was disabled in Arma 3.<br>
For remote execution, see [[Arma 3 Remote Execution]], [[remoteExec]] and [[remoteExecCall]].}}
For remote execution, see [[Arma 3 Remote Execution]], [[remoteExec]] and [[remoteExecCall]].}} |DESCRIPTION=
|DESCRIPTION=
____________________________________________________________________________________________
____________________________________________________________________________________________


Line 19: Line 18:
| [[Nothing]] |RETURNVALUE=
| [[Nothing]] |RETURNVALUE=
____________________________________________________________________________________________
____________________________________________________________________________________________
|x1= <code>[[processInitCommands]];</code> |EXAMPLE1=


| [[setVehicleInit]], [[clearVehicleInit]] |SEEALSO=
| [[setVehicleInit]], [[clearVehicleInit]] |SEEALSO=

Revision as of 01:59, 5 January 2020

-wrong parameter ("Arma") defined!-1.00
Hover & click on the images for description

Description

Description:
Process statements stored using setVehicleInit. The statements will only be executed once even if processInitCommands is called multiple times.

Arma 3
For security reasons, the command was disabled in Arma 3.
For remote execution, see Arma 3 Remote Execution, remoteExec and remoteExecCall.
Groups:
Uncategorised

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

Notes

Bottom Section