setVehicleInit: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
mNo edit summary
m (Text replacement - "AgentRevolution" to "AgentRev")
 
(65 intermediate revisions by 15 users not shown)
Line 1: Line 1:
[[Category:Scripting Commands|S]]
{{RV|type=command
[[Category:Scripting Commands ArmA|S]]


<new command not populated>
|game1= ofpe
|version1= 1.00


|game2= arma1
|version2= 1.00


<h2 style="color:#000066">''''' setVehicleInit '''''</h2>
|game3= arma2
|version3= 1.00


|game4= arma2oa
|version4= 1.50


'''Operand types:'''
|game5= tkoh
|version5= 1.00


'''Type of returned value:'''
|eff= global


'''Compatibility:'''
|gr1= Object Manipulation


'''Description:'''
|descr= Attach a statement to a unit. The statement is propagated over the network in MP games, it can be executed by invoking [[processInitCommands]].


{{Feature|arma3|For security reasons, the command was disabled in Arma 3. Use [[remoteExec]] for remote execution.}}


'''Example:'''
|mp= The statement will be sent to clients connecting after the command has been executed.<br>
Note that the statement will be executed automatically by [[Multiplayer Scripting#Join In Progress|JIP]] clients before [[Event Scripts#init.sqs|init.sqs]]/[[Event_Scripts#init.sqf|init.sqf]] have been executed - see [[Initialisation Order]].
 
|s1= unitName [[setVehicleInit]] statement
 
|p1= unitName: [[Object]]
 
|p2= statement: [[String]]
 
|r1= [[Nothing]]
 
|x1= <sqf>_soldier3 setVehicleInit "this allowFleeing 0";</sqf>
 
|seealso= [[Multiplayer Scripting]] [[Initialisation Order]] [[processInitCommands]] [[clearVehicleInit]]
}}
 
<dl class="command_description">
 
<dt><dt>
<dd class="notedate">03:12, 20 March 2008 (CET)</dd>
<dt class="note">[[User:Crowe|Crowe]]</dt>
<dd class="note">setVehicleInit statements will be executed in the order of the unit creation time.
This means, the statements of units who have been placed in the editor first, will be executed first.</dd>
 
<dt><dt>
<dd class="notedate">Posted on 2016-05-22 - 21:38 (UTC)</dd>
<dt class="note">[[User:AgentRev|AgentRev]]</dt>
<dd class="note">[[remoteExec]] and [[remoteExecCall]] will accept an object as JIP parameter, which make them behave in a very similar way to [[setVehicleInit]] before it was disabled.</dd>
 
</dl>

Latest revision as of 23:07, 4 May 2024

ofpe logo.png1.00Logo A1 black.png1.00Logo A2.png1.00A2 OA Logo.png1.50tkoh logo small.png1.00
GEGlobal
Hover & click on the images for description

Description

Description:
Attach a statement to a unit. The statement is propagated over the network in MP games, it can be executed by invoking processInitCommands.
Arma 3
For security reasons, the command was disabled in Arma 3. Use remoteExec for remote execution.
Multiplayer:
The statement will be sent to clients connecting after the command has been executed.
Note that the statement will be executed automatically by JIP clients before init.sqs/init.sqf have been executed - see Initialisation Order.
Groups:
Object Manipulation

Syntax

Syntax:
unitName setVehicleInit statement
Parameters:
unitName: Object
statement: String
Return Value:
Nothing

Examples

Example 1:
_soldier3 setVehicleInit "this allowFleeing 0";

Additional Information

See also:
Multiplayer Scripting Initialisation Order processInitCommands clearVehicleInit

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
03:12, 20 March 2008 (CET)
Crowe
setVehicleInit statements will be executed in the order of the unit creation time. This means, the statements of units who have been placed in the editor first, will be executed first.
Posted on 2016-05-22 - 21:38 (UTC)
AgentRev
remoteExec and remoteExecCall will accept an object as JIP parameter, which make them behave in a very similar way to setVehicleInit before it was disabled.
Retrieved from "https://community.bistudio.com/wiki?title=setVehicleInit&oldid=364116"