Feature Status Register

Feature Status Register

This register separates working systems from partial, deferred or risky systems found during indexing.

Working / Active Systems

• Core Warfare loop: towns, commanders, bases, factories, upgrades, resources and victory checks.
• Client/server/common initialization split.
• Generic PVF request/response system.
• Player supply-truck missions on master.
• Enhanced day/night cycle with server authority and client smoothing.
• Server FPS publishing and RHUD/FPS HUD.
• Performance audit instrumentation plus analyzer.
• Anti-stack module with optional mission parameter.
• AFK kick through BattlEye publicVariable filter.
• MASH marker synchronization.
• ICBM/radiation module.
• EASA aircraft loadout module.
• Client marker blinking guarded by parameter.
• LoadoutManager mission copy/generation workflow.
• Discord bot status updates from exported game data.

Partial / Deferred / Needs Review

Area	Evidence	Status
Autonomous AI supply trucks	UpdateSupplyTruck compile is commented at Server/Init/Init_Server.sqf:36, but the live call [_side] Spawn UpdateSupplyTruck; remains at :383, gated by WFBE_C_ECONOMY_SUPPLY_SYSTEM == 0 && WFBE_C_AI_COMMANDER_ENABLED > 0. AI_UpdateSupplyTruck.sqf also references missing Server/FSM/supplytruck.fsm.	Config-gated latent breakage. Default supply system 1 is safe; supply system 0 with AI commanders is broken until the compile and FSM are restored or redesigned.
Task system	TaskSystem compile and TownAddComplete spawn are commented in Client/Init/Init_Client.sqf though Client_TaskSystem.sqf still exists.	Disabled/partial. Re-enable only after checking task spam/JIP behavior.
MASH marker receiver	receiverMASHmarker.sqf (registers the WFBE_SE_MASH_MARKER_SENT client EH) is referenced only by the commented compile at Client/Init/Init_Client.sqf:132; the server re-broadcast (Server/Module/MASH/MASHMarker.sqf) is live.	Confirmed broken (receiver never registered) → MASH map markers never appear; MASH respawn itself is independent. See Deep-review findings DR-3.
Paratrooper drop markers	Server/Support/Support_Paratroopers.sqf:117 sends HandleParatrooperMarkerCreation, but it is absent from _clientCommandPV in Init_PublicVariables.sqf (no EH; CLTFNC… never compiled).	Confirmed broken/dead on all configs; receiver file exists but is unwired. See Deep-review findings DR-2.
PV dispatch trust boundary	Server_HandlePVF.sqf/Client_HandlePVF.sqf run Call Compile on the sender-chosen command string with no validation; BattlEyeFilter/publicvariable.txt has only the kickAFK feature rule (no security filter).	Live-server hardening gap (High). Validate the command string before compile + add a real BE PV filter. See Deep-review findings DR-1.
Old map blink loop	Client_BlinkMapIcons and AddUnitToTrack compiles plus old exec are commented; newer singular Client_BlinkMapIcon and bookkeeping are active.	Legacy replacement. Avoid resurrecting old loop without perf review.
Server map blinking units	Server_MapBlinkingUnits.sqf exec is commented in Init_Server.sqf.	Disabled/legacy.
Old WASP init block	initJIPCompatible.sqf contains a commented WASP init block marked as old and resource-heavy.	Legacy/deferred removal. Individual WASP scripts still exist and may be called elsewhere.
Server FPS compile variable	WFBE_CO_FNC_monitorServerFPS compile lines are commented, but Init_Server.sqf later execVMs Server/Module/serverFPS/monitorServerFPS.sqf.	Not broken; document the direct exec path.
MASH marker duplicate compile	One MASH marker compile is active and a later duplicate is commented.	Likely cleanup artifact; do not re-enable both.
Volumetric clouds	Parameter exists but is forced disabled in constants and client init.	Intentional optimization.
Modded map generator path	SqfFileGenerator.cs has TODO to add modded maps back in one path.	Verify before assuming modded mission regeneration is complete.
Dangerous CRV7PG loadouts	LoadoutManager has WARNING_GAME_CRASH_DO_NOT_USE_IN_LOADOUTS_* weapon/ammunition classes, and WILDCAT.cs references one.	High-risk data. Keep these warnings visible when changing loadouts.
Gear menu cleanup	GUI_BuyGearMenu.sqf has a TODO about securing vanilla/removing unused code.	Low-priority cleanup unless touching gear UI.
Fast travel fee	GUI_Menu_Tactical.sqf TODO mentions travel fee/mod parameter work.	Missing/unfinished feature.
Base/town dynamic logic TODO	Common/Init/Init_Common.sqf has a TODO around dynamic logic presence.	Low-level init cleanup candidate.
CoIn border TODO	Client/Module/CoIn/coin_interface.sqf notes temporary border logic should move if logic position changes.	Construction UI risk.
AI attack radio/combat tuning	Server_AI_SetTownAttackPath.sqf TODOs mention combat mode, speed and radio on waypoint completion.	Enhancement backlog.

Broken Feature Candidate: AI Supply Logistics

This is the clearest broken/abandoned feature. AI_UpdateSupplyTruck.sqf is present and loops over wfbe_ai_supplytrucks, but it cannot run correctly because the compile is disabled and the referenced supplytruck.fsm is absent. PR #1 correctly defers autonomous supply helicopters because the AI logistics base is incomplete.

Claude sharpened the status on 2026-06-01: the feature is not cleanly inert. In Server/Init/Init_Server.sqf, the compile line is commented, but the per-side init still calls [_side] Spawn UpdateSupplyTruck; when supply system 0 and AI commanders are enabled. With current defaults, WFBE_C_ECONOMY_SUPPLY_SYSTEM is 1, so normal play does not hit the call. If an admin selects supply system 0 with AI commanders, the server can hit a nil-code spawn error, and restoring the compile would still fail later because Server/FSM/supplytruck.fsm is missing.

Confirmed Defect: Stacked Supply-Vehicle Killed Handlers

PR #1 adds or extends Server/Module/supplyMission/supplyMissionStarted.sqf so supply vehicles can award interdiction cash when destroyed. The script adds a Killed event handler every time a supply mission starts, with no removal or already-tracked guard. Reusing one vehicle across many missions stacks handlers. Current double-payment risk is bounded because the first handler sets SupplyAmount to 0, but the handler leak is real and future side effects would multiply.

Missing Feature Candidates

• Autonomous AI supply trucks/helicopters.
• Formal generated docs from LoadoutManager data classes into mission docs.
• Automated validation that generated Takistan/modded missions match Chernarus source after docs/code changes.
• Automated SQF syntax or reference validation in CI.

Continue Reading

Previous: External integrations | Next: AI assistant guide

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