moveInCargo: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<dd class="notedate">Posted on ([^<>]+) " to "<dd class="notedate">Posted on $1</dd> ") |
Lou Montana (talk | contribs) m (Text replacement - "<dt class="note">([^<>]+) " to "<dt class="note">$1</dt> ") |
||
Line 41: | Line 41: | ||
<dd class="notedate">Posted on August 4, 2006 - 14:42</dd> | <dd class="notedate">Posted on August 4, 2006 - 14:42</dd> | ||
<dt class="note">[[User:Hardrock|hardrock]] | <dt class="note">[[User:Hardrock|hardrock]]</dt> | ||
<dd class="note">''Notes from before the conversion''<br> | <dd class="note">''Notes from before the conversion''<br> | ||
If you place a soldier in a vehicle with the moveInCargo command, he wont "know" he's in the vehicle, and thus he won't disembark properly when the vehicle reaches a Transport Unload waypoint. Therefore you have to use the [[assignAsCargo]] command, in order for the AI to catch on. Something like this: <code>_soldier [[moveInCargo]] helo1; _soldier [[assignAsCargo]] helo1;</code> | If you place a soldier in a vehicle with the moveInCargo command, he wont "know" he's in the vehicle, and thus he won't disembark properly when the vehicle reaches a Transport Unload waypoint. Therefore you have to use the [[assignAsCargo]] command, in order for the AI to catch on. Something like this: <code>_soldier [[moveInCargo]] helo1; _soldier [[assignAsCargo]] helo1;</code> | ||
<dd class="notedate"> | <dd class="notedate"> | ||
<dt class="note">[[User:Ceeeb|Ceeeb]] | <dt class="note">[[User:Ceeeb|Ceeeb]]</dt> | ||
<dd class="note"> | <dd class="note"> | ||
In '''OFP v1.96''', the moveIn commands will not trigger an associated getIn [[Operation_Flashpoint:_EventHandlers_List|event]]. To ensure the getIn event is fired, use the "getIn Cargo" [[Operation_Flashpoint:_Actions_List|action]] command. | In '''OFP v1.96''', the moveIn commands will not trigger an associated getIn [[Operation_Flashpoint:_EventHandlers_List|event]]. To ensure the getIn event is fired, use the "getIn Cargo" [[Operation_Flashpoint:_Actions_List|action]] command. | ||
<dd class="notedate"> | <dd class="notedate"> | ||
<dt class="note">[[User:Killzone_Kid|Killzone_Kid]] | <dt class="note">[[User:Killzone_Kid|Killzone_Kid]]</dt> | ||
<dd class="note"> | <dd class="note"> | ||
In Arma 3 when using the alternative syntax of [[moveInCargo]], it is necessary to call [[assignAsCargoIndex]] because it is not called automatically. | In Arma 3 when using the alternative syntax of [[moveInCargo]], it is necessary to call [[assignAsCargoIndex]] because it is not called automatically. |
Revision as of 01:29, 30 January 2021
Description
- Description:
- Description needed
- Groups:
- Unit Control
Syntax
- Syntax:
- Syntax needed
- Parameters:
- unitName: Object
- vehicle: Object
- Return Value:
- Return value needed
Alternative Syntax
- Syntax:
- unitName moveInCargo [vehicle, CargoIndex]
- Parameters:
- unitName: Object
- vehicle: Object
- CargoIndex: Number
- Return Value:
- Nothing
Examples
- Example 1:
_soldierOne moveInCargo _jeepOne;
- Example 2:
_soldierOne moveInCargo [_jeepOne, 1];
Additional Information
- See also:
- See also needed
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
- Posted on August 4, 2006 - 14:42
- hardrock
- Notes from before the conversion
If you place a soldier in a vehicle with the moveInCargo command, he wont "know" he's in the vehicle, and thus he won't disembark properly when the vehicle reaches a Transport Unload waypoint. Therefore you have to use the assignAsCargo command, in order for the AI to catch on. Something like this:_soldier moveInCargo helo1; _soldier assignAsCargo helo1;
- Ceeeb
- In OFP v1.96, the moveIn commands will not trigger an associated getIn event. To ensure the getIn event is fired, use the "getIn Cargo" action command.
- Killzone_Kid
-
In Arma 3 when using the alternative syntax of moveInCargo, it is necessary to call assignAsCargoIndex because it is not called automatically.
unit1 moveInCargo [heli, 3]; unit1 assignAsCargoIndex [heli, 3];
Alternatively avoid this broken syntax all together and use:unit1 assignAsCargoIndex [heli, 3]; unit1 moveInCargo heli;