setWaypointType: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "[[Category:Scripting Commands ArmA|" to "[[Category:Scripting Commands Armed Assault|")
m (Text replacement - "(\|[pr][0-9]+ *= *[^- ]*) *- *W([a-z ])" to "$1 - w$2")
(37 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Command|Comments=
{{RV|type=command
____________________________________________________________________________________________


| arma |Game name=
|game1= arma1
|version1= 1.00


|1.00|Game version=
|game2= arma2
____________________________________________________________________________________________
|version2= 1.00


| Changes the waypoint type.  
|game3= arma2oa
|version3= 1.50


Type can be:
|game4= tkoh
* <tt>"MOVE"</tt>
|version4= 1.00
* <tt>"DESTROY"</tt>
* <tt>"GETIN"</tt>
* <tt>"SAD"</tt> ''(Seek And Destroy)''
* <tt>"JOIN"</tt>
* <tt>"LEADER"</tt>
* <tt>"GETOUT"</tt>
* <tt>"CYCLE"</tt>
* <tt>"LOAD"</tt>
* <tt>"UNLOAD"</tt>
* <tt>"TR UNLOAD"</tt>
* <tt>"HOLD"</tt>
* <tt>"SENTRY"</tt>
* <tt>"GUARD"</tt> ''(for use with GUARDED BY trigger or [[createGuardedPoint]])''
* <tt>"TALK"</tt>
* <tt>"SCRIPTED"</tt>
* <tt>"SUPPORT"</tt>
* <tt>"GETIN NEAREST"</tt>
* <tt>"DISMISS"</tt>
* <tt>"LOITER"</tt> ''(new in Arma 3)''
* <tt>"HOOK"</tt> ''(new in Arma 3)'' - slingload object
* <tt>"UNHOOK"</tt> ''(new in Arma 3)'' - drop slingload
* <tt>"AND"</tt> ''(only for game logics)''
* <tt>"OR"</tt> ''(only for game logics)''


More details at [[Waypoint types]]. |Description=
|game5= arma3
____________________________________________________________________________________________
|version5= 0.50


| waypoint [[setWaypointType]] type |Syntax=
|gr1= Waypoints


|p1= waypoint: [[Array]] - format [[Waypoint]] |Parameter 1=
|descr= Sets the waypoint type of given waypoint.


|p2= type: [[String]] |Parameter 2=
More details at [[Waypoints]].


| [[Nothing]] |Return value=
|s1= waypoint [[setWaypointType]] type
____________________________________________________________________________________________
 
|x1= <code>_myWaypoint [[setWaypointType]] "HOLD";</code> |Example 1=
____________________________________________________________________________________________


| [[Mission_Editor:_Waypoints#Select_Type|waypoints description]], [[Waypoint types]], [[waypoints]], [[deleteWaypoint]], [[copyWaypoints]], [[setCurrentWaypoint]], [[setWaypointBehaviour]], [[setWaypointCombatMode]], [[setWaypointCompletionRadius]], [[setWaypointDescription]], [[setWaypointFormation]], [[setWaypointHousePosition]], [[setWaypointPosition]], [[setWaypointScript]], [[setWaypointSpeed]], [[setWaypointStatements]], [[setWaypointTimeout]], [[setWaypointVisible]], [[waypointAttachVehicle]], [[waypointAttachedVehicle]], [[setWaypointLoiterRadius]], [[waypointLoiterRadius]], [[addWaypoint]], [[setWaypointLoiterType]], [[waypointSpeed]], [[createGuardedPoint]] |See also=
|p1= waypoint: [[Array]] - format [[Waypoint]]
 
|p2= type: [[String]] - waypoint type. Can be:
{{Columns|4|
* {{hl|"MOVE"}}
* {{hl|"DESTROY"}}
* {{hl|"GETIN"}}
* {{hl|"SAD"}} ''(Seek And Destroy)''
* {{hl|"JOIN"}}
* {{hl|"LEADER"}}
* {{hl|"GETOUT"}}
* {{hl|"CYCLE"}}
* {{hl|"LOAD"}}
* {{hl|"UNLOAD"}}
* {{hl|"TR UNLOAD"}}
* {{hl|"HOLD"}}
* {{hl|"SENTRY"}}
* {{hl|"GUARD"}} <small>(for use with GUARDED BY trigger or [[createGuardedPoint]])</small>
* {{hl|"TALK"}}
* {{hl|"SCRIPTED"}}
* {{hl|"SUPPORT"}}
* {{hl|"GETIN NEAREST"}}
* {{hl|"DISMISS"}}
* {{hl|"LOITER"}} <small>({{arma3}})</small>
* {{hl|"HOOK"}} <small>({{arma3}}) - slingload object</small>
* {{hl|"UNHOOK"}} <small>({{arma3}}) - drop slingload</small>
* {{hl|"AND"}} <small>(only for game logics)</small>
* {{hl|"OR"}} <small>(only for game logics)</small>
}}
 
|r1= [[Nothing]]
 
|x1= <sqf>_myWaypoint setWaypointType "HOLD";</sqf>
 
|seealso= [[2D Editor: Waypoints#Select Type|Waypoints Types]] [[waypointType]]
}}
}}


<h3 style="display:none">Notes</h3>
<dl class="command_description">
<dl class="command_description">
<!-- Note Section BEGIN -->
 
<dd class="notedate">Posted on 07:44, 23 November 2007
<dt></dt>
<dd class="notedate">Posted on 07:44, 23 November 2007</dd>
<dt class="note">[[User:User:ArmAtec|ArmAtec]]</dt>
<dt class="note">[[User:User:ArmAtec|ArmAtec]]</dt>
<dd class="note">
<dd class="note">
Line 62: Line 70:
</dd>
</dd>


<dd class="notedate">Posted on May 6, 2017 - 16:09 (UTC)</dd>
<dt><dt>
<dd class="notedate">Posted on 2017-05-06 - 16:09 (UTC)</dd>
<dt class="note">[[User:RHfront|RHfront]]</dt>
<dt class="note">[[User:RHfront|RHfront]]</dt>
<dd class="note">
<dd class="note">
Line 68: Line 77:
</dd>
</dd>


<dd class="notedate">Posted on May 30, 2017 - 09:14 (UTC)</dd>
<dt><dt>
<dd class="notedate">Posted on 2017-05-30 - 09:14 (UTC)</dd>
<dt class="note">[[User:IT07|IT07]]</dt>
<dt class="note">[[User:IT07|IT07]]</dt>
<dd class="note">
<dd class="note">
In '''Arma 3 v1.70.141838''', if you add a '''MOVE''' waypoint very soon after a '''LOITER''' waypoint, (assuming that the index of the MOVE waypoint is HIGHER than the index of the LOITER waypoint) then the LOITER waypoint will be considered as a MOVE waypoint.<br>
In '''Arma 3 v1.70''', if you add a '''MOVE''' waypoint very soon after a '''LOITER''' waypoint, (assuming that the index of the MOVE waypoint is HIGHER than the index of the LOITER waypoint) then the LOITER waypoint will be considered as a MOVE waypoint.<br>
And, if you add another waypoint after ( for example ) more than 1 second after adding the LOITER waypoint,
And, if you add another waypoint after ( for example ) more than 1 second after adding the LOITER waypoint,
then the LOITER waypoint will NOT complete even when its condition has been met.<br>
then the LOITER waypoint will NOT complete even when its condition has been met.<br>
Line 79: Line 89:
The difference between those two methods is that the latter prevents the LOITER waypoint from executing its statement.
The difference between those two methods is that the latter prevents the LOITER waypoint from executing its statement.
</dd>
</dd>
</dl>
</dl>
<!-- Note Section END -->
<h3 style="display:none">Bottom Section</h3>
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands OFP Elite |{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Armed Assault|{{uc:{{PAGENAME}}}}]]
[[Category:Command_Group:_Waypoints|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Take On Helicopters|{{uc:{{PAGENAME}}}}]]

Revision as of 17:35, 8 November 2023

Hover & click on the images for description

Description

Description:
Sets the waypoint type of given waypoint. More details at Waypoints.
Groups:
Waypoints

Syntax

Syntax:
waypoint setWaypointType type
Parameters:
waypoint: Array - format Waypoint
type: String - waypoint type. Can be:
  • "MOVE"
  • "DESTROY"
  • "GETIN"
  • "SAD" (Seek And Destroy)
  • "JOIN"
  • "LEADER"
  • "GETOUT"
  • "CYCLE"
  • "LOAD"
  • "UNLOAD"
  • "TR UNLOAD"
  • "HOLD"
  • "SENTRY"
  • "GUARD" (for use with GUARDED BY trigger or createGuardedPoint)
  • "TALK"
  • "SCRIPTED"
  • "SUPPORT"
  • "GETIN NEAREST"
  • "DISMISS"
  • "LOITER" (Arma 3)
  • "HOOK" (Arma 3) - slingload object
  • "UNHOOK" (Arma 3) - drop slingload
  • "AND" (only for game logics)
  • "OR" (only for game logics)
Return Value:
Nothing

Examples

Example 1:
_myWaypoint setWaypointType "HOLD";

Additional Information

See also:
Waypoints Types waypointType

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 07:44, 23 November 2007
ArmAtec
Using MOVE on a game logic group will move the logic to the set location just like setPos. In the editor, only AND and OR type of waypoints are available for GAME LOGICS but you can use CYCLE type as well with setWaypointType.
Posted on 2017-05-06 - 16:09 (UTC)
RHfront
To use the LAND function in a waypoint, you must set "A3\functions_f\waypoints\fn_wpLand.sqf" as the script for that waypoint.
Posted on 2017-05-30 - 09:14 (UTC)
IT07
In Arma 3 v1.70, if you add a MOVE waypoint very soon after a LOITER waypoint, (assuming that the index of the MOVE waypoint is HIGHER than the index of the LOITER waypoint) then the LOITER waypoint will be considered as a MOVE waypoint.
And, if you add another waypoint after ( for example ) more than 1 second after adding the LOITER waypoint, then the LOITER waypoint will NOT complete even when its condition has been met.
There are two ways to quit an existing LOITER waypoint that was added more than about 1 second ago:
  • use the setCurrentWaypoint command
  • add a waypoint that has the same ID as the LOITER waypoint.
The difference between those two methods is that the latter prevents the LOITER waypoint from executing its statement.