-
Notifications
You must be signed in to change notification settings - Fork 0
Map Marker Families Content Catalog
Source-verified 2026-07-07 against claude/build84-cmdcon36 (c3cc5b1, Build 91 / release 1.2.2 candidate). Paths relative to Missions/[55-2hc]warfarev2_073v48co.chernarus/ unless noted. Arma 2 OA 1.64.
A content lookup of every map-marker family the mission produces: marker-name pattern, marker TYPE (icon class), COLOR, SIZE, TEXT source, LOCALITY, and the CREATOR path:line. This page is the what (one compact table per family). For the how — the registrar/registry/consolidated-loop architecture, per-tick gating, and the FSM updaters — see Marker Loop Engine and Registries and Client Marker FSM Updater Map. For the marker function APIs (WF_createMarker, WFBE_CL_FNC_Delete_Marker, MarkerUpdate), see Marker Subsystem Function Reference.
| Verb | Replicates? | Used by |
|---|---|---|
createMarkerLocal |
No — marker exists on the calling client only | Almost every family below (town, camp, base, unit, team, patrol, AICOM, sniper, CBR-contact, ICBM-warning, UAV-spotted, respawn, airport, FT, defense rings, sell-preview) |
createMarker |
Yes — existence + position replicate to all clients | Current master AICOM-wildcard convoy/HVT, Bank, UAV self-marker, and WF_createMarker callers (fire mission, commander ICBM, radzone). PR #43 B68 removes the W17 convoy global marker. |
setMarker*Local |
No — style/text/pos local only | local recolor, live text, capture recolor |
setMarker* (bare) |
Yes | the GLOBAL families' initial style; sniper text (setMarkerText, Skill_Sniper.sqf:16) on an otherwise-local marker |
"GLOBAL" below means the marker's existence is created by createMarker and so is map-visible cross-client. Some GLOBAL markers (the WF_createMarker ones) still apply their type/text/color only locally, gated on playerSide == _side_who_see_marker (Common/Functions/Common_CreateMarker.sqf:62-78), so they exist everywhere but only paint for the addressed side.
Each family draws its numeric suffix from a global counter. Several families share one counter, so suffixes are not contiguous within a family.
| Counter | Init | Families that increment it |
|---|---|---|
unitMarker |
Common/Init/Init_Common.sqf:177 (unitMarker = 0) |
Unit/Vehicle (Common/Init/Init_Unit.sqf:157), AA-Radar (Common/Common_AARadarMarkerUpdate.sqf:11), Paratrooper (Client/PVFunctions/HandleParatrooperMarkerCreation.sqf:29), UAV-spotted (Client/Functions/Client_FNC_Special.sqf:100), respawn-menu (Client/GUI/GUI_RespawnMenu.sqf) — shared across 5 families
|
buildingMarker |
Client/Init/Init_Client.sqf:420 (= 0) |
Base structure (Client/Init/Init_BaseStructure.sqf:22), commander defense rings (Client/GUI/GUI_Menu_Tactical.sqf:717-718) |
CCMarker |
Client/Init/Init_Client.sqf:325 (= 0) |
UAV-terminal range ring (Client/Init/Init_BaseStructure.sqf:24) |
CBRCircleMarker |
Client/Init/Init_Client.sqf:326 (= 0) |
CBR range ring (Client/Init/Init_BaseStructure.sqf:59) |
markerID |
Client/Module/Skill/Skill_Sniper.sqf:10 (if (isNil "markerID") then {markerID = 1}) |
Sniper spot (Skill_Sniper.sqf:20) |
The UAV self-marker walks its own free _id (loops while markertype is non-empty, Client/Module/UAV/uav_interface.sqf:158-159) rather than a global counter. Convoy/HVT, radzone, fire-mission, ICBM and CBR-contact suffix on a time token (round time / diag_tickTime / str time).
| Field | Value |
|---|---|
| Name |
WFBE_<townLogic>_CityMarker (Client/Init/Init_Markers.sqf:21) |
| Type |
"Depot" (Init_Markers.sqf:23) |
| Color | own-side WFBE_C_<side>_COLOR if _townSide == WFBE_Client_SideID, else WFBE_C_UNKNOWN_COLOR (Init_Markers.sqf:15-17,24) |
| Size | default (none set at creation) |
| Text | live SV/supply label set by FSM Client/FSM/updatetownmarkers.sqf — " SV: x/y [+SUPPLY]" :40, " SV: x/y [+]" :42, " SV: x/y [mm:ss]" :53, plain :60, cleared "" :63
|
| Creator |
Init_Markers.sqf:22 (createMarkerLocal) |
| Locality |
local — side-recolored per client; recolored on capture Client/PVFunctions/TownCaptured.sqf:24
|
| Field | Value |
|---|---|
| Name |
WFBE_<town>_CityMarker_Camp<i> — assigned server-side Common/Init/Init_Town.sqf:156, read by clients via _x getVariable "wfbe_camp_marker" (Init_Markers.sqf:44) |
| Type |
"Strongpoint" (Init_Markers.sqf:46) |
| Color | own-side / WFBE_C_UNKNOWN_COLOR (Init_Markers.sqf:38-40,47) |
| Size |
[0.5,0.5] (Init_Markers.sqf:48) |
| Creator |
Init_Markers.sqf:45 (createMarkerLocal) |
| Locality |
local; recolored on capture Client/PVFunctions/CampCaptured.sqf:23,48
|
File Client/Init/Init_BaseStructure.sqf, guarded if (local player) (:7) + own-side gate if (_side != WFBE_Client_SideJoined) exitWith {} (:17).
| Sub-marker | Name | Type | Color | Size | Text | Creator |
|---|---|---|---|---|---|---|
| Structure icon |
BaseMarker<buildingMarker> (:21) |
"mil_box", or "Headquarters" if _hq (:34,36,37) |
"colorBlack" (:35,43) |
[0.5,0.5] for non-HQ (:40) |
letter from GetStructureMarkerLabel (:40,42) |
:25 (createMarkerLocal) |
| ServicePoint variant | (same marker, when label == "S") |
"mil_objective" (:47) |
side color WFBE_C_<side>_COLOR (:49) |
— |
"SP" (:48) |
:46-50 |
| UAV-terminal range ring |
CCrange<CCMarker> (:23) |
Ellipse/Border (:30,29) |
"ColorBlack" (:31) |
[_radius,_radius] where _radius = WFBE_C_STRUCTURES_COMMANDCENTER_RANGE (:15,32) |
— |
:28-32; deleted with structure :118
|
| CBR range ring |
CBRrange<CBRCircleMarker> (:58) |
Ellipse/Border (:76,77) |
"ColorRed" (:78) |
[_cbrRadius,_cbrRadius] (:79); live-resized in watch :104; deleted :111
|
— | :75-79 |
Structure-icon label letters (Client/Functions/Client_GetStructureMarkerLabel.sqf:14-23): B Barracks, L Light, C CommandCenter, H Heavy, A Aircraft, S ServicePoint, R Bank/Federal Reserve, AAR AARadar, AR ArtilleryRadar, RES Reserve; default "". The structure marker is deleted on death (:117). The CBR ring radius is the fixed airfield 2000 m when the server broadcasts wfbe_cbr_radius (Server/FSM/server_town.sqf:537; read Init_BaseStructure.sqf:63, treated as the "fixed" non-resizing case :91), otherwise the upgrade tier [750,1500,2000] (:64,72).
Locality: all base-structure sub-markers are local (createMarkerLocal).
| Field | Value |
|---|---|
| Name |
HQUndeployed (literal, single per side) — Common/Init/Init_Unit.sqf:186
|
| Type |
"Headquarters" (Init_Unit.sqf:186) |
| Color |
"ColorPink" (Init_Unit.sqf:186) |
| Size |
[1,1] (Init_Unit.sqf:186) |
| Refresh |
0.2 s, no death-marker (trackDeath = false, Init_Unit.sqf:186) |
| Creator | params built Init_Unit.sqf:186 → _params Spawn MarkerUpdate (:201) → createMarkerLocal in registrar Common/Common_MarkerUpdate.sqf:39
|
| Locality |
local (registry/loop, side-gated Common_MarkerUpdate.sqf:25) |
There is no HQDeployed marker — HQUndeployed is the only HQ-vehicle marker name in the whole mission (single source ref, Init_Unit.sqf:186); deploy/undeploy does not rename it.
File Common/Init/Init_Unit.sqf:148-201; side gate if (!_perfSideMatch) exitWith {} (:146).
| Field | Value |
|---|---|
| Name |
unitMarker<unitMarker> (Init_Unit.sqf:157-158) |
| Type (man) |
"mil_dot" (:161); immobile-vehicle override to "mil_objective" applied in the loop (Common/Common_MarkerLoop.sqf:329), not at creation |
| Type (vehicle) | role-keyed: "SupplyVehicle" (:173), "RepairVehicle" (:174), "Attack" (ammo truck :179), "SalvageVehicle" (:184); else default "Vehicle" (:151) |
| Color | own group "ColorOrange" (:164); Bicycle "ColorWhite" (:169); Plane/Heli "ColorPink" (:170,171); local+MP "ColorOrange" (:172); ammo "ColorRed" (:179); lifter "ColorWhite" (:181); ambulance "ColorYellow" (:182); salvage "ColorKhaki" (:184); repair "ColorBrown" (:174); arty "ColorPink" (:176); else side color (:152) |
| Size | man [0.5,0.5] (:162); supply [1,1] (:173); ammo [0.4,0.4] (:179); else [5,5] (:153) |
| Text | own-group AI digit via GetAIDigit (:165), else ""
|
| Death marker | type "DestroyedVehicle", color = last color, applied in the loop for WFBE_C_PLAYERS_MARKER_DEAD_DELAY (Common_MarkerLoop.sqf:176-182); params carry it at index 8/9 (Init_Unit.sqf:167,185) |
| Creator |
_params Spawn MarkerUpdate (:201) → createMarkerLocal registrar Common_MarkerUpdate.sqf:39
|
| Locality |
local (side-gated Common_MarkerUpdate.sqf:25) |
Combat-blink recolor (red↔original) is attached only when WFBE_C_MAP_ICON_BLINKING_ENABLED == 1 (Init_Unit.sqf:190); the recolor helper Client/Functions/Client_BlinkMapIcon.sqf:18,23,31,37 only re-colors an existing unit marker — it creates none.
Effectively a Unit-family marker; distinguished only by its spawn path and audit tag. File Client/PVFunctions/HandleParatrooperMarkerCreation.sqf; side gate if (sideID != _sideID) exitWith {} (:18).
| Field | Value |
|---|---|
| Name |
unitMarker<unitMarker> (:29-30) |
| Type |
"mil_dot" (:32) |
| Color | own group "ColorOrange" (:35), else side color (:24) |
| Size |
[0.5,0.5] (:33) |
| Creator | params :38 → _params Spawn MarkerUpdate (:40) → Common_MarkerUpdate.sqf:39
|
| Locality |
local (audit-tagged paratrooper_marker_spawn :45) |
Registrar Common/Common_AARadarMarkerUpdate.sqf, called from Common/Init/Init_Unit.sqf:118 only when WFBE_C_STRUCTURES_ANTIAIRRADAR > 0 and the tracked aircraft is on the opposite side (:115-116).
| Field | Value |
|---|---|
| Name |
unitMarker<unitMarker> (:11-12) — shares the unit namespace |
| Type |
"mil_arrow2" (filled arrow) (:15) |
| Color |
"ColorRed" (:16) |
| Size |
[0.5,0.5] (:17), alpha 0 until visible (:18) |
| Text (live) |
"<speed> <altitude> <name>" written in the loop Common/Common_MarkerLoop.sqf:469-471 (name only at AAR level > 1, :457-459); alpha→1 when visible :464
|
| Creator |
:14 (createMarkerLocal); registry push :45-46; loop started :50-51
|
| Locality |
local (opposite-side gated :33-39) |
File Client/FSM/updateteamsmarkers.sqf; one marker per clientTeams entry, cached by index.
| Field | Value |
|---|---|
| Name |
<sideText>AdvancedSquad<n>Marker (:22) |
| Type |
"Arrow" (:25) |
| Color |
"ColorBlack" default (:30); player's own team "ColorOrange" (:33); live recolor :243
|
| Size |
[0.7,0.7] (:27), alpha 0 initial (:28) |
| Text | AI digit / role label _label set :227, cleared "" :259
|
| Creator |
:24 (createMarkerLocal) |
| Locality |
local; arrow direction follows velocity (setMarkerDirLocal, FSM follow pass) |
File Client/FSM/updatepatrolmarkers.sqf; tracks WFBE_ACTIVE_PATROLS (:19).
| Field | Value |
|---|---|
| Name |
wfbe_patrolmarker_<i> (:32) |
| Type |
"mil_arrow2" (:37) |
| Color |
"ColorYellow" (:38) |
| Size |
[0.6,0.6] (:39) |
| Text |
"Patrol <i>" (:40) |
| Creator |
:35 (createMarkerLocal); deleted on death :73
|
| Locality |
local, FRIENDLY-ONLY (_sid == WFBE_Client_SideID, :25) |
File Client/FSM/updateaicommarkers.sqf; tracks WFBE_ACTIVE_AICOM_TEAMS (:23).
| Field | Value |
|---|---|
| Name |
wfbe_aicommarker_<i> (:56) |
| Type |
"mil_arrow2" (:59) |
| Color | side color by entry sideID (:49-54,60) |
| Size |
[0.7,0.7] (:61) |
| Text |
"HQ Team" (:62) |
| Creator |
:58 (createMarkerLocal); deleted :109
|
| Locality |
local, FRIENDLY-ONLY (_sid == _mySid where _mySid = WFBE_Client_SideID, :34,42 — intel-leak guard) |
File Server/Functions/AI_Commander_Wildcard.sqf. On current origin/master@0139a346, these are the GLOBAL, fully-cross-side-visible wildcard markers created with bare createMarker/setMarker* server-side. PR #43 / B68 branch head b8a1505f removes the W17 Supply Convoy global marker route at Chernarus AI_Commander_Wildcard.sqf:994 because own-side convoy visibility already comes through friendly unit markers; W18 remains intentionally global branch evidence until separately changed.
| Sub-family | Name | Type | Color | Text | Creator / delete |
|---|---|---|---|---|---|
| Supply Convoy (W17) |
aicom_convoy_<sideText>_<round time> (:980) |
"mil_destroy" (:982) |
"ColorBlue" west / "ColorRed" (:983) |
"Supply Convoy (<side>)" (:984) |
create :981; deleteMarker :1006
|
| Bounty HVT (W18) |
hvt_<sideText>_<round time> (:1036) |
"mil_dot" (:1038) |
"ColorBlue" west / "ColorRed" (:1039) |
"HVT (<enemySide>)" (:1040) |
create :1037; deleteMarker :1045
|
Locality: GLOBAL (visible to all sides) on current master. Branch note: origin/claude/b57-soak-proposals@b8a1505f removes W17 creation, so smoke PR #43 for friendly-only convoy visibility and enemy non-visibility before merging or release wording.
Not part of the base-structure marker family (Client/Init/Init_BaseStructure.sqf) or the consolidated marker loop — a GUER field FOB factory (Barracks/Light/Heavy, B75 guer-tech, built via Client/Action/Action_BuildFOB.sqf → Server/PVFunctions/RequestFOBStructure.sqf) additionally gets a standalone event-style marker riding the same WildcardMarker PVF idiom as the AICOM wildcard family above — created/deleted by direct server calls, no registrar, no per-tick service.
| Field | Value |
|---|---|
| Name |
guer_fob_<floor(x)>_<floor(y)> — deterministic from the FOB build position (Server/PVFunctions/RequestFOBStructure.sqf:79) |
| Type |
"mil_objective" (RequestFOBStructure.sqf:79) |
| Color |
"ColorGreen" (RequestFOBStructure.sqf:79) |
| Size |
[1,1], fixed by the WildcardMarker idiom itself, not caller-configurable (Client/PVFunctions/WildcardMarker.sqf:66) |
| Text |
"FOB <Barracks|Light|Heavy> - forward base active - spawn and resupply here" — label Format ["FOB %1", _facType] + detail combined by WildcardMarker.sqf:58-59
|
| Creator |
[resistance, "WildcardMarker", ["create", ...]] Call WFBE_CO_FNC_SendToClients (RequestFOBStructure.sqf:79), fired after the authoritative token + placement checks pass, just before the delivery truck is consumed (:44-81) |
| Deleted |
[resistance, "WildcardMarker", ["delete", <same name>]] Call WFBE_CO_FNC_SendToClients (Server/Functions/Server_BuildingKilled.sqf:79) — only on the player-kill, non-teamkill branch that pays the "GUER FOB barracks cleared" bounty (:72-80). A teamkill or a kill not attributed to a live player (AI, environmental/null instigator) skips this branch; the structure is still removed (deleteVehicle _structure runs unconditionally, :176) but the marker is left on the map. |
| Locality |
local, resistance-only — the PVF is dispatched with a SIDE-typed destination (resistance); Client/Functions/Client_HandlePVF.sqf:40 only clears its exit flag when sideJoined == _destination, so WEST/EAST clients never even reach WildcardMarker.sqf. The marker itself is createMarkerLocal (WildcardMarker.sqf:63). |
| Side chat echo | the same create call also posts "Wildcard: FOB <type> - forward base active - spawn and resupply here." to command chat, resistance-only (WildcardMarker.sqf:72-74) |
No feature flag gates the marker specifically — it fires unconditionally whenever the existing WFBE_C_GUER_PLAYERSIDE gate (default 1, B66) allows a FOB to be built at all (RequestFOBStructure.sqf:31).
| Sub-family | Name | Type | Color | Size | Text | Locality | Creator |
|---|---|---|---|---|---|---|---|
| Bank (Federal Reserve / Bank Rossii) |
wfbe_bank_<west|east> (Server/Construction/Construction_MediumSite.sqf:134) |
"mil_warning" (:138) |
"ColorBlue" west / "ColorRed" east (:135) |
default |
"FEDERAL RESERVE" / "BANK ROSSII" (:136) |
GLOBAL (createMarker :137) |
:137-140 |
| Sell-mode preview |
wfbe_econ_sell_<idx> (Client/GUI/GUI_Menu_Economy.sqf:201) |
"Empty" (:203) |
"ColorYellow" (:204) |
[0.7,0.7] (:205) |
"$<refund>" (:206) |
local |
:202 (createMarkerLocal) |
| Sub-family | Name | Shape / Type | Color | Size | Locality | Creator |
|---|---|---|---|---|---|---|
| Side respawn zones |
respawn_east / respawn_west / respawn_guerrila (Common/Init/Init_Common.sqf:189,195,201) |
RECTANGLE / BORDER (:191-192) |
"ColorGreen" (:190) |
[15,15], alpha 0 (:193-194) |
local |
:189,195,201 (createMarkerLocal) |
| Field | Value |
|---|---|
| Name |
wfbe_airport_<i> (Common/Init/Init_Airports.sqf:25) |
| Type |
"mil_triangle" (:26) |
| Color |
"ColorYellow" (:27) |
| Creator |
:25 (createMarkerLocal), guarded if (local player) (:24) |
| Locality | local |
| Sub-family | Name | Type | Color | Size | Text | Locality | Creator / delete |
|---|---|---|---|---|---|---|---|
| Player fire mission |
ARTY_<diag_tickTime> + ellipse Elipse_ARTY_... (Client/Functions/Client_RequestFireMission.sqf:22,29) |
"Destroy" (:24) |
"ColorRed" (:26) |
radius _arty_radius (:28) |
"ARTY [<player>]" (:25) |
GLOBAL via WF_createMarker (:31), side-gated display |
auto-deleted 80 s :32-33
|
| Tactical-menu arty preview |
artilleryMarker + artilleryAreaMarker (Client/GUI/GUI_Menu_Tactical.sqf:26,32) |
"mil_destroy" (:28) + Ellipse (:34) |
"ColorRed" (:29,35) |
[1,1] / [artyRange,artyRange] (:30,36) |
— | local |
:27,33 (createMarkerLocal) |
| Counter-battery contact |
WFBE_CBR_<diag_tickTime> (Client/PVFunctions/CounterBatteryContact.sqf:18) |
"mil_destroy" (:22) |
"ColorRed" (:23) |
[0.8,0.8] (:25) |
localized contact + time (:19,24) |
local (side-addressed PVF) |
:21 (createMarkerLocal); auto-deleted 75 s :28
|
| Sub-family | Name | Type | Color | Text | Locality | Creator |
|---|---|---|---|---|---|---|
| ICBM impact warning |
icbmstrike (Client/Module/Nuke/OnEventHandler_ICBM_Launch.sqf:26) |
"mil_warning" (:27) |
"ColorRed" (:29) |
"ICBM" (:28) |
local, side-gated (playerSide == _ICBM_side, :22) |
:26 (createMarkerLocal) |
| Commander ICBM (tactical) |
ICBM_<time> + Elipse_<name> (Client/GUI/GUI_Menu_Tactical.sqf:474,481) |
"mil_warning" (:476) |
"ColorRed" (:478) |
"ICBM by commander" (:477) |
GLOBAL via WF_createMarker (:483) |
:483 |
| Radiation zone |
RADZONE_<west|east>_<round time>_<rand> + ellipse (Client/Module/Nuke/radzone.sqf:57,58) |
"mil_warning" (:51) |
"ColorGreen" (:53) |
"RADIOACTIVE ZONE" (:52) |
GLOBAL per-side via WF_createMarker (west :64-73, east :76-85) |
:64,76 |
| Sub-family | Name | Type | Color | Size | Text | Locality | Creator |
|---|---|---|---|---|---|---|---|
| UAV self-marker |
_user_defined_UAV_MARKER_<id> (Client/Module/UAV/uav_interface.sqf:162; OA variant uav_interface_oa.sqf:68) |
"mil_destroy" (:163 / :69) |
"colorred" (:164 / :70) |
[0.5,0.5] (:165 / :71) |
"UAV <id>: <time>" (:167 / :73) |
GLOBAL (createmarker) |
:162 / :68
|
| UAV spotted (FNC_Special) |
WFBE_UAV_SPOTTED_<unitMarker> (Client/Functions/Client_FNC_Special.sqf:99) |
Ellipse (:102) |
"ColorOrange" (:103) |
[_size,_size] (:104) |
— | local |
:101 (createMarkerLocal); auto-deleted :108
|
File Client/Module/Skill/Skill_Sniper.sqf.
| Field | Value |
|---|---|
| Name |
Spot<markerID> (:13) |
| Type |
"mil_destroy" (:17) |
| Color |
"ColorRed" (:18) |
| Size |
[0.5,0.5] (:19) |
| Text |
"SPOTTED: <time>" (:16) |
| Creator |
:14 (createMarkerLocal; text applied via global setMarkerText :16); auto-deleted 180 s :27-28
|
| Locality | local |
File Client/GUI/GUI_Menu_Tactical.sqf:715-733; suffix walks the buildingMarker counter (:717-718).
| Sub-marker | Name | Shape | Color | Size / brush | Creator |
|---|---|---|---|---|---|
| Large range |
WFBE_A_Large<track> (:720) |
ELLIPSE (:723) |
"ColorBlue" (:722) |
[_maxRange,_maxRange], alpha 0.4, brush by mode (:725-729) |
:721 (createMarkerLocal) |
| Small range |
WFBE_A_Small<track> (:730) |
ELLIPSE (:733) |
"ColorBlack" (:732) |
— |
:731 (createMarkerLocal) |
Locality: local.
File Client/GUI/GUI_Menu_Tactical.sqf.
| Field | Value |
|---|---|
| Name |
FTMarker<i> (:201); fee marker FTMarker<i><i> when _ft == 2 (:209) |
| Type |
"mil_circle" (:204,212) |
| Color |
"ColorYellow" (:205,213) |
| Size |
[1,1] (:206); fee marker [0,0] (:214) |
| Text (fee) |
"$<fee>" (:215) |
| Creator |
:203,211 (createMarkerLocal) |
| Locality | local |
These are used by several families above; APIs are documented in Marker Subsystem Function Reference.
-
WF_createMarker=Common/Functions/Common_CreateMarker.sqf— creates the marker GLOBAL (createMarker:53) plus an optional ellipse (:59), but applies type/text/color locally only ifplayerSide == _side_who_see_marker(:62-78), then setsMARKER_CREATIONandpublicVariables it (:82-83). Callers: fire mission, commander ICBM, radzone. -
Client/Functions/Client_onEventHandler_MARKER_CREATION.sqf— theMARKER_CREATIONPV consumer. ThecreateMarkerLocal/createMarkerlines are commented out (:35,43); the handler only re-styles already-created (global) markers (:36-46). -
Client/Functions/Client_BlinkMapIcon.sqf— combat-blink recolor of an existing unit marker (unitMarkerBlink/OriginalMarkerColor,:18,23,31,37); creates no markers. -
Client/PVFunctions/WildcardMarker.sqf— SIDE-scoped local marker create/delete (createMarkerLocal/deleteMarkerLocal), dispatched via aSIDE-typed PVF destination so only that side's clients ever run it (Client/Functions/Client_HandlePVF.sqf:40). Registered as a client PVF (Common/Init/Init_PublicVariables.sqf:47). Callers:Server/Functions/AI_Commander_Wildcard.sqf:1634(AICOM wildcard events),Server/Functions/AI_Commander_Wildcard_GUER.sqf:183,189(GUER Car Bomb wildcard), andServer/PVFunctions/RequestFOBStructure.sqf:79/Server/Functions/Server_BuildingKilled.sqf:79(GUER FOB active marker, above).
-
No
HQDeployedmarker — onlyHQUndeployed(Init_Unit.sqf:186); deploy state never renames the HQ marker. -
Client_onEventHandler_MARKER_CREATION.sqf:35,43— marker-creation lines commented out; the PV path only re-styles. -
Server/Functions/Server_OnHQKilled.sqf:99— itsWF_createMarkercall is commented out (dead). -
mil_dot→mil_objectiveimmobile-vehicle swap happens in the loop (Common_MarkerLoop.sqf:329), not at creation. - The
unitMarker<n>namespace is shared across Unit/Vehicle, AA-Radar, Paratrooper, UAV-spotted and respawn-menu markers, so suffixes are not contiguous within any one of those families. - No marker family is created by an "RHUD" path — RHUD is a resource/control HUD, not a map-marker producer.
- GUER FOB active marker (
guer_fob_<x>_<y>) is deleted only on the player-kill, non-teamkill path inServer/Functions/Server_BuildingKilled.sqf:72-80; a teamkill or a kill not attributed to a live player leaves the marker on the map after the FOB structure itself is gone.
- Marker Loop Engine and Registries — the registrar → registry → consolidated-loop architecture and per-tick gating
- Client Marker FSM Updater Map — the town/team/patrol/AICOM FSM updaters that drive live text, color and direction
-
Marker Subsystem Function Reference —
WF_createMarker,MarkerUpdate,WFBE_CL_FNC_Delete_Markerand related APIs - Towns Camps And Capture Atlas — town/camp logic, sideID coloring and the capture recolor path
- Counter-Battery Radar System — CBR range rings, the 750/1500/2000 tier ladder and counter-battery contact markers
Home | Agent Guide | Current live state | Release 1.2.2 (B91) | Quickstart | Progress | Lifecycle wait-chain | Join/disconnect | Parameters/build | Assets/config | SQF atlas | PV index | Modules | Support/specials | Commander/HQ | Commander vote/reassign | Construction/CoIn | Construction cleanup | WDDM compositions | Factory/purchase | Upgrades/research | Towns/camps/capture | Victory/endgame | Markers/cleanup | Server runtime | AI runtime/HC | AI commander audit | HC delegation | Town AI safety | Commander reassignment | Resistance supply | Player UI workflow | UI atlas | Respawn/death | Gear template filter | Vehicle cargo loop | Service guards | UI IDD repair | UI design inspiration | WASP overlay | Feature status | Source propagation | release readiness | Tooling readiness | Integration trust | AntiStack DB | Owner decisions | Shelved registry | Abandoned feature revival | Hardening roadmap | PVF dispatch | Server authority | ICBM authority | Attack-wave authority | Telemetry families | AICOM V2 cutover | Consumer port map | Testing workflow | Server ops | Web tools | Ecosystem repos | Arma 2 OA refs | A2 traps | OA compatibility audit | Coverage ledger | Navigation inventory | Pruning ledger | Knowledge roadmap | Agent context | Collab protocol | Worklog | Audit archive 2026-07 | Briefing reference | Utes invasion concept
- Shelved AICOM concepts - revivable someday ideas (owner-shelved 2026-07-03)
Docs rule: source-backed claims only; Arma 2 OA scripting docs only; gameplay edits start in Missions/[55-2hc]warfarev2_073v48co.chernarus.
- Getting started
- Status and coordination
- Agent context
- Agent collaboration protocol
- Agent worklog
- Agent worklog archive
- Progress dashboard
- PR cleanup and integration lab
- Shelved PR #169: gear price double-count
- Shelved PR #194: Chernarus no-trees
- Coordination board
- Codebase coverage ledger
- Bottleneck removal queue
- Current source status
- Wiki mirror reconciliation
- Navigation inventory
- Registers
- Agent orchestration
- Architecture
- Architecture overview
- Mission entrypoints and lifecycle
- Lifecycle wait chain
- Player join/disconnect and AntiStack lifecycle
- Mission parameters/localization/build inputs
- Stringtable localization key-family catalog
- Source inventory
- Content structure and maps
- Assets/config/localization/parameters
- Mission start parameters index
- Code and networking
- Gameplay systems
- Core systems index
- Gameplay systems atlas
- Commander/HQ lifecycle atlas
- Economy, towns and supply
- Economy system reference
- Balance asymmetries
- Anti-stack skill-balance mechanic
- Empty-side supply income stagnation
- Towns, camps and capture atlas
- Victory and endgame atlas
- Victory conditions reference
- Territorial victory reference
- Marker cleanup and restoration
- Marker loop engine and registries
- Map marker families content catalog
- Marker subsystem function reference
- Client marker FSM updater map
- Support specials and tactical modules
- SCUD TEL tactical munitions
- Naval HVT objectives (carriers/SCUD)
- SCUD saturation strike mechanic
- Takistan airfield FPV drone design
- Construction and CoIn systems
- Structure damage reduction & friendly-fire
- Construction logic list cleanup
- Flak tower & WDDM anchor compositions
- Resistance supply scaffold
- GUER Insurgents faction overview
- GUER Insurgents branch audit
- GUER insurgent player economy
- GUER Commissar Panel
- GUER air-defense loop (Ka-137/Mi-24)
- Upgrades and research atlas
- Supply mission architecture
- Supply mission authority cleanup
- Current supply helicopters PR1
- Respawn and death-loop lifecycle
- Vehicle theft economy pitch
- GUER tunnel network pitch
- Content, reference and catalogs
- Faction unit/vehicle roster catalog
- Auxiliary/SF/civilian unit catalog
- Gear store loadout route catalog
- Upgrade research (cross-faction)
- Gear store price and upgrade catalog
- Gear store catalog (complete, per faction)
- Defense structures catalog
- Artillery reference per faction
- AI squad team templates catalog
- Town AI lifecycle reference
- Town AI group composition catalog
- Class-skill system reference
- Player skill abilities reference
- Default gear template content catalog
- Chernarus map content reference
- Takistan map content reference
- Takistan features
- Takistan parity reference
- Takistan oilfields objective reference
- IRS IR-smoke countermeasure
- Arty module special munitions
- Zeta cargo sling-load reference
- Spawn primitive function reference
- Kill and score pipeline
- Waypoint helper function reference
- Position and proximity function reference
- Side/team state function reference
- Player AI watchdog and recovery
- AICOM stuck-recovery v2
- LoadoutManager data-model contributor guide
- Discord status bot setup and reference
- GLOBALGAMESTATS extension reference
- New player quickstart (player guide)
- Optional client mods (player guide)
- Earning funds and score (player guide)
- Vehicle service and logistics (player guide)
- Commander's handbook (player guide)
- Tactical support menu
- Paradrop player experience
- Supply missions (player guide)
- In-game briefing & Diary field manual
- Playable maps catalog
- Faction root variables reference
- Faction base structures catalog
- Counter-battery radar system
- Bank, Reserve and Artillery Radar structures
- Map ruleset model and object config
- Countermeasures module reference
- Vehicle countermeasure (flares/spoofing)
- UAV terminal and spotter system
- Artillery firing function reference
- Service Point pricing model
- Medic redeployment truck (forward spawn)
- Side-patrol runtime and convoy mechanics
- Day/night cycle and weather system
- Config lookup helper reference
- CIPHER sort utilities reference
- Modded maps status and content
- BattlEye filter setup and OA taxonomy
- Player squad/group join protocol
- AutoFlip vehicle recovery
- Engine stealth fuel toggle
- Valhalla vehicle climbing-assist
- Missile and ordnance Fired-EH reference
- Vehicle equip and rearm reference
- Array and collection utilities
- Server composition spawner reference
- Upgrade queue server loop
- Map boundaries and off-map enforcement
- Namespace/profile/diagnostic utilities
- Group bool getVariable A2-OA trap
- Vehicle weapon balance init
- View distance auto-throttle
- Camp & respawn-camp getters
- Performance audit writer
- Site clearance (bulldozer)
- Factory queue cancel & refund
- AI commander tunable constants
- Experimental feature-flag constants
- Flag system quick reference
- Mission tunable constants catalog
- Gear parsing & cargo capacity
- Structure dressing function
- Paradrop delivery functions
- ICBM nuke client VFX & radiation
- Server HandleSpecial router
- LocalizeMessage chat router
- Gear buy-menu render & price functions
- Server broadcast & telemetry loops
- Per-unit client init pipeline
- Vehicle marking & texture pipeline
- Defense category & budget
- Legacy AI order primitives
- Commander-team driver
- AICOM command verbs
- AICOM behavior fix taxonomy
- AI commander wildcard deck reference
- AICOM aircraft and airfield system
- Static-defense manning
- End-of-game stats screen
- AI commander execution loop
- Deployable bipod / weapon resting
- Town-economy getters
- Server-init deadspawn & airfield probe
- GUER VBIED detonate action
- Resource income-tick engine
- AI commander treasury accessors
- PVF send-helper contracts
- AICOM logging & AICOMSTAT telemetry
- AICOMSTAT v2 event census
- WASPSCALE v2 telemetry
- WASPSCALE v2-ext coverage audit
- Telemetry families reference
- Group lifecycle & entity reaping
- Batch AI spawner orchestrator
- Client funds/income HUD readout
- Server group GC & cap warning
- Town runtime tuning constants
- Client input/hotkey handler
- WASP base-repair system
- WASP DropRPG launcher/ordnance
- CoIn construction-interface client engine
- Town-capture garrison & airfield rebuild
- Map-control & minimap templates
- Client FPS & state telemetry
- Client service-proximity getters
- Airfield-exclusive roster & unit hints
- Unit-camera spectator system
- Town-garrison patrol/defense worker
- RequestTeamUpdate squad-discipline
- Arma2Warfare GPT assistant
- LoadoutManager build configs & defines
- GLOBALGAMESTATS extension logging
- Discord bot instrumented logging
- Eden/Everon & Taviana map content
- Cruise missile strike asset
- AI / HC
- AI headless and performance
- AI mods and pathfinding reference
- Headless client scaling and topology
- AI runtime/HC loop map
- Headless client init and stat loop
- HC delegation target selection
- Player AI caps and role balance
- Old WarfareBE FPS comparison
- AI commander autonomy audit
- Upstream BE 2073 AICOM delta
- Parent 2.073 divergence audit
- AI commander capture & fun plan
- AI commander B69 improvement roadmap
- AI commander B69 implementation sketches
- AICOM V2 cutover status
- Headless delegation and failover
- Commander reassignment call shape
- GUER Director living-resistance pitch
- Quality and operations
- Foundation perf findings & Tier-3 dead-ends
- Dead/stale code register
- Commander vote/reassignment
- Attack-wave authority
- Server runtime and operations
- Server ops runbook
- JIP enrollment & client data delivery (b74.2 lessons)
- Server gameplay runtime atlas
- PerformanceAuditAnalyzer
- Performance opportunity sweep
- Documentation plan
- Knowledge platform roadmap
- Wiki quality audit
- Wiki pruning and relevance ledger
- Audit findings queue (2026-06-03)
- Deep review findings
- Client UI / server-loop perf findings
- Performance gain simulation
- Self-host testing field notes
- Cleanup and work lanes
- Hardening and authority
- UI / player workflows
- Client UI, HUD and menus
- UI HUD and dialogs
- Player UI workflow map
- Client UI systems atlas
- UI IDD collision repair
- UI control class library reference
- UI theme palette and style macros
- UI design inspiration 2026-07
- Available-actions client gate FSM
- Gear/loadout/EASA atlas
- Gear template profile filter
- Vehicle cargo equip loop bounds
- Factory and purchase systems atlas
- Service menu affordability guards
- WASP overlay
- Class-skill system reference
- Skin selector and class swap
- Earplugs audio toggle
- Mission audio catalog
- HQ radio knowledge-base catalog
- QoL trio player hints
- Player vehicle/travel actions
- Tooling / release / integrations
- Tools and build workflow
- Warfare web tools
- Ecosystem & companion repos
- Zargabad tooling parity
- July 2026 release readiness
- Operator monitor and CPU affinity tools
- Tooling release readiness audit
- Source fix propagation queue
- Agent release readiness ledger
- Release source intake map
- Testing/debugging/release workflow
- Current RPT release gate
- RPT telemetry consumer port map
- External integrations
- Integration trust boundary audit
- AntiStack database extension audit
- Community & Dev
- Community & Dev
- Miksuu upstream wiki import / archive index
- Upstream changelog feature leads
- Developer history and upstream lessons
- Upstream Miksuu commit intel
- Upstream mining ledger
- Archive script mining v2
- Upstream BE 2073 AICOM delta
- Parent 2.073 divergence audit
- PR8 and Drone upstream lesson match
- Development lessons learned
- External research reports
- Audit archive 2026-07
- Briefing reference
- Utes invasion concept
- Miksuu archive: Home
- Miksuu archive: Welcome
- Miksuu archive: Big announcements
- Miksuu archive: Changelog
- Miksuu archive: Development process
- Miksuu archive: Discord bot
- Miksuu archive: Gameplay videos
- Miksuu archive: LoadoutManager
- Miksuu archive: Chernarus script architecture
- Base-game visual catalogs
- Compatibility and references
- HC upstream history and lessons
- Player stats branch audit
- BuyMenu EASA QoL branch audit
- Perf quick wins branch audit
- Commander positions branch audit
- Zargabad branch audit
- Quad AI Commander concept
- Arma 2 OA external reference guide
- Base-game config & image reference
- Arma 2 OA compatibility audit
- Arma 2 OA agent traps reference
- Arma 2 OA command versions
- Wiki source consistency
- External Arma 2 OA reference index