expectedDestination: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - " \|p([0-9]{1,2})=([^ ]+) + \| *(\[\[Arr.+) * " to " |p$1=$2 |r1=$3 ") |
Lou Montana (talk | contribs) m (Text replacement - "\| *(arg|eff|mp|serverExec|gr[0-9]) *= *(.*) * *\|([^=0-9]{12})" to "|$1=$2 |descr=$3") |
||
| Line 20: | Line 20: | ||
|gr1= Unit Control | |gr1= Unit Control | ||
| Return expected destination of unit as an array. | |descr= Return expected destination of unit as an array. | ||
|s1= '''expectedDestination''' person | |s1= '''expectedDestination''' person | ||
Revision as of 21:05, 13 June 2021
Description
- Description:
- Return expected destination of unit as an array.
- Groups:
- Unit Control
Syntax
- Syntax:
- expectedDestination person
- Parameters:
- person: Object
- Return Value:
- Array in form:
- 0: Position
- 1: planningMode
- 2: forceReplan
Examples
- Example 1:
_data = expectedDestination player;
Additional Information
- See also:
- setDestination
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 16:24, 3 March 2007 (CET)
- Donnervogel
- For AI units I have found the following values: planningMode is "LEADER PLANNED" when the unit is ordered by the group leader to go somewhere or if the unit is the group leader and it follows a waypoint. Otherwise planningMode it is "DoNotPlan". Units moving in formation have "DoNotPlan" as long as they don't receive orders by the group leader. Units also have "DoNotPlan" when they don't move. Units executing special formation tasks like engaging or return to formation have "FORMATION PLANNED" as long they have not fulfilled the task.