From Bohemia Interactive Community
- Posted on 8 May, 2014 - 18:59
- ffur2007slx2_5
-
(ArmA3 ver 1.18), here's a quick reference to unit's embarkation and disembarkation.
orderGetIn
|
false
|
orderGetIn won't take effect on player controlled AI units. It needs to be used together with assignAsXXX command family. Generally speaking, orderGetIn is a Role Executor.
|
When orderGetIn is set false, it won't unassign unit's vehicle role but will force the unit to get out of the vehicle and stop him re-entering until set true again. orderGetIn false won't stop short an unit on the way to enter the vehicle in the but unassignVehicle will do. orderGetIn false will wait to fire until the unit enter a vehicle.
|
allowGetIn
|
false
|
allowGetIn won't take effect on player controlled AI units. Different from orderGetIn, this command is a Role Holder, it can control the unit's movement in the half way set by orderGetIn but not by setWaypointType, unit will be forced to get out from a vehicle by allowGetIn false and won't automatically re-enter the vehicle until allowGetIn true
|
allowGetIn won't do anything with unit's vehicle role
|
doGetOut
|
true
|
Works on player controlled ai silently, unit will automatically get back to the vehicle after disembarkation. (Unit won't get out until vehicle is stopped or landed)
|
false
|
commandGetOut
|
true
|
Same as doGetOut with radio message. (Unit won't get out until vehicle is stopped or landed)
|
false
|
leaveVehicle
|
false
|
leaveVehicle can't force a player controlled AI disembark
|
true
|
action ["GetOut",_veh]
|
true
|
Eject immediately without parachute
|
false
|
action ["Eject",_veh]
|
true
|
Eject immediately with parachute if needed
|
false
|
setWaypointType "GETIN"
|
false
|
Waypoint won't be affected by orderGetIn false or allowGetIn false until the unit is on the vehicle.
|
N/A
|