doMove: Difference between revisions
Jump to navigation
Jump to search
m (changed global to local variable to make clear the variable) |
(rm. incorrect note, add. new one) |
||
Line 36: | Line 36: | ||
<!-- Note Section BEGIN --> | <!-- Note Section BEGIN --> | ||
<dd class="notedate">Posted on | <dd class="notedate">Posted on February 9, 2008</dd> | ||
<dt class="note">'''[[User: | <dt class="note">'''[[User:Kronzky|Kronzky]]'''</dt> | ||
<dd class="note"> | |||
If doMove is to be used in conjunction with waypoint behavior commands (e.g. [[setSpeedMode]]), then those have to be issued ''after'' the move command to have an effect. Otherwise the move will be done with the default settings. | |||
</dd> | </dd> | ||
Revision as of 18:28, 9 February 2008
Description
- Description:
- Order the given unit(s) to move to the given position (without radio messages).
- Groups:
- Uncategorised
Syntax
Examples
- Example 1:
_soldier1 doMove (position officer)
- Example 2:
this doMove (getMarkerPos "Marker1")
Additional Information
- See also:
- commandMove
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
- Posted on February 9, 2008
- Kronzky
- If doMove is to be used in conjunction with waypoint behavior commands (e.g. setSpeedMode), then those have to be issued after the move command to have an effect. Otherwise the move will be done with the default settings.
Bottom Section
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint version 1.00
- Operation Flashpoint: New Scripting Commands
- Operation Flashpoint: Scripting Commands
- Command Group: Uncategorised
- Scripting Commands: Global Effect
- Scripting Commands OFP 1.96
- Scripting Commands OFP 1.46
- Scripting Commands ArmA
- Command Group: Unit Control