Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
we are a group of friends, nothing profitable or nothing.
unfortunately we have no API for that scenario. But we will create an issue on our Github page and address some missing API functions.
For the time beeing, you can use the following code. This uses some internal variables and practices, but will currently suffice you.
Put this in your activation code block of your trigger.
_markersInArea = (allVariables mts_markers_namespace) select {(getMarkerPos format["%1_frame", _x]) inArea thisTrigger};
{
[_x] call mts_markers_fnc_deleteMarker;
}
forEach _markersInArea;
I just read in your wiki "If you edit a marker it will behave the same as deleting and then creating a new marker on the same position." and realized due to the prefix getting changed whenever that happens, it may also be more reliable if there was a function to search within the radius of a trigger (e.g. 10 meters) and pull the prefixes of any found markers into an array.
This array could then be run through a loop to delete each one for example and would always work even if the mission developer edited his markers.