Function And Module Index

Function And Module Index

This page names the major function groups and what they are for. It is intentionally behavior-oriented so a developer or AI assistant can find the right file family quickly.

Common Function Families

• Common_Array*: array helpers used by older SQF code that predates richer utility libraries.
• Common_Get*: lookup helpers for factories, towns, camps, groups, side IDs, side logic/HQ, team state, funds, supply, upgrades, config data and positions (Common/Init/Init_Common.sqf:24-65,113-140). Depot lookup is a client family helper (WFBE_CL_FNC_GetClosestDepot at Client/Init/Init_Client.sqf:102), not a Common_Get* helper.
• Common_Set*: shared state setters for commander votes, team autonomy/respawn/move mode/move position/type, namespace/profile variables and turret magazines (Common/Init/Init_Common.sqf:75-80,150,171).
• Common_SendTo*: network abstraction around PVF dispatch to client(s) and server.
• Common_Handle*: event handlers for reload, AT, AA, missile/bomb/artillery, rocket tracer and alarms (Common/Init/Init_Common.sqf:6-16,66-68,141-143). Generic building damage handling is server-side (BuildingHandleDamages), not a Common_HandleDamage helper.
• Common_CreateMarker, Common_MarkerUpdate, Common_AARadarMarkerUpdate: marker creation/update layers.
• Common_LogContent: mission logging wrapper used for INITIALIZATION, INFORMATION, WARNING and error-style RPT lines.
• PerformanceAudit_*: local RPT audit writer helpers consumed later by Tools/PerformanceAuditAnalyzer.

Client Function Families

• Client_BuildUnit: main player purchase/spawn path after buy-menu selection.
• Client_UI*: list filling, gear templates, price updates, respawn selector and target updates.
• Client_Get*: client-side lookup helpers for respawn, income, gear content, nearby camps/depots/airports.
• Client_Handle*: map clicks, PVF dispatch, map state and HQ action helpers.
• Client_Delegate*: local AI delegation handlers when server delegates AI work to clients/headless.
• Client_WatchdogPlayerAI and Client_RecoverPlayerAI: player AI recovery/watchdog systems.
• Client_BookkeepBlinkingIcons and Client_SetMapIconStatusInCombat: combat marker blinking system.
• Client_UpdateRHUD: HUD/FPS overlay update loop with cached UI writes.

Server Function Families

• Server_BuyUnit: AI/team purchase path.
• Server_ProcessUpgrade: authoritative upgrade processing.
• Server_UpdateTeam: team state synchronization.
• Server_HandlePVF: server-side PVF dispatcher.
• Server_HandleDefense, Server_SpawnTownDefense, Server_ManageTownDefenses: town/static defense systems.
• Server_AI_SetTownAttackPath*: AI attack path selection and safety checks.
• Server_AI_Com_Upgrade: live AI commander upgrade worker; selects from Format ["WFBE_C_UPGRADES_%1_AI_ORDER", _side] (Server/Functions/Server_AI_Com_Upgrade.sqf:12), checks AI commander funds/supply and debits, but no obvious live scheduler has been found.
• Server_DelegateAI*: delegation to headless/client workers.
• Server_FNC_Delegation: selects delegation targets for town/player AI. No setGroupOwner rebalancing path has been found.
• Server_AssignNewCommander: commander assignment notification/AI-commander stop helper; likely call-shape bug because it assigns _side = _this while callers pass [_side, _commander].
• Server_HandleBuilding*, Server_Building*, Server_OnHQKilled, Server_MHQRepair: structure lifecycle and HQ damage/repair.
• Server_ChangeSideSupply, Server_PV_RequestSupplyValue: side supply network bridge.
• Server_LogGameEnd, Server_CallExtensions/GlobalGameStats: operational reporting.

Performance Audit Writer Family

