deleteMarkerLocal: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - " |= Example " to " ") |
Lou Montana (talk | contribs) m (Text replacement - " \{\{GameCategory *\| *arma1 *\| *(New )?Scripting Commands\}\}" to "") |
||
| Line 33: | Line 33: | ||
{{GameCategory|ofpe|Scripting Commands}} | {{GameCategory|ofpe|Scripting Commands}} | ||
{{GameCategory|arma2|Scripting Commands}} | {{GameCategory|arma2|Scripting Commands}} | ||
{{GameCategory|arma3|Scripting Commands}} | {{GameCategory|arma3|Scripting Commands}} | ||
Revision as of 02:44, 13 June 2021
Description
- Description:
- Description needed
- Groups:
- Markers
Syntax
- Syntax:
- deleteMarkerLocal markerName
- Parameters:
- markerName: String
- Return Value:
- Return value needed
Examples
- Example 1:
deleteMarkerLocal "Marker1"
Additional Information
- See also:
- createMarkerLocaldeleteMarker
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 7 January, 2012
- HomerJohnston
- Unproven: I believe that if you use this command on a globally-created marker, and subsequently another machine executes a global command on the same marker (e.g. setMarkerPos), then the marker will be re-created on the machine it was previously deleted on. Can result in confusing marker behaviour.