setCurrentWaypoint: Difference between revisions
Jump to navigation
Jump to search
m (VBS2 scripting category removal) |
(mass edit: removing obsolete </dt> and </dd> tags) |
||
| Line 31: | Line 31: | ||
<!-- Note Section BEGIN --> | <!-- Note Section BEGIN --> | ||
<dd class="notedate" | <dd class="notedate"> | ||
<dt class="note">'''[[User:Galzohar|Galzohar]]''' | <dt class="note">'''[[User:Galzohar|Galzohar]]''' | ||
<dd class="note"> | <dd class="note"> | ||
This command will '''crash the game''' to desktop with no error message (only "stack overflow" is shown in the RPT file) if you call it from the on act field of a waypoint that belongs to that same unit. It also seems to crash in other situations when called from code written in the editor but I couldn't figure out how to reproduce it. Executing a script that will then execute this command does not crash the game, but causes issues that aren't a whole lot worse than crashing - Mostly it seems to somehow overload the server as well as clients which makes other scripts not really function as intended. I suggest never using this command (at least right as a unit reached its waypoint) unless someone knows exactly what is wrong with it and how to avoid it.<br><br> | This command will '''crash the game''' to desktop with no error message (only "stack overflow" is shown in the RPT file) if you call it from the on act field of a waypoint that belongs to that same unit. It also seems to crash in other situations when called from code written in the editor but I couldn't figure out how to reproduce it. Executing a script that will then execute this command does not crash the game, but causes issues that aren't a whole lot worse than crashing - Mostly it seems to somehow overload the server as well as clients which makes other scripts not really function as intended. I suggest never using this command (at least right as a unit reached its waypoint) unless someone knows exactly what is wrong with it and how to avoid it.<br><br> | ||
Tested on Arma 2 vanilla 1.05. | Tested on Arma 2 vanilla 1.05. | ||
<dd class="notedate" | <dd class="notedate"> | ||
<dt class="note">'''[[User:Ceeeb|Ceeeb]]''' | <dt class="note">'''[[User:Ceeeb|Ceeeb]]''' | ||
<dd class="note"> | <dd class="note"> | ||
Note that a waypoints number as seen in the mission editor is not the same as it's waypoint number using this command. In the mission editor, waypoint 0 refers to the first placed waypoint, whereas waypoint 0 with the setCurrentWaypoint command refers to the unit's initial position waypoint. | Note that a waypoints number as seen in the mission editor is not the same as it's waypoint number using this command. In the mission editor, waypoint 0 refers to the first placed waypoint, whereas waypoint 0 with the setCurrentWaypoint command refers to the unit's initial position waypoint. | ||
<dd class="notedate" | <dd class="notedate"> | ||
<dt class="note">'''[[User:Way|Way]]''' | <dt class="note">'''[[User:Way|Way]]''' | ||
<dd class="note"> | <dd class="note"> | ||
Does not seem to work with Game Logic as of ArmA v1.08. Crashes to desktop. | Does not seem to work with Game Logic as of ArmA v1.08. Crashes to desktop. | ||
<!-- Note Section END --> | <!-- Note Section END --> | ||
</dl> | </dl> | ||
Revision as of 02:54, 18 October 2011
Description
- Description:
- Sets the currently active waypoint for a group.
- Groups:
- Uncategorised
Syntax
- Syntax:
- groupName setCurrentWaypoint waypoint
- Parameters:
- groupName: Object or Group
- waypoint: Array - format Waypoint
- Return Value:
- Nothing
Examples
- Example 1:
_grp setCurrentWaypoint [_grp, 1]
Additional Information
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
- Galzohar
-
This command will crash the game to desktop with no error message (only "stack overflow" is shown in the RPT file) if you call it from the on act field of a waypoint that belongs to that same unit. It also seems to crash in other situations when called from code written in the editor but I couldn't figure out how to reproduce it. Executing a script that will then execute this command does not crash the game, but causes issues that aren't a whole lot worse than crashing - Mostly it seems to somehow overload the server as well as clients which makes other scripts not really function as intended. I suggest never using this command (at least right as a unit reached its waypoint) unless someone knows exactly what is wrong with it and how to avoid it.
Tested on Arma 2 vanilla 1.05. - Ceeeb
- Note that a waypoints number as seen in the mission editor is not the same as it's waypoint number using this command. In the mission editor, waypoint 0 refers to the first placed waypoint, whereas waypoint 0 with the setCurrentWaypoint command refers to the unit's initial position waypoint.
- Way
- Does not seem to work with Game Logic as of ArmA v1.08. Crashes to desktop.