The mission-side PerformanceAudit code is local telemetry plumbing, not a networked stats service. Init_Common.sqf:47 compiles Common/Functions/Common_PerformanceAudit.sqf on maintained roots. That file defaults PerformanceAuditEnabled from WFBE_C_PERFORMANCE_AUDIT_ENABLED and PerformanceAuditFlushInterval = 60 (Common_PerformanceAudit.sqf:9-10), writes only local RPT rows through diag_log (:109-149), and keeps separate PerformanceAuditData_CLIENT / PerformanceAuditData_SERVER buffers (:11-12,169-195). Client init starts ["CLIENT"] Spawn PerformanceAudit_Run at Client/Init/Init_Client.sqf:355-356; server init starts ["SERVER"] Spawn PerformanceAudit_Run at Server/Init/Init_Server.sqf:591-592.

Helper / surface	Source-backed behavior	Indexing note
PerformanceAudit_Record	Aggregates NAME, call count, total elapsed, max elapsed and last extra string in the local scope buffer (Common_PerformanceAudit.sqf:160-195).	Missing records mean missing instrumentation or disabled audit, not proof a path is cheap.
PerformanceAudit_Flush / PerformanceAudit_Log	Emits a periodic snapshot plus one row per aggregated script, converting elapsed seconds to avg/max milliseconds (Common_PerformanceAudit.sqf:109-149,196-219).	Rows are consumed offline by PerformanceAuditAnalyzer; server and clients write separate RPTs.
PerformanceAudit_Run	Emits session anchor/start rows, sleeps PerformanceAuditFlushInterval, flushes until gameOver, then flushes once more (Common_PerformanceAudit.sqf:222-241).	Use RPT collection in Testing workflow, not live tailing.
Representative client writers	RHUD, update-client, action polling, marker loops, salvage, player-AI watchdog and AAR/marker helpers record client-scope rows (Client_UpdateRHUD.sqf:199-201,367-369; updateclient.sqf:161-163,230-232; updateavailableactions.fsm:237; updatetownmarkers.sqf:119-121; Common_MarkerUpdate.sqf:65-88,216-241; Common_AARadarMarkerUpdate.sqf:36-38,178-194).	Client RPTs are needed for UI/HUD/marker conclusions.
Representative server writers	Town/camp/town-AI loops, cleaners/restorers, empty-vehicle/garbage collectors, delegation, AntiStack and town-defense workers record server-scope rows (server_town.sqf:343-345; server_town_ai.sqf:313-315; server_town_camp.sqf:151-153; emptyvehiclescollector.sqf:24-26; server_collector_garbage.sqf:26-28; Server_FNC_Delegation.sqf:67-69; Server_OperateTownDefensesUnits.sqf:150-153; AntiStack/mainLoop.sqf:46-48).	Server RPTs are needed for loop/cadence and AI/delegation conclusions.

Server AI Order Helpers

These helpers are compiled early in server init (Server/Init/Init_Server.sqf:13-18) and are real waypoint executors, but current static callers prove support/resistance use, not a general commander map-order queue. Use AI, headless and performance for the commander-order caveat.

Helper	Source-backed behavior	Current static caller status
AIMoveTo	AI_MoveTo.sqf:6-21 sets combat/behavior/formation/speed, runs CanUpdateTeam / UpdateTeam only for west/east teams, then calls AIWPAdd with one destination waypoint.	Support drops call it from paratroopers, para-ammo and para-vehicles (Support_Paratroopers.sqf:92,122; Support_ParaAmmo.sqf:38,96; Support_ParaVehicles.sqf:39,78).
AIPatrol	AI_Patrol.sqf:7-37 sets combat movement state, generates patrol waypoints, loops while surfaceIsWater _pos, then calls AIWPAdd.	Resistance CPatrol spawns it (AI_Resistance.sqf:16). The uncapped water-avoidance loop remains a branch-sensitive optimization/correctness candidate.
AITownPatrol	AI_TownPatrol.sqf:16-23,50-69 requires a town object, uses town/camp objects plus WFBE_C_TOWNS_PATROL_HOPS, loops while generated points are water, then calls AIWPAdd.	Compiled at Init_Server.sqf:15; a 2026-06-06 static Chernarus search found no live caller outside the compile line and the helper file. Treat it as latent until Arma smoke or a dynamic caller proves use.
AIWPAdd / AIWPRemove	AI_WPAdd.sqf:19,32-38 optionally clears existing waypoints, adds waypoints, and can apply scripted waypoint scripts/statements; AI_WPRemove.sqf:3-5 deletes waypoints from the end.	Used by the helper family and resistance SAD orders (AI_Resistance.sqf:14). Current static callers pass empty script/statement fields, so do not document a network-controlled waypoint-statement path without new evidence.

Client Modules

• Client/Module/AFKkick
• Client/Module/AntiStack
• Client/Module/AutoFlip
• Client/Module/CM
• Client/Module/CoIn
• Client/Module/EASA
• Client/Module/Engines
• Client/Module/MASH
• Client/Module/Nuke
• Client/Module/Skill
• Client/Module/supplyMission
• Client/Module/UAV
• Client/Module/Valhalla
• Client/Module/ZetaCargo

Common Modules

• Common/Module/Arty
• Common/Module/CIPHER
• Common/Module/IRS
• Common/Module/Reaktiv

Server Modules

• Server/Module/afkKick
• Server/Module/AntiStack
• Server/Module/MASH
• Server/Module/NEURO
• Server/Module/serverFPS
• Server/Module/supplyMission

Module Status And Gates

Presence in the tree does not always mean enabled in the current mission mode. Popper's module/support pass found this practical status split:

Module family	Status	Gate / note
Common/Module/Arty	Live.	Used through common artillery handlers and support flows.
Common/Module/IRS	Live.	Initialized through common init at Init_Common.sqf:320; vehicle/module availability still depends on constants and vehicle config.
Common/Module/Reaktiv	Dead / unreachable in current source.	Common/Module/Reaktiv/Reaktiv_Init.sqf:5 compiles the handler, but grep finds no caller outside Common/Module/Reaktiv/; Init_Common.sqf:319-323 initializes ICBM, IRS and CIPHER but not Reaktiv.
Client/Module/Nuke	Live and config-gated.	RequestSpecial / ICBM authority is the critical DR-27 risk.
Client/Module/EASA, Client/Module/CM	Live but config-gated.	Countermeasures are also gated by vanilla/OA mode.
Server/Module/AntiStack	Compiled but optional.	Runtime loops are dormant when WFBE_C_ANTISTACK_ENABLED == 0; external DB dependency is still live-server sensitive when enabled.
Server/Module/MASH	Marker relay present, marker feature broken.	MASH respawn and MASH map-marker sync are separate; the marker relay lacks a live client trigger/receiver.
Server/Support/Support_Paratroopers.sqf	Drop flow live, marker path broken.	Server sends HandleParatrooperMarkerCreation, but that command is absent from the client PVF registry, so the marker handler never receives an event.

High-Risk Edit Areas

• Init_CommonConstants.sqf: central constant namespace. Changes here affect both server and clients.
• Init_PublicVariables.sqf: PVF registration. Missing files or mismatched function names break networking; direct publicVariable channels outside this registry are inventoried in Networking/PV.
• description.ext / initJIPCompatible.sqf: both include generated version.sqf; a fresh checkout without generated version files will not preprocess cleanly.
• Client_BuildUnit.sqf and Server_BuyUnit.sqf: purchase/spawn paths with many factory-specific assumptions.
• Server/Init/Init_Server.sqf: long-lived server loops; duplicate or unconditional loops can hurt live performance.
• Tools/LoadoutManager: generated mission copying/packing; accidental edits to generated mission folders can be overwritten.

Continue Reading

Previous: SQF code atlas | Next: Networking/PV

Main map: Home | Fast path: Quickstart | Agent file: agent-context.json