Skip to content

Feature Status Register

Jump to bottom
rayswaynl edited this page Jun 22, 2026 · 471 revisions

Feature Status Register

This register separates working systems from partial, deferred or risky systems found during indexing. For revive/remove decisions on dormant feature paths, use Abandoned feature revival.

What this page is

  • Canonical risk-and-readiness map for current gameplay feature health.
  • Evidence-first patch status for active systems, partial systems and likely regressions.
  • Canonical cross-link hub so subsystem pages and playbooks route users here for current patch risk and ownership.

Where it lives

How this page runs in the workflow

  1. Read this register first for risk ranking before opening a subsystem playbook.
  2. Use [Area] rows to pick the current highest-impact lane and then open:
    • Source index / atlas pages (e.g., SQF-Code-Atlas.md, Server-Gameplay-Runtime-Atlas.md)
    • Hardening roadmap
    • DR/cross-link pages (Deep-review findings, Public-variable channel index, feature atlases)
  3. Prefer this page for the latest patch status and known open dependencies before editing source.

What depends on this page

Risk notes

  • Keep patch-risk edits in-place and one-way: add proof to canonical pages instead of repeating deep call stacks in this register.
  • Treat entries marked "patch-ready-current-source-unpatched" as live claims requiring source+vanilla validation before changing status to published.
  • If a finding is promoted or closed, update this register and the corresponding lane record in agent-feature-status.jsonl first, then mirrors and progress pages.
  • Use Developer history and upstream lessons when a risky feature overlaps upstream supply, JIP, marker, town-AI, performance or reverted-branch history.
  • Upstream-derived risk rows should name exact refs when used for implementation claims. The current local miksuu/master head checked for the 2026-06-13 P0 network refresh is b8389e74; use Community & Dev and Upstream Miksuu commit intel before turning upstream lessons into implementation claims.

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.
  • Client auto view-distance and target-FPS hotkeys; current source uses a 60 FPS default, +/-4 FPS band and map-visible guard.
  • Anti-stack module with optional mission parameter.
  • AFK kick through BattlEye publicVariable filter.
  • Mobile ambulance respawn support; MASH support is branch-sensitive and listed below.
  • ICBM/radiation module.
  • EASA aircraft loadout module.
  • Client marker blinking guarded by parameter.
  • Air Event override parameter remains live: it forces event economy/upgrade-clearance defaults and hides ICBM plus Avenger/Tunguska-style heavy AA. Canonical route: Mission parameters.
  • LoadoutManager mission copy/generation workflow.
  • Discord bot status updates from exported game data.

Partial / Deferred / Needs Review

Area Evidence Status
Client-visible indicators and state surfaces 2026-06-06 indicator scout/sharpening and indicator-surface-matrix-index passes found and routed indicator families across Rsc/Titles.hpp, Client_UpdateRHUD.sqf, updateavailableactions.fsm, client_title_capture.sqf, marker loops, Tactical/Respawn markers, support marker PVFs, Buy Units/EASA/Gear/Upgrade icons, server-FPS/status publishers and Client/Images references. 2026-06-22 status-counter pass split player HUD SERVER_FPS_GUI, compatibility WFBE_VAR_SERVER_FPS, PerformanceAudit RPT/tooling and transient supply/status signals, with branch scope checked across docs a27086cd, current stable origin/master@0139a346, Miksuu b8389e74, perf 0076040f and historical a96fdda2. Matrix seeded; status-counter family refreshed; other families remain per-family work. Use Client UI systems atlas and status counter audience split to pick one surface family at a time for branch/root validation, owner-page integration or pruning before redesigning indicators.
Skin selector/class swap WFBE_C_SKIN_SELECTOR defaults to 0 (Common/Init/Init_CommonConstants.sqf:601), the WF-menu shortcut is hidden (Rsc/Dialogs.hpp:1258), but current source still has join-time, WF-menu and User11 openers plus the replacement-player apply chain (Client/Module/Skill/Skill_Init.sqf:75-77; Client/GUI/GUI_Menu.sqf:211-215; Client/Init/Init_Keybind.sqf:1-14; WASP/actions/SkinSelector/SkinSelector_Apply.sqf:207-257). Source-present, default disabled, smoke pending before live-feature wording. Use Skin selector/class swap before enabling or editing class pools, ghillie role gates, handler restoration or respawn persistence.

Networking / Public-variable hardening lane (source-backed)

This lane tracks direct channels, PVF authority boundaries, and JIP semantics that are still open after the PVF dispatch trust patch lane.

  • publicVariable/publicVariableServer direct request channels are not hardened by PVF allowlisting.
  • request handlers still need explicit side/team/ownership checks even after dispatch is fixed.
  • missionNamespace/JIP handling differs by channel; some flows are request-response only and are not replay-safe.
Area Evidence Status
PVF/PVEH sender authentication (systemic) Deep-review findings DR-55 remains open after the dispatcher lookup change. 2026-06-22 refresh: docs branch HEAD@ade4d356 Chernarus forwards only the value tuple at Common/Init/Init_PublicVariables.sqf:46,51 and still dispatches via Server_HandlePVF.sqf:14 / Client_HandlePVF.sqf:22 Call Compile; Miksuu b8389e74 and origin/perf/quick-wins@0076040f match that old dispatcher shape in checked maintained roots. Current stable origin/master@0139a346 and B69 origin/claude/b69@0a1ccb4d forward only (_this select 1) at Init_PublicVariables.sqf:56,61; their server/client dispatchers resolve missionNamespace CODE at Server_HandlePVF.sqf:14-15 / Client_HandlePVF.sqf:32-33 but still do not pass authenticated publisher context. Current-stable high-risk examples include RequestVehicleLock.sqf:3-8, RequestChangeScore.sqf:3-8,13, RequestNewCommander.sqf:3-14, RequestTeamUpdate.sqf:3-25, direct AttackWave.sqf:19-42, SupplyMissionCompleted supplyMissionCompleted.sqf:2,6-12,31,40-45,52 and the RequestSpecial router. Open — P0. Current origin/master@0139a346 removes dispatch-time Call Compile, but sender authentication and per-handler side/role/funds/object re-derivation still close the forgery surface. See agent-hardening-backlog.jsonl#pvf-handler-sender-authentication.
New source-confirmed economy/scoring/AI findings DR-49 side-supply underflow guard adds supply (Common/Server_ChangeSideSupply); DR-52 support specials no server auth; DR-53 PR#1 supply-heli forgeable amount/double-reward; DR-56 ARTY_HandleSADARM thread-leak/busy-wait. DR-57 town patrols never spawn is now historical for the old 89ae9dad path: current origin/master@0139a346 retires that path and adds Patrols v2 in both maintained roots. Open except DR-57 current-master route. The economy/authority/perf findings remain source-unpatched. Patrols v2 is source-present and smoke-pending; see Towns/camps/capture and Source fix propagation queue. DR-50 now has a dedicated HQ score row below.
HQ-kill score double-award (DR-50) Commander/HQ lifecycle owns the branch matrix. Current stable recheck 2026-06-21: origin/master@0139a346 Chernarus and maintained Vanilla both keep the two-award shape in Server/Functions/Server_OnHQKilled.sqf: generic HQ building score from _points = 30000 / 100 * WFBE_C_BUILDINGS_SCORE_COEF at :23, awarded at :52 / :54, plus a second _score = 900 HQ bounty at :83 / :86 under the non-teamkill guard at :80. The coefficient remains 3 at Common/Init/Init_CommonConstants.sqf:529. Older docs/Miksuu/perf/release/feat-ai refs remain branch-scoped on the owner page. Patch-ready, current-stable-unpatched scoring bug. A clean enemy HQ kill pays 1800; a friendly/teamkill HQ kill still gets the generic 900. Keep one non-teamkill award, make teamkills score zero, propagate maintained Vanilla and smoke enemy/friendly HQ kills plus DR-20 idempotency interactions.
Commander reassignment call-shape (DR-15) Commander reassignment call shape owns the refreshed branch matrix. Current stable origin/master@0139a346 Chernarus and maintained Vanilla now unpack _side = _this select 0 / _commander = _this select 1 at Server_AssignNewCommander.sqf:4-5; Miksuu b8389e74, origin/perf/quick-wins 0076040f, historical release a96fdda2 and historical AI-commander c20ce153 match that maintained-root helper shape. Docs branch b44aaaf8 still uses _side = _this at :3, and current stable Napf/Eden/Lingor full modded forks still use _side = _this at Modded_Missions/*/Server/Functions/Server_AssignNewCommander.sqf:3. Current-stable maintained-root helper fix source-present; broader reassignment still open. Do not reopen the helper unpacking on current stable. Choose one new-commander-assigned sender, switch commander assignment UI to row value/team identity, keep requester authority separate, and do not claim modded propagation without a modded maintenance decision.
Upstream supply-run exploit/JIP regression pattern Miksuu PR #10 / merge 97dfff26 fixed remote supply-truck activation; PR #11 / 8164cc33 added a 50 m "too far" notification; PR #12 / 86ec28d6 fixed that notification firing during JIP. Confirmed historical risk. Keep supply mission start/reward hardening server-owned and test late join + remote-start behavior before merging new supply/cash-run variants.
Town-defense activation/capture-state regression pattern 4aaa814a and 6189f3c5 optimized town/camp/town-AI scans; follow-ups a20a5a0f, 84b1b684, ea0bff2e restored reliable/pre-capture activation and prevented defenders from waking enemy towns; e4be1958 adds capture-side cleanup. A 2026-06-22 ref scan found no Server_CleanupExpiredTownDefenseAssets.sqf path in docs checkout f7aad9a8, current stable origin/master@0139a346, current Miksuu b8389e748243, perf/quick-wins@0076040f, historical release a96fdda2, origin/feat/aicom-fleet-improvements@cc5090bed4ad or B69 origin/claude/b69@0a1ccb4d, so older 89ae9dad persistence-helper notes are branch-historical rather than current branch truth. Historical regression lesson; current helper claim retired. Keep activation/capture-state changes smoke-gated and re-audit capture persistence before treating it as current stable behavior. Current tracked town-AI vehicle deletion risk routes to Town AI vehicle despawn safety.
Upstream marker locality/cache regression pattern 9a550b7a reverted a group-leader marker global-var experiment; 9c72a281, 951e72cb, 332874fd fixed marker tracking, disconnect staleness and side visibility leaks. Confirmed historical risk. Marker/cache changes need side-visibility and disconnect/reconnect validation.
Deep-history AntiStack/RequestJoin fragility 09131233, 841d16af, 88a2ef49, 448b1d85, b32babc7 show command typo, launch-state semantic change, RequestJoin fixes, DB type crash and an AntiStackV6 revert. Confirmed historical risk. AntiStack changes need launch/late join, teamswap, disabled-mode, DB-unavailable and monitoring-only validation.
Deep-history removed task system f61f7222 removed task system entirely; 4881e0d5 removed it from all terrains. Confirmed removed/deferred. Do not revive as a small UI toggle; rebuild as a new JIP-safe task feature if owner wants it back.
Deep-history generated map/version failure pattern 081c1dc4 added copypasted untested modded terrain files; c312b0ec added missions with copypaste method; 812e9596 removed Tasmania after clean-repo mission-load failures tied to ignored/generated version.sqf. Confirmed tooling/release risk. Generated version.sqf and clean-checkout map loads are release gates.
Deep-history branch tombstones and reverted PRs oldMasterBranch tip 3a7972a2 deletes old master contents; PR #3 HQ repair price merged then 346e3be8 reverted it; PR #9 endgame music closed unmerged; A3 test tree removed by 83298186. Confirmed negative knowledge. Do not revive old branch or PR content from name/status alone; check later reverts, branch family and OA compatibility first.
Deep-history client init/UI/marker lifecycle risk 3ff02aea moved clientInitComplete to the real end of init; c6d2539e fixed UI global action state; 95a12305 fixed UAV marker audience leakage; 9c72a281 restored marker motion after cache optimization. Confirmed historical risk. Client/UI/marker work must preserve lifecycle ordering, side audience, moving-marker position refresh and JIP behavior.
Deep-history construction/removal/runtimes 77a07bc0 reverted construction argument dedupe; 16856ae7/8b7fab95 removed guerilla barracks across FSM/HC/buy paths; 33fb2676 reverted supply performance work using wrong authority context. Confirmed historical risk. Construction/removal/performance edits need call-contract docs, full reference greps and dedicated-server/JIP smoke.
Second-wave release tooling and modded packaging risk Current ZipManager.cs packages Missions and Missions_Vanilla while Modded_Missions is commented out; 2a13ce36 requires env var 7za; 3458e714 handled locked file copies; f095e461 fixed Takistan DB map ID post-copy. Confirmed tooling/release risk. Treat release output as Chernarus + generated Vanilla/Takistan unless modded packaging is re-enabled and validated; inspect LoadoutManager logs, 7za, version.sqf, and terrain post-copy fixes.
Second-wave HQ repair and ICBM economy authority risk PR #3 / 7cd0e18d increasing HQ repair cost was reverted by 346e3be8/59a995e8; 5db438ca 75k nukes were reverted by 31d8a06d; current ICBM/HQ repair paths still have client-side action/debit authority concerns. Confirmed historical + current authority risk. Do not add HQ repair escalation or ICBM price/effect changes until server validates affordability, side/team/commander, cooldown, debit and final effect.
Second-wave marker blinking and HC routing risk Dec 2025 marker blinking chain includes 2f6ff43d, 9a550b7a, 9c1fe110 defaulting blinking off; HC upstream history adds a241ac75, 6760f1a3, 1d79ba2a, 6b90c872, f5e8fa47 and bb01ebfc for typed HC routing, side-less call hazards and generated mission-slot drift. Confirmed branch-history risk. Keep marker blinking off by default; HC changes need typed pools, server update-back, side-less HC tests, generated mission slot checks and event-handler cleanup proofs.
Second-wave score/bounty/supply-compensation coupling f17445c1, b31539b4, cc127ef4, 415615c9 changed score/bounty/teamkill handling; upstream/SkillDiffCompensation feeds side supply through ChangeSideSupply. Confirmed historical risk. Treat score awards, bounty math and skill-diff compensation as AntiStack/economy changes; harden side-supply authority before expanding compensation.
Old WarfareBE FPS comparison and AI-cap debate Old WarfareBE performance comparison compares old BennyBoy WarfareBE Takistan Lite at aeb71bb against current Wasp Chernarus and finds lower old player-AI defaults (12 player cap, fixed Soldier +6, no commander +10) but no magic old town-AI architecture: old BE still has town nearEntities, spawn/despawn, static gunners, cleanup collectors, PVF dispatch and marker loops. Confirmed docs/test lane, not a source patch. Use the old mission as an A/B baseline and run matched tests before changing gameplay: normal-role cap 8-10, Soldier/commander identity preserved deliberately, HC present/absent logged, active town/static counts split from player followers, and view distance separated from server-AI load.
Old-FPS scout easy-win harvest The returned old-warfarebe-fps-scout addendum confirmed both FPS publishers are active, SERVER_FPS_GUI is the RHUD path while WFBE_VAR_SERVER_FPS lacks an obvious source consumer, current PV/PVF surface is broader but server requests use publicVariableServer, delegated town AI avoids global per-unit init, AntiStack/PerformanceAudit are current-only A/B variables, and static-defense HC readback remains unproven. Evidence harvested into owner pages. First actions are test/config/docs: consumer-map FPS variables, pin view distance, run AntiStack/audit ON/OFF presets and avoid claiming static-defense HC as a confirmed FPS win. Source patches remain future code-owner work.
Dynamic player-AI cap and AI-source scoreboard The old-vs-current-fps-opportunity-scout and old-be-current-wasp-fps-opportunity-scout-2 reports at C:\Users\Steff\Documents\Codex\2026-06-05\wasp-old-vs-current-fps-investigation\outputs\Old-BE-vs-Current-Wasp-FPS-Opportunity-Audit.md and C:\Users\Steff\Documents\Codex\2026-06-05\wasp-old-mission-fps-opportunity-window\outputs\Old-BE-vs-Current-Wasp-FPS-Opportunity-Scout.md promote a role-aware cap design: public pilot normal roles near 10, Soldier preserved higher, commander bonus reduced from +10, and final policy driven by a server-published side AI budget. The final scout fixes the preferred test order as AI-source scoreboard, cap pilot, HC proof, low-SV town branch, static-defense HC/accounting, cleanup/object-count evidence, then PV/server-FPS/network cleanup. Owner-decision gameplay/performance lane. Not a confirmed FPS fix until the full-server FPS opportunity pack records 10/15/20/25/30-player evidence. Any implementation must keep buy menu and RHUD cap formulas aligned, enforce lower caps non-destructively for future purchases first, and treat static-defense HC accounting as a proof gate rather than a claimed FPS win.
WF menu ops-console reskin branch origin/feat/wf-menu-ops-console head 0767c0b5 is a UI-only theme branch from origin/master 2cdf5fb8: Chernarus + maintained Vanilla Rsc/GUI/HUD files, new brand_chevron.jpg, and docs/superpowers plan/spec/mockup files. Evidence: Rsc/Styles.hpp:10-40, Rsc/Ressources.hpp:117-131,274-277, Rsc/Dialogs.hpp:1057-1064,1173-1179,1240-1249, Rsc/Titles.hpp:178-179. Confirmed branch-review risk. Not gameplay logic, but not release-ready until Arma 2 OA visual smoke proves font availability, texture path/case handling, contrast, hub/menu/HUD rendering and Chernarus/Vanilla parity. Also clean branch trailing whitespace reported by git diff --check in docs/superpowers/plans/2026-06-03-wf-menu-ops-console.md:78,179. Use Client UI systems atlas and the branch-only feature smoke pack.
BuyMenu/EASA QoL branch Historical QoL commit a66d4691 is a narrow Chernarus UI branch snapshot; current origin exposes no feat/buymenu-easa-qol head on 2026-06-21. The snapshot carries unaffordable buy-unit price tint (Client_UIFillListBuyUnits.sqf:1,61-62,104), live queue counts on factory tabs (GUI_Menu_BuyUnits.sqf:201-210), selected-unit cost formula/display work (GUI_Menu_BuyUnits.sqf:280,335,388,444,487) and EASA current-loadout highlight/preselect (GUI_Menu_EASA.sqf:29-40). Full audit: BuyMenu EASA QoL branch audit. Confirmed historical branch-review risk, low blast radius. It is UI-only, 3 Chernarus files and git diff --check clean, but not propagated to maintained Vanilla and not represented by a live origin head. Needs Arma 2 OA menu smoke for affordability color versus full/crew cost, queue label refresh/no flicker, final idc 12034 price after the later write, and EASA current-loadout selection including filtered/unset cases if revived.
GUER Insurgents playable resistance source Current origin/master@0139a346 contains the merged GUER lineage (9af83596 is an ancestor) and later maintained-root parity. Both Chernarus and maintained Vanilla Takistan carry WFBE_C_GUER_PLAYERSIDE (Rsc/Parameters.hpp:587), gate/constant fallbacks (Init_CommonConstants.sqf:76-79), gated side hostility (Init_Server.sqf:11), shared player overlay loading (Root_GUE.sqf:129-130; Root_TKGUE.sqf:102-104; Root_GUE_PlayerOverlay.sqf:47,69-82), economy startup (Init_Server.sqf:584-612; Server_GuerStipend.sqf:14,30), VBIED action/handler (Action_GuerVbiedDetonate.sqf:33,46; Server_HandleSpecial.sqf:484-495) and buy/service UI hooks. Source-present in both maintained roots; smoke and balance still pending. Use GUER Insurgents branch audit for current source status, GUER insurgent player economy and GUER VBIED detonate action for subsystem detail, and keep the old Gameplay systems atlas intake as historical branch-review memory. Smoke gate-off, Chernarus gate-on, Takistan gate-on, VBIED auth/blast/reward, Ka-137 fire geometry and actual A2 OA HC behavior before release-complete wording.
PR #43 / B68 AI commander live soak branch PR #43 is open from claude/b57-soak-proposals to master; gh pr view 43 on 2026-06-21 returned head b8a1505f8a89881f487a03262f066c8b33eca94d, updated 2026-06-21T17:26:33Z. The B68 commit b8a1505f changes four Chernarus files: it removes the W17 global Supply Convoy marker route at Server/Functions/AI_Commander_Wildcard.sqf:994 while origin/master@0139a346 still creates it at :981-984; it adds/tunes AICOM last-stand/stranded-remnant/retreat constants at Common/Init/Init_CommonConstants.sqf:277-284,319; it changes maneuver-strength and last-stand logic at AI_Commander_Strategy.sqf:41-68,99,441,571-590; and it adds retreat reissue/distance caps at AI_Commander_Produce.sqf:90-151. Live Chernarus branch evidence, not merged master/release wording. Use AI commander autonomy audit and marker catalog. Before merge/release, smoke friendly-only convoy visibility, enemy non-visibility, winning-side attack pressure, last-stand lifting, far lone survivor cull, near survivor return/refit and maintained Vanilla propagation.
B69 AI commander current branch / PR #47, PR #48 and PR #49 branch merges origin/claude/b69@39eed5c0 is a branch-only B69 series on top of B68 b8a1505f; b8a1505f..39eed5c0 is 22 files / +699 / -91 and changes only current Chernarus mission files plus B69-IMPLEMENTATION-PLAN.md. PR #48 merged claude/b71-pr-harvest -> claude/b69 at 4dcc10b143a0fc4d94e55f5506217d208994d4ff; PR #49 then merged claude/b72-tints-on -> claude/b69 at 39eed5c02d8ba9c5a27b7a4173607526edc0677e. The latest delta 4dcc10b143a0..39eed5c0 is one Chernarus constants file / +1 / -1 with no maintained Vanilla diff, flipping WFBE_C_VEHICLE_TINTS to nil-guard default 1 at Init_CommonConstants.sqf:795; the adjacent comment still preserves the older default-off / in-engine cosmetic-check caveat. Branch source-present, Chernarus-only, smoke/propagation pending. Use AI commander autonomy audit, B69 roadmap, B69 sketches and PR cleanup lab. Do not call B69 release-ready or master/stable merged until Arma smoke, maintained Vanilla propagation or explicit scope, review and master-target routing are recorded.
Player stats branch origin/feat/player-stats head e01e47e1 adds off-by-default SQF stat emission (WFBE_C_STATS_ENABLED = false at Init_CommonConstants.sqf:443), kill-stat hooks (RequestOnUnitKilled.sqf:51-65), Server/Stats/*, DiscordBot Stats/* RPT tailing/accumulation and DiscordBot.Tests/*. Local branch validation passed: dotnet test 13/13. Full audit: Player stats branch audit. Confirmed branch-review risk. Safe by default because the feature flag is false, but enabling it is operational/integration work: decide RPT path/state-file ownership, UID/privacy policy, log volume, corrupt stats.json recovery, deployment config, Chernarus-only vs Vanilla propagation and whether stats belong in DiscordBot or the mission extension.
Perf quick-wins branch origin/perf/quick-wins head 0076040f is a Chernarus-only fix branch with 18 files, +27/-27 and clean git diff --check. It patches known docs-backed defects including side-supply clamp shape (Common_ChangeSideSupply.sqf:25, Server_ChangeSideSupply.sqf:12,36), factory queue cleanup on crewless buys (Client_BuildUnit.sqf:365-368), paratrooper marker PV registration (Init_PublicVariables.sqf:40), mine-cleaner pair removal (mines_cleaner.sqf:17), dead-object wfbe_trashed handling (server_collector_garbage.sqf:17), fixed resource interval (updateresources.sqf:74), camp-bunker nil-code EH removal (Server_HandleSpecial.sqf:235-236) and kill-assist bounty type (RequestOnUnitKilled.sqf:92). Full audit: Perf quick wins branch audit. High-value branch-review risk. Treat as a fix candidate, not proof that stable master is fixed. It is source-Chernarus only; Missions_Vanilla has no branch diff and still shows the old clamp/EH/kill-assist/resource-loop shapes. For factory queue, it fixes the crewless counter leak only; the low-entropy varQueu token remains open. Reconcile with docs/source propagated fixes, propagate maintained Vanilla deliberately, keep DR-44 side-supply authority separate from the clamp, and smoke economy debit/no-credit inversion, factory queue counters/tokens, paratrooper marker handling, cleaner/camp/resource loops and WASP touched actions before merge/release wording.
Commander positions / modular walls branch origin/feat/commander-positions head 560db61c has merge base f5985b77, 83 changed files and broad Chernarus/Vanilla deltas. The actual WDDM commander-position runtime is source-Chernarus only: anchor classes (Structures_CO_US.sqf:168-174, Structures_CO_RU.sqf:166-172), template map (Init_Defenses.sqf:93-183), compile (Init_Server.sqf:26) and Server_ConstructPosition.sqf:1-66. No Server_ConstructPosition or WFBE_POSITION_TEMPLATE_MAP hits exist under maintained Vanilla on branch grep. Full audit: Commander positions branch audit. Broad branch-review risk. Do not describe as a clean construction-only branch or Vanilla-propagated feature. Before promotion: split or audit unrelated deltas, clean branch whitespace, re-check construction request authority (DR-6), smoke position placement at the clicked map point, HQ undeploy cleanup, CoIn UI, and decide/implement maintained Vanilla propagation.
Zargabad low-pop map branch origin/feature/zargabad-map head e9294ede adds a new maintained Vanilla Zargabad mission folder and terrain/tooling support: ZARGABAD.cs:1-13, SqfFileGenerator.cs:127-130, initJIPCompatible.sqf:121-124, Init_Boundaries.sqf:4-10, Init_Zargabad.sqf:1-125 and Guides/Zargabad-Completion-Gates.md:8-20. Branch diff is huge: 832 files, +77733/-95. The refreshed head tunes low-pop defaults across constants, generated parameters and validators: AI max 6, player AI max 8, Soldier skill cap 3, team supply cap 30000, UAV 650, town mortar/patrol 420/300, chopper/plane countermeasures 12/18, starting funds 8000, starting supply 3600, ordnance ranges 1500, Air AA/flares/thermal on, ICBM off and price multipliers 0.95/1.15/1.4/1.75/2.0/1.0. Local static branch validation passed at e9294ede with Tools\Validate-ZargabadMission.ps1: 13 towns, 19 camps, 1 airport, 9 starts, 33 defense logics, no duplicate object ids, no missing sync targets and no Takistan Zargabad-module spillover. Full audit: Zargabad branch audit. Map-release branch-review risk. Static validation is strong but runtime evidence is still open. Treat as a full terrain release candidate and low-pop balance profile, not a normal generated-mission copy. Needs generated whitespace cleanup (git diff --check reports 3542 findings), hosted/dedicated/JIP/HC runtime evidence, screenshot/RPT audit packet validation, town/base/camp/economy/air-price balance checks, edge-guard/black-market smoke and class-load verification.
Supply helicopter branch historical head 2026-06-22 remote check found no live origin/feat/supply-helicopter, origin/*supply* or origin/release/* head. Historical PR #1 evidence remains at old head 262dc431: Air-factory upgrade 3 load/action gates (Skill_Apply.sqf:62-72, supplyMissionStart.sqf:21-29), Air upgrade 4 cash-run branch (supplyMissionCompleted.sqf:24-35), lobby toggle (Rsc/Parameters.hpp:4-10), load/unload timers and central class lists (Init_CommonConstants.sqf:168-180). That head clears SupplyAmount/SupplyFromTown but not SupplyByHeli (supplyMissionCompleted.sqf:40-41). Historical PR #1 branch-review evidence. Current stable origin/master@0139a346 now carries the maintained-root supply-heli/cash-run shape; use Supply mission architecture for current scope. The old PR #1 gates remain useful if revived: Vanilla propagation, retained SupplyByHeli state, timer UX, Air 3/4 economy semantics and runtime smoke.
PR #8 release head delta Current origin/release/2026-06-feature-bundle head a96fdda2 has moved beyond the older 7ff18c49 delegated-AI/cleaner checkpoint. Current release Chernarus and maintained Vanilla keep delegated town-AI group registration/update-back (Client_DelegateTownAI.sqf:29-44; Server_HandleSpecial.sqf:86-115), static-defense HC update-back still commented (Client_DelegateAIStaticDefence.sqf:27-30), fallback-group locality guards (Common_CreateUnit.sqf:34-37; Common_CreateUnitForStaticDefence.sqf:67-70) and cleaner/restorer startup timer floors (crater_cleaner.sqf:3-7,50; droppeditems_cleaner.sqf:3-7,46; ruins_cleaner.sqf:3-7,30; buildings_restorer.sqf:3-6,31). Stable cf2a6d6a and release a96fdda2 also carry marker-based commander-built ARTY discovery at Construction_StationaryDefense.sqf:132-135 plus Common_GetTeamArtillery.sqf:46-78. Release-branch review risk. This is not current-source proof and does not close DR-42 static-defense update-back/failover; update-back remains design work. Smoke HC/town/static delegation, commander-built ARTY discovery and long-session cleaner/restorer behavior before release-ready wording. Use PR cleanup lab, Headless delegation/failover, Marker cleanup/restoration and Testing workflow.
Drone/recon support branch split origin/feat/drone-saturation-strike head 8ca4be90 is the latest drone tuning branch; origin/feat/recon-uav head 563418ea adds server AI-flown ReconUAV/ReconUAVRecall and removes the old UAV module, but only includes drone history through 93b47594. Drone diff from stable origin/master is 17 total files (+1133/-4), of which 15 are source-Chernarus mission files (+379/-4) and 0 are maintained Vanilla mission files. Recon diff is 25 total files (+1461/-657), of which 22 are source-Chernarus mission files (+593/-657) and 0 are maintained Vanilla mission files. Confirmed branch-review risk. Treat drone strike and recon UAV as separate support features. Before merge, resolve drone tuning drift, move paid support authority server-side, validate old-UAV replacement/recall/reveal/JIP cleanup, and either propagate generated Vanilla or keep Chernarus-only scope explicit. Use PR8 and drone upstream lesson match plus the branch-only feature smoke pack.
Direct attack-wave request trust (ATTACK_WAVE_INIT / ATTACK_WAVE_DETAILS) Attack-wave authority playbook owns the branch/root matrix. Current stable origin/master@0139a346 Chernarus and maintained Vanilla keep the same direct-PV trust shape: Common_AttackWaveActivate.sqf:6,8 sends ATTACK_WAVE_INIT; Server_AttackWave.sqf:5-6,15,23,27,36,38 trusts payload _supply / _side for modifier math and publishes details; AttackWave.sqf:19,23-25,40 trusts detail payload and debits side supply. Miksuu b8389e74, origin/perf/quick-wins 0076040f, historical AI-commander commit c20ce153, historical release commit a96fdda2 and historical upstream/AttackWave commit 994150da keep the same shape; current origin exposes no release/* or feat/ai-commander heads on 2026-06-21. P1 direct-PV authority gap, patch-ready and branch-unrescued. Treat ATTACK_WAVE_INIT as a request, re-derive requester/side/supply server-side, clamp modifier/duration, guard ATTACK_WAVE_DETAILS against forged direct payloads, propagate maintained Vanilla and smoke valid activation, forged _supply >= 70000, wrong-side payloads, duplicate active waves and JIP replay.
Direct side-supply mutation (wfbe_supply_temp_*) Branch refresh 2026-06-22: docs branch 4db90f1c is source-unchanged from 7047da5d9 / f52ccee8 for checked side-supply paths. Docs checkout, current stable origin/master@0139a346 and current Miksuu b8389e748243 all keep _currentSupply - _amount negative floors in Common_ChangeSideSupply.sqf:25 and Server_ChangeSideSupply.sqf:12,36 across Chernarus and maintained Vanilla, plus payload-side trust in the west/east temp-channel handlers. Current origin exposes no release/* heads; historical release commit a96fdda2 kept the same old shape. origin/perf/quick-wins@0076040f fixes only Chernarus arithmetic to 0. B69 origin/claude/b69@39eed5c0 fixes Chernarus server arithmetic and adds a Chernarus wfbe_supply_temp_resistance handler at Server_ChangeSideSupply.sqf:25-45, but maintained Vanilla remains old-shape and DR-44 side/channel/requester validation remains open. Patch-ready, current-source-unpatched; B69/perf are Chernarus-only candidates. Use Economy authority first cut, Resistance supply scaffold and Public variable channel index; clamp arithmetic first, then validate direct-channel shape and move spend acceptance server-side flow by flow.
Direct SEND_MESSAGE compile surface Branch refresh 2026-06-21: docs head 16247fc8f, current stable origin/master@0139a346, Miksuu upstream b8389e74 and origin/perf/quick-wins 0076040f all register the direct receiver at Client/FSM/updateclient.sqf:12, compile payload text in Client/Functions/Client_onEventHandler_SEND_MESSAGE.sqf:27, and repeat the helper compile/broadcast path in Common/Functions/Common_SendMessage.sqf:26,38 in both maintained roots. Targeted diffs 1e16527b..16247fc8f and cf2a6d6a..0139a346 do not touch the checked receiver/helper paths. Current origin exposes no release/* heads on 2026-06-21; older a96fdda2 release evidence is historical until restored. DR-46. P0 live + open: direct-channel RCE surface that is not covered by current stable's PVF dispatcher namespace lookup or any future PVF allowlist. Use Public variable channel index, Pending owner decisions and Hardening roadmap.
Side-supply reason string off-by-one Branch refresh 2026-06-22: docs branch 4db90f1c is source-unchanged from 7047da5d9 / f52ccee8 for checked reason paths. Docs checkout, current stable origin/master@0139a346, current Miksuu b8389e748243, origin/perf/quick-wins@0076040f and B69 origin/claude/b69@39eed5c0 all keep Common_ChangeSideSupply.sqf:8-14 reading _reason only when count _this > 3. Three-argument AttackWave.sqf:40 calls publish the default error reason instead of the caller's audit string; four-argument supply completion preserves its reason (supplyMissionCompleted.sqf:26 on docs/Miksuu/perf, :40 on current stable). Current origin exposes no release/* heads; historical release a96fdda2 kept the current-stable :40 supply-completion line shape. Low-risk audit/logging defect. Use Economy authority; fix with the side-supply clamp pass by reading _reason when count _this > 2 and _includeStagnation when count _this > 3.
Resource income cap and payout/display drift Branch refresh 2026-06-22: docs branch d7a30e15, Miksuu b8389e74, origin/perf/quick-wins@0076040f and historical release a96fdda2 keep the old updateresources.sqf:31 cap guard over side-supply growth (:49), team paychecks (:63) and AI-commander funds (:67). Current stable origin/master@0139a346 is partial source-present: the guard at :45 still wraps side supply (:63) and team paychecks (:77), but AI-commander over-cap income/stipend fallback is outside the guard at :102-109. Income system 4 still has the server/client display drift: server 1.5 at old refs :42-43 and current stable :56-57, while Client_GetIncome.sqf:24-28 omits that multiplier. Current origin exposes no release/* heads on 2026-06-22. Economy correctness debt with branch split. Use Economy, towns and supply and resource income tick distribution; do not reopen stable's AI-commander funds-famine fallback, but verify side supply, actual team paychecks, AI commander funds on old-shape targets and RHUD/menu display before changing income-system behavior.
Town/camp capture reward authority TownCaptured.sqf:37-81 and CampCaptured.sqf:19-40 grant funds locally and send RequestChangeScore after server-side capture broadcasts. Live mixed-authority reward path. When moving capture rewards server-side, preserve distance/assist/commander bounty semantics but derive eligible units, side and score on the server.
Auto view-distance optimizer Client/Init/Init_Client.sqf:12-13,175-176,236-240; Client/FSM/updateclient.sqf:102-107; Common/Functions/Common_AdjustViewDistance.sqf:17-69; Common/Functions/Common_AutomaticViewDistance.sqf:6-36 Working client UX/performance feature with three moving pieces. Startup defaults target FPS to 60 and auto mode off; User18 toggles auto mode while User19/User20 adjust either view distance or target FPS; the client FSM only runs the auto loop when the map is not visible, using the profile key WFBE_TARGET_FPS and a +/-4 FPS band. Historical +/-2 changelog wording is stale.
AFK enforcement policy Rsc/Parameters.hpp:44-48; Client/FSM/updateclient.sqf:28-31,117-160; Client/Init/Init_Client.sqf:256-264; Client/Module/AFKkick/monitorAFK.sqf:19-30; BattlEyeFilter/publicvariable.txt:1-2 Working but dual-path/client-local. Current parameter default is 15 minutes. The FSM path publishes kickAFK for BattlEye; the older module still runs a 30-minute AFKthresholdExceededName/failMission path. Clean up to one owner before changing policy.
Aircraft ordnance guardrails Rsc/Parameters.hpp:284-300; Common/Init/Init_Unit.sqf:118-128,207-212; Common/Functions/Common_HandleShootBombs.sqf:15-44; Common/Functions/Common_HandleIncomingMissile.sqf:9-21; Common/Functions/Common_HandleShootMissiles.sqf:95-140; Common/Init/Init_Common.sqf:10-11 Partial. Bomb distance deletion for FAB-250/Mk82 is live; incoming missile range and terrain-masking projectile deletion are live. Bomb altitude is only parameterized/commented in the handler, so do not claim active altitude enforcement. Legacy HandleATReloadVehicle / HandleBombs common compiles are commented; Common_HandleATReloadVehicle.sqf exists but is not wired, while Common_HandleBombs.sqf is absent. Treat the legacy hooks as archive/revive work, not active ordnance logic.
MASH marker relay health Docs/Miksuu/perf-shaped roots: Client/Module/Skill/Skill_Officer.sqf:8,26,29, Server/Module/MASH/MASHMarker.sqf:1,9,11, Client/Module/MASH/receiverMASHmarker.sqf:1, Client/Init/Init_Client.sqf:132; current-stable/B69 removal cue: Skill_Apply.sqf:43. See Respawn and death lifecycle. Branch-split. Docs head db3015f18ea3, Miksuu b8389e748243 and perf 0076040f8a5e keep source-supported local MASH respawn plus orphaned marker synchronization in both maintained roots. Current stable origin/master@0139a3468609, historical a96fdda28087, origin/claude/b69@0a1ccb4d05c5 and origin/claude/b69-finalpieces@80d3267c1b2b remove the maintained-root deploy/module path while retaining config/classname residues. Owner decision: revive with server-held marker registry/JIP resend on old-shape targets or finish removal/cleanup deliberately on the target branch.
Paratrooper marker registration gap Server/Support/Support_Paratroopers.sqf, Client/PVFunctions/HandleParatrooperMarkerCreation.sqf, Common/Init/Init_PublicVariables.sqf Branch-scoped / smoke pending. 2026-06-14 source check: docs checkout 1f0b9018, stable origin/master cf2a6d6a and release a96fdda2 register HandleParatrooperMarkerCreation in both maintained roots; Miksuu b8389e74 omits it in both maintained roots; perf/quick-wins 0076040f registers Chernarus only while maintained Vanilla omits it. Arma marker smoke remains pending.
Spawn/race behavior in PVF dispatchers Common/Functions/Common_SendToServer*.sqf, Server/Functions/Server_HandlePVF.sqf, Client/Functions/Client_HandlePVF.sqf Open: dispatch and execution ordering still non-deterministic for burst traffic
Area Evidence Status
Autonomous AI supply trucks AI commander autonomy audit owns the branch matrix. Docs branch docs/developer-wiki-index@ea0e0f1b still raw-spawns the commented worker in both maintained roots at Init_Server.sqf:36,382-383, and AI_UpdateSupplyTruck.sqf:17 still references missing Server/FSM/supplytruck.fsm. Current stable origin/master@0139a346 is safety-disabled instead: both maintained roots keep UpdateSupplyTruck commented at Init_Server.sqf:43, initialize wfbe_ai_supplytrucks and log-disable legacy AI supply-truck logistics at :462-463. Miksuu b8389e74 and perf/quick-wins@0076040f still raw-spawn; historical a96fdda2 matches the older safe-disable line shape, and historical c20ce153 guards only Chernarus. Current origin exposes no release/* or feat/ai-commander heads on 2026-06-22. Current stable is safety-disabled, not revived. Preserve the warning/disable shape when merging branches; a real autonomous logistics feature still needs a server-owned loop/FSM design and smoke.
AI commander automation Current stable origin/master@0139a346 has a real side-level supervisor route in both maintained roots: WFBE_SE_FNC_AI_Commander is compiled at Server/Init/Init_Server.sqf:64, spawned for present non-GUER sides at :847, sets/clears wfbe_aicom_running at AI_Commander.sqf:127,253, and calls the upgrade worker at :161. It is still partial/smoke-pending: AI commander economics, production and B69 hardening remain branch-sensitive. Upgrade debit/cost lookup is current-stable fixed, but old docs/Miksuu/perf targets still carry the old worker shape. Historical c20ce153 is commit-only feat/ai-commander evidence, while PR #43 / origin/claude/b57-soak-proposals@b8a1505f remains the current open master-target soak route for B68 attack/retreat fixes. Source-present but not release-complete. Use AI commander autonomy audit plus the branch-only feature smoke pack; do not call PR #43/B69 work master-merged or release-ready until maintained Vanilla propagation and Arma smoke are recorded.
AI commander upgrade debit/cost lookup Current-stable refresh 2026-06-22: docs branch docs/developer-wiki-index@ade4d356, Miksuu b8389e74 and perf/quick-wins 0076040f validate AI upgrade costs as [supply, funds] like the player menu (GUI_UpgradeMenu.sqf:96-97,139-140,159; Server_AI_Com_Upgrade.sqf:34-36) but still read raw AI-order cost at Server_AI_Com_Upgrade.sqf:27 and debit AI funds with _cost select 0 / side supply with _cost select 1 at :47,50. Current stable origin/master@0139a346 resolves both maintained roots: current-level cost lookup at :75, affordability gates at :89,92,97, AI funds debit _cost select 1 at :125, side supply debit _cost select 0 at :136, and opt-in funds-fallback surcharge at :131-132. Historical a96fdda2 and b061c905 fix debit order only; historical c20ce153 fixes cost/debit only in Chernarus. Current origin exposes no release/*, feat/upgrade-queue-stacking or feat/ai-commander heads. Current stable resolved / old-target patch-ready. Use AI commander autonomy and Upgrades and research: do not reopen this on current stable, port current stable's worker to docs/Miksuu/perf if those targets matter, and smoke AI upgrade affordability/debit plus funds-fallback before release wording.
Town AI vehicle despawn safety Branch check 2026-06-22: docs checkout f7aad9a8 Chernarus and maintained Vanilla still delete inactive tracked town-AI vehicles at server_town_ai.sqf:214 with alive _x plus !(isPlayer leader group _x) and no player crew check. Current stable origin/master@0139a346 keeps the same unsafe vehicle guard at :309; Miksuu b8389e748243 at :195, perf/quick-wins@0076040f at :219, historical release a96fdda2 at :200 and live origin/feat/aicom-fleet-improvements@cc5090bed4ad at :207 are also unsafe in both maintained roots. B69 origin/claude/b69@0a1ccb4d has a Chernarus candidate crew guard at :325, but maintained Vanilla remains leader-only at :319. Confirmed patch-ready bug on current stable and most checked refs; B69 is candidate evidence, not closure. Add a full player-occupancy guard before deleting wfbe_active_vehicles, preserve empty AI-only cleanup, propagate maintained Vanilla and smoke driver/gunner/cargo/turret occupancy plus empty AI vehicle cleanup. If a future branch reintroduces persistent town-defense cleanup, audit that as a separate cleanup surface.
Task system Current-stable refresh 2026-06-22: docs checkout 3406ffa0, Miksuu b8389e74 and origin/perf/quick-wins@0076040f still keep the old town TaskSystem compile and town task spawns commented in both maintained roots, with Client_TaskSystem.sqf still present (Client/Init/Init_Client.sqf:75,744 on docs; Miksuu :75,758; perf :75,759; TownCaptured.sqf:35,87). Current stable origin/master@0139a346 is different: it still leaves comment residue at Client/Init/Init_Client.sqf:94,819 and TownCaptured.sqf:36,88, but Client_TaskSystem.sqf is absent in both maintained roots. Current stable separately revives commander Objective Ping through GUI_Menu_Command.sqf:336,344 and registers SetTask at Common/Init/Init_PublicVariables.sqf:40; historical a96fdda2 keeps the helper file plus Objective Ping sends and registers SetTask at :36. Current origin exposes no release/* or task feature heads on 2026-06-22. Disabled/deferred legacy town UX. Remove/annotate stale comments or rebuild as a fresh JIP-safe task feature; do not classify current-stable Objective Ping as old town TaskSystem revival.
MASH marker receiver On docs/Miksuu/perf-shaped roots, receiverMASHmarker.sqf registers the WFBE_SE_MASH_MARKER_SENT client EH, but is referenced only by the commented compile at Client/Init/Init_Client.sqf:132 (:134 on current Miksuu). Current stable/B69-shaped maintained roots no longer carry the MASH module path. Duplicate of the row above, kept as a receiver-specific pointer for dead-code searches. Use the canonical MASH split in Respawn and death lifecycle; do not launch a fresh broad MASH discovery pass unless gameplay code changes.
Paratrooper drop markers Server/Support/Support_Paratroopers.sqf:117 sends HandleParatrooperMarkerCreation; docs/source Chernarus and Vanilla register that client PVF at Common/Init/Init_PublicVariables.sqf:39, stable/release register it at :34, and the handler file exists in checked maintained roots. Miksuu omits the registration; perf registers Chernarus only. docs/source, stable and release carry the static registration in both maintained roots; Miksuu omits it; perf is Chernarus-only; Arma smoke pending. Use Paratrooper marker revival and Source fix propagation queue. Modded folders still drift: Napf/eden/lingor register the handler but lack the handler file.
PV dispatch trust boundary Current-stable recheck 2026-06-21: origin/master@0139a346 Chernarus and maintained Vanilla both resolve _code = missionNamespace getVariable _script and spawn only CODE at Server_HandlePVF.sqf:14-15 and Client_HandlePVF.sqf:32-33. Chernarus blame is 7d60b02b4; maintained Vanilla propagation blame is 9b49883cb. Init_PublicVariables.sqf:55-61 still precompiles/registers handlers without a registered-handler allowlist or rejection log. Miksuu b8389e74 and origin/perf/quick-wins 0076040f still use Spawn (Call Compile _script) in both maintained roots; current origin exposes no release/* heads on 2026-06-21. Partial source-present on current stable; hardening still open. Dispatch-time Call Compile removal / DR-38 is present in current master, but add registered-handler allowlists/logging before treating handler-name dispatch as fully hardened. DR-55 legitimate-handler payload validation and direct PV channels remain separate. Use PVF dispatch implementation.
PV legitimate-command forgery Hilbert's network pass confirmed high-trust handlers: RequestChangeScore.sqf overwrites score from payload, RequestVehicleLock.sqf locks payload vehicles, RequestTeamUpdate.sqf mutates team behavior, and RequestUpgrade.sqf forwards to upgrade processing without visible sender/cost validation in the handler. Live-server hardening gap (High). Even after current stable's namespace lookup or a future full allowlist, validate sender, role, side, funds, ownership and object locality inside high-impact handlers.
Direct publicVariable channels outside PVF Direct PVEH/PV channels exist for attack waves, side supply, supply missions, MASH markers, HQ state, AntiStack compensation, server FPS, AFK, day/night and marker/message channels. DR-41 confirms ATTACK_WAVE_INIT is forgeable and can make side-wide unit prices free or negative from client-supplied _supply. A PVF dispatcher fix or WFBE_PVF_* whitelist does not cover these. Review each channel's sender, lifecycle and JIP semantics before calling networking hardened. See Networking and public variables, Server authority map and Attack-wave authority playbook.
BattlEye mitigation as shipped Claude DR-30 verified the repo footprint: only the AFK publicVariable rule is shipped in-tree; no broader filter/config bundle is present. Canonical evidence lives in External integrations. High live-server hardening gap. Use External integrations and backlog id battleye-hosting-hardening; do not treat BattlEye as shipped remediation until production BEpath files or a tested filter set are supplied.
ICBM/Nuke RequestSpecial authority Claude DR-27 traced the Tactical-menu ICBM path: client-side menu gates call Client/Module/Nuke/nukeincoming.sqf, which sends RequestSpecial ["ICBM", ...]; the server HandleSpecial ICBM case spawns NukeDammage from client payload without upgrade/commander/funds validation. Critical live-server hardening gap. One forged RequestSpecial PV can trigger server-applied map-wide damage. Use ICBM authority before patching or trusting this module publicly.
Non-ICBM RequestSpecial support effects GUI_Menu_Tactical.sqf:262-276,371-373,513-527 gates and debits paratroops, para-vehicle and para-ammo locally; Client/Module/UAV/uav.sqf:27-52 spawns/debits the old UAV locally; Server_HandleSpecial.sqf:43-64,147-170 trusts payload side/destination/team/object data for support spawns, supply-truck forced respawn, UAV cleanup and camp repair. High server-authority gap. Harden after or alongside the support authority pass, but keep it separate from the P0 ICBM playbook: server should re-derive requester, side, role/commander status, upgrade, funds, cooldown, target object and destination bounds before effects.
RequestSpecial upgrade-sync argument shape Support specials owns the compact branch matrix. Current-stable refresh 2026-06-21: docs-source base ad05401a3 remains source-unchanged from line-anchor checkpoint ff8dd884 for checked handler/caller/process-upgrade paths; current stable origin/master@0139a346 still keeps Server_HandleSpecial.sqf:67-73 reading _side from _args but upgrade id/level from _this, with the caller at GUI_UpgradeMenu.sqf:292 and sync variable lifecycle at Server_ProcessUpgrade.sqf:32,35,41. Miksuu b8389e74 and perf/quick-wins 0076040f still call from GUI_UpgradeMenu.sqf:241; historical release a96fdda2 calls from :254; historical upgrade-queue commit b061c905 calls from :268. Current origin exposes no release/* or feat/upgrade-queue-stacking heads on 2026-06-21. Patch-ready consistency cleanup, not a P1 authority bug. Normalize the parser to one tuple source, keep RequestUpgrade authority migration separate, propagate maintained Vanilla and smoke commander upgrade completion, non-server timer sync and malformed/short payload rejection.
RequestSpecial track-playerobject branch Server_HandleSpecial.sqf:133-145 defines a track-playerobject case, but the 2026-06-04 RequestSpecial scout found no active Chernarus RequestSpecial caller for that tag. Likely dead/undriven bookkeeping branch. Before reviving it, validate sender identity and player-object ownership; otherwise remove or comment it during RequestSpecial hardening.
Grouped base-area cleanup and dormant group monitor Server/Init/Init_Server.sqf:565 starts Server/FSM/basearea.sqf only when WFBE_C_BASE_AREA > 0; the loop prunes invalid base-area logics and delayed orphan defenses. groupsMonitor.sqf exists but the only source start point found is commented at Init_Server.sqf:567. Base-area cleanup is live only under the parameter; groupsMonitor is dormant debug tooling. If editing basearea.sqf, add _unit to the nested private list and smoke grouped-base defense cleanup.
Construction request authority DR-6 confirms construction PVFs trust client payload authority and mostly class-existence checks. Hardening gap. Use Deep-review findings DR-6 for proof, Construction and CoIn systems atlas for flow, and Server authority migration map for migration design.
Stationary defense base-area null guard and commander artillery ownership Construction and CoIn systems owns the current branch split. Docs checkout 4bd37b98 guards the base-area weapons read at Construction_StationaryDefense.sqf:12-15 and assigns manned artillery-class defense gunners to the current commander team at :91-93, matching docs-checkout group-based Tactical discovery at Common_GetTeamArtillery.sqf:10-30; the checked construction files are unchanged from the earlier 1aa178f8 anchor snapshot. Stable origin/master cf2a6d6a and release a96fdda2 instead keep marker-based ARTY discovery (Construction_StationaryDefense.sqf:133-135; Common_GetTeamArtillery.sqf:46-78) but still read _area getVariable "weapons" before a null guard at Construction_StationaryDefense.sqf:15. Miksuu b8389e74 and perf 0076040f have neither ARTY discovery shape nor the guard. Docs/source and stable/release have static commander ARTY discovery evidence by different designs; Arma smoke pending. The base-area null-guard fix is docs-checkout-only among checked refs and does not close client CoIn guard-order issues or broader construction authority hardening.
Player purchase authority GUI_Menu_BuyUnits.sqf calls local BuildUnit and deducts funds client-side; Init_PublicVariables.sqf has no RequestBuyUnit, and no Server/PVFunctions/RequestBuyUnit.sqf exists. Legacy/client-local buy path. Add server validation before adding exploit-sensitive purchases. See Factory and purchase systems atlas.
Legacy AI TL waypoint handler Server/AI/AI_TLWPHandler.sqs:9-31 exists, but the 2026-06-04 AI scout found no static Chernarus caller or compile reference. Legacy/orphan candidate. Keep it out of working-order claims unless a dynamic caller is proven; remove or document during AI order cleanup.
Factory queue counter leak Claude DR-33 confirmed Client_BuildUnit.sqf:365 can exit an empty-vehicle purchase before the later WFBE_C_QUEUE decrement at :469. Repeated empty-vehicle buys can locally soft-lock a factory category for that player. Every post-enqueue exit path must decrement both the building unitQueu token and the relevant WFBE_C_QUEUE_<type> counter.
Factory FIFO token churn Client_BuildUnit.sqf uses a random queue token and broadcasts the building queu array on each mutation. Perf/JIP hardening gap. Use Factory queue cleanup, unique queue tokens and reduced public broadcasts before expanding factory side effects.
Factory buy authority/refund model Micro-scout 2026-06-04 confirmed there is no RequestBuyUnit/RequestBuildUnit PVF in the checked player-buy paths. Current docs branch ebd86fad0 is source-unchanged from 8d611092 for checked Chernarus/Vanilla buy/build paths and still debits locally before BuildUnit; Miksuu b8389e74, perf/quick-wins 0076040f and historical QoL commit a66d4691 keep the same dead/null factory cleanup without refund. Current stable origin/master@0139a346 passes _currentCost into BuildUnit and refunds the dead/null factory abort at Client_BuildUnit.sqf:276-280 in both maintained roots; historical a96fdda2 has the same dead/null refund at :212-216. Current origin exposes no release/* or feat/buymenu-easa-qol heads. Player factory buys remain client-local even where the refund is fixed. Preserve/port the current-stable / historical a96fdda2 refund payload when targeting older roots, but decide request/acceptance/rollback semantics and server acceptance before adding expensive or exploit-sensitive factory features. See Factory and purchase systems.
Duplicate client skill init Docs checkout 719455a2 Chernarus and Vanilla have one Skill_Init.sqf call at Client/Init/Init_Client.sqf:547, followed by WFBE_SK_FNC_Apply at :571. Stable origin/master cf2a6d6a has the same one-call shape at :564 / apply :587; release a96fdda2 has :563 / apply :586 in both maintained roots. Miksuu b8389e74, perf/quick-wins 0076040f and feat/ai-commander c20ce153 still duplicate Skill_Init before apply in both maintained roots. docs/source, stable and current release carry the single-init shape; Miksuu/perf/feat-ai still duplicate; Arma smoke pending. See Client skill init idempotency.
Commander vote AI/no-commander outcome mismatch Commander vote/reassignment owns the branch scope. Current stable origin/master@0139a346 Chernarus and maintained Vanilla still count _aiVotes at Server_VoteForCommander.sqf:18,26-27, but the old tautological server comparison is fixed at :43: player commander assignment now requires _highest >= _aiVotes instead of _highest >= _aiVotes OR _highest <= _aiVotes. Chernarus blame points to cbc2294c4; maintained Vanilla propagation points to 91dc6a75. GUI_VoteMenu.sqf:88 still previews AI/no commander when no option has a strict majority or row 0 leads, so UI/server-policy smoke remains open. Miksuu b8389e74, origin/perf/quick-wins 0076040f, historical release commit a96fdda2 and historical AI-commander commit c20ce153 still keep the old `>=
Commander reassignment call shape Docs branch b44aaaf8 Chernarus and maintained Vanilla still assign _side = _this in Server_AssignNewCommander.sqf:3, while current stable origin/master@0139a346 maintained roots fix helper unpacking at :4-5. RequestNewCommander.sqf:13-14 still calls the helper and also sends new-commander-assigned; current stable helper :10 sends the same message. Current stable full modded Napf/Eden/Lingor forks still carry the old helper shape. Branch-split / current-stable partial source-present. Port the helper unpacking only on old-shape targets, then choose one notification owner, keep modded forks out of parity claims until maintained, and smoke one-message reassignment.
Commander reassignment UI identity Every checked root still stores row team indexes with lnbSetValue at GUI_Commander_VoteMenu.sqf:13,63 but resolves the selected commander by visible leader-name text at :33,37. UI correctness debt. Patch with the DR-15 reassignment flow by using row value/team identity, then smoke duplicate/similar names and mid-dialog team changes. Use Commander vote/reassignment.
Commander authority and requester validation RequestNewCommander currently uses PVF wrapper cooldown logic but does not prove sender authority before mutate-eligible command-side transitions. On current stable origin/master@0139a346, RequestNewCommander.sqf:14 and Server_AssignNewCommander.sqf:10 both contain reachable new-commander-assigned sends because the helper side argument is now fixed in maintained roots. High. Choose exactly one notification owner on current stable, patch old-shape targets separately, and keep sender/side/role checks in a follow-up owner-validation pass; do not close commander-authority until both layers are patched.
Commander vote restart/request edge GUI_Menu.sqf:75,91 sends RequestCommanderVote when wfbe_votetime <= 0; RequestCommanderVote.sqf:3-22 resets votes, spawns VoteForCommander and broadcasts commander-vote-start using the payload side/name. Useful recovery path with authority-light payload shape. Include vote restart, late join, requester identity and cooldown smoke in commander-authority work.
Commander task assignment / Objective Ping branch split Current docs head 8c3942d2 is source-unchanged from f82a9127 for checked commander-task paths; docs, Miksuu b8389e74, perf/quick-wins 0076040f and feat/ai-commander c20ce153 still build task data but leave maintained-root SetTask sends commented at GUI_Menu_Command.sqf:335,337,343 while registering SetTask (Common/Init/Init_PublicVariables.sqf:33 on docs). Stable origin/master cf2a6d6a and release a96fdda2 send targeted Objective Ping tasks at GUI_Menu_Command.sqf:336,344 and register SetTask at Common/Init/Init_PublicVariables.sqf:36 in both maintained roots. Old town TaskSystem remains commented everywhere checked. Branch-present/smoke-pending on stable/release; still partial on docs/Miksuu/perf/feat-ai. Before promotion, smoke commander menu tab, selected-team vs all-player-led targets, receiving-client task creation/completion timer, JIP, side filtering and spam behavior.
Supply mission cooldown casing DR-18 remains open in docs/source 15563691, Miksuu b8389e74 and perf/quick-wins 0076040f: Init_Town.sqf:35 seeds lowercase lastSupplyMissionRun, while isSupplyMissionActiveInTown.sqf:8 reads LastSupplyMissionRun. Current stable origin/master@0139a346 seeds LastSupplyMissionRun at Common/Init/Init_Town.sqf:35 and reads it with default 0 at isSupplyMissionActiveInTown.sqf:8 in both maintained roots. Historical release anchor a96fdda2 has the same fixed shape; current origin exposes no live release/* head. Branch-split correctness bug. Port or recreate the casing/default fix where targeting docs/Miksuu/perf; keep server-owned start/reward hardening separate. Use Supply mission architecture and Supply mission authority cleanup.
Supply mission reward authority Client supply mission start sets truck SupplyFromTown and SupplyAmount; server completion trusts those truck variables. Hardening gap. Recompute reward/cooldown server-side from trusted town/truck state.
Town mortar scaffold Server_ManageTownDefenses.sqf:31-32 has a mortar-management hook shape, while Server_SpawnTownMortars.sqf:19-21 reads the wrong local variable shape and no live town init setter for wfbe_town_mortars was found in the maintained mission scan. Broken/dormant scaffold. Keep it out of working town-defense claims; revive only with explicit town anchor setup, variable fix and Arma smoke, or remove/archive it with other dead defense hooks.
Supply player-object list indexing Source Chernarus and maintained Vanilla initialize the WFBE_SE_PLAYERLIST update index before the player-list loop (playerObjectsList.sqf:17-29), but reconnect/supply smoke and stale disconnect-row pruning remain open. docs/source propagated; smoke pending. Use Player join/disconnect lifecycle, Source fix propagation queue and Testing workflow.
Supply mission player-facing reward copy Client/Module/supplyMission/supplyMissionStart.sqf:22-34 computes cargo as town supplyValue * WFBE_C_ECONOMY_SUPPLY_MISSION_MULTIPLIER * supplyUpgradeModifier; Client/Module/supplyMission/supplyMissionCompletedMessage.sqf:8,13-14 grants raw _supplyAmount. stringtable.xml:188-193 still says players receive 4 x the actual value, and WFBE_C_PLAYERS_SUPPLY_TRUCKS_DELIVERY_FUNDS_COEF = 4 at Init_CommonConstants.sqf:268 has no live consumer in this flow. Player-facing docs debt. Fix copy when supply reward authority is redesigned, or update stringtable immediately to match the live formula so players are not balancing around dead text.
Supply mission command-center scan Branch check 2026-06-22: docs/source 15563691 Chernarus and maintained Vanilla use the truck-only typed terminal scan at supplyMissionStarted.sqf:25,28, with the nearby-player scan still broad at :44. Current stable origin/master@0139a346 uses the heli-aware typed terminal scan with _byHeli at :7, terminal guard at :55, typed 400 m heli / 80 m truck nearestObjects at :61, and the nearby-player scan still broad at :83. Historical release anchors a96fdda2 and 7ff18c49 carry the heli-aware typed shape, but current origin exposes no live release/* or supply feature head. Miksuu b8389e74 and perf/quick-wins 0076040f still enumerate nearestObjects [..., [], 80] at :28 and post-filter Base_WarfareBUAVterminal at :25. Branch-split, smoke pending. Docs/source and current stable carry typed command-center scans in both maintained roots; Miksuu/perf do not; release-line evidence is historical until a live head returns. Truck/heli command-center delivery and unrelated-object non-completion still need Arma smoke on the target branch. See Supply mission architecture and Supply mission scan narrowing.
Upgrade request authority RequestUpgrade accepts side/id/level from clients after local UI checks, then Server_ProcessUpgrade applies progress/state transitions. High. Local checks are partial; server-side side, owner, dependency and idempotency checks are still needed before trust assumptions are raised.
Support/repair/rearm reward authority GUI_Menu_Service, GUI_Menu_EASA, GUI_BuyGearMenu, bounty handlers and WASP repair actions still mutate/announce client-funds paths in places; HQ/camp/town reward emitters are mixed. Service/EASA refresh 2026-06-22: docs branch 9b3fc38e remains old-shape for checked service/EASA paths, current stable origin/master@0139a346 only partially guards service rearm/refuel, current Miksuu upstream b8389e748243 keeps the old direct service debit shape, and B69 finalpieces fixes exact-funds EASA only in Chernarus. Medium. This is a shared non-isolated economy lane and should follow the upgrade/construction authority design rather than isolated local guards only. Use Service menu affordability guards for local service/EASA correctness evidence.
Victory/endgame winner inversion and double-fire 2026-06-21 current-stable refresh: docs head d30d23466 is source-unchanged from a0a86da2 / 2f2132f8 for checked victory/endgame paths. Docs, Miksuu b8389e74, origin/perf/quick-wins 0076040f and historical release commit a96fdda2 keep the older opposite-side logger block in both maintained roots (server_victory_threeway.sqf:23-41), which logs all-towns wins as the loser. Current stable origin/master@0139a346 changed both maintained roots to add the HQ nil/null skip at :18-22, keep the mixed condition at :29, write WF_Winner at :37, set WFBE_GameOver at :39, write WASPSTAT _x at :41-46 and call LogGameEnd with [_x] at :49; that still logs HQ/factory eliminations as the loser and still lacks a full-condition guard/side-loop exit. Client_EndGame.sqf:5-13 still inverts the payload and GUI_EndOfGameStats.sqf:6-8 still lacks a GUER label on current stable. origin/claude/b57-soak-proposals@b8a1505f has Chernarus-only guard/client-label edits, not maintained Vanilla parity or explicit winner/loser computation. Correctness bug, current-stable-unpatched. Compute explicit winner/loser sides per branch, guard the combined condition with !WFBE_GameOver, exit after one accepted endgame path, align client payload semantics/GUER label/WASPSTAT/logger, then propagate maintained Vanilla and smoke HQ elimination, all-towns victory, same-tick mutual elimination and AntiStack tails. Route implementation through Victory/endgame atlas, Deep-review findings DR-11/DR-36, the Hardening roadmap and Source fix propagation queue.
Threeway victory mode 2026-06-21 branch check: docs head d30d23466, current stable origin/master@0139a346, Miksuu b8389e74, origin/perf/quick-wins 0076040f and historical release commit a96fdda2 still read WFBE_C_VICTORY_THREEWAY and run detection only when _victory == 0 in both maintained roots; line refs drift (Init_CommonConstants.sqf:401-402 docs/Miksuu/perf, current stable :631-632, historical release :417-418, server_victory_threeway.sqf:3,11). Current origin exposes no release/* heads. origin/claude/b57-soak-proposals@b8a1505f removes the gate only in Chernarus and explicitly does not add new victory modes. Broken/abandoned mode on current stable until end conditions are implemented for non-default victory modes, or explicitly guarded/documented as unsupported. Keep implementation detail on Victory/endgame atlas.
Resistance side supply updates Branch refresh 2026-06-22: docs HEAD@56370c44 is source-unchanged from 4db90f1c for checked mission paths. Docs/current Miksuu b8389e748243/perf 0076040f/historical a96fdda2 publish generic wfbe_supply_temp_<side> at Common_ChangeSideSupply.sqf:28,30, but have no checked maintained-root WFBE_L_GUE owner logic, no wfbe_supply_temp_resistance handler and resistance reads still hit REQUEST_SUPPLY_VALUE / waitUntil at Common_GetSideSupply.sqf:40-43. Current stable origin/master@0139a346 adds WFBE_L_GUE owner logic at Chernarus mission.sqm:4928,4931 / Vanilla :4198,4201 and funds-only 0 reads at Common_GetSideSupply.sqf:36-40, but Server_ChangeSideSupply.sqf:1,25 remains west/east only. B69 origin/claude/b69@39eed5c0 adds Chernarus wfbe_supply_temp_resistance at Server_ChangeSideSupply.sqf:25-45; B69 Vanilla remains west/east only. Partially wired only on B69 Chernarus; current stable has safe owner/read behavior but no resistance write handler. Use Resistance supply scaffold and Economy authority before changing code; decide funds-only 0 versus live resistance supply state, then validate west/east/resistance channels plus requester authority.
Hosted server FPS loops Branch check 2026-06-14: docs checkout db7667c9 Chernarus and maintained Vanilla keep the two-publisher guard shape (serverFpsGUI.sqf:1, monitorServerFPS.sqf:1; starts at Init_Server.sqf:578,595) and those FPS files are unchanged from the server-runtime 92c5cf05 anchor. Stable origin/master cf2a6d6a and release a96fdda2 both use one guarded serverFpsGUI.sqf:4 publisher, start it at stable Init_Server.sqf:580 / release :579, document monitor removal at stable :596-598 / release :595-597, and have no maintained-root Server/Module/serverFPS/monitorServerFPS.sqf file. Miksuu b8389e74 and perf/quick-wins 0076040f still keep the two old unguarded publisher loops in both checked roots. docs/source, stable and release are guarded but use different source shapes; Miksuu/perf remain old-loop-shaped. Arma smoke pending. Use Hosted server FPS loop sleep and Server gameplay runtime atlas.
Old map blink loop Current-stable refresh 2026-06-22: docs checkout 3406ffa0 still has old plural blink/add-track comments at Client/Init/Init_Client.sqf:138,140,782 in both maintained roots, while live singular Client_BlinkMapIcon compiles at :139. Miksuu b8389e74 keeps the old comments with line drift at :140,142,796; origin/perf/quick-wins@0076040f keeps docs-shaped lines. Current stable origin/master@0139a346 and historical a96fdda2 no longer carry the old plural/AddUnitToTrack comments in checked maintained roots and keep only the live singular compile at stable :163 / historical :143. Branch-split legacy residue. Clean old comments only on old-shape targets; avoid resurrecting the full-map loop without rebuilding missing files and doing a performance review. Current work should use the guarded per-unit blink path.
Supply mission dead twin compile Docs/source 15563691, Miksuu b8389e74 and perf/quick-wins 0076040f still compile WFBE_SE_FNC_SupplyMissionActive at Server/Init/Init_Server.sqf:81 while the live PVEH is registered by supplyMissionStarted.sqf. Current stable origin/master@0139a346 comments the removed compile at Init_Server.sqf:97 and has no maintained-root supplyMissionActive.sqf / checkCCProximity.sqf file. Historical release anchor a96fdda2 comments the removed compile at Init_Server.sqf:81 and also omits those files; current origin exposes no live release/* head. Branch-split dead-code cleanup. Do not treat the second compile as proof of an autonomous supply-mission state machine; route any remaining cleanup through Supply mission architecture and the authority/cooldown lanes.
Server map blinking units Current-stable refresh 2026-06-22: docs checkout 3406ffa0 and Miksuu b8389e74 still comment the missing Server_MapBlinkingUnits.sqf exec at Server/Init/Init_Server.sqf:593 in both maintained roots; perf keeps it at Chernarus :588 and Vanilla :593. Current stable origin/master@0139a346 and historical a96fdda2 have no checked maintained-root Server_MapBlinkingUnits.sqf file and no old commented exec. Disabled/legacy on old-shape targets; no current-stable cleanup remains for this exact comment unless marker authority is redesigned.
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.
Static-defense HC update-back DR-42 verified Client_DelegateAIStaticDefence.sqf:28 comments out the update-delegation-static_defence send-back, unlike town-AI delegation (Client_DelegateTownAI.sqf:35) which reports vehicles back to Server_HandleSpecial.sqf. Follow-up source check: Common_CreateUnitForStaticDefence.sqf:69 returns only [_teams], and Server_HandleSpecial.sqf:86-96 has only the town-vehicle update-town-delegation receiver. HC upstream history also shows older static-defense HC routing churn in 6b90c872. Partial headless feature. HC-created static-defense units are not recorded by the server for cleanup/accounting/re-delegation. Do not merely uncomment the old call; restore tracking only with a deliberate static-defense payload and receiver, or explicitly accept/remove the one-way behavior. Use HC delegation/failover before patching.
HC registration owner-id miss Headless/Init/Init_HC.sqf:11-15 sends one connected-hc; Server_HandleSpecial.sqf:120-130 only appends the HC group when owner _hc != 0 and otherwise logs a warning with no retry. High reliability gap for public HC timing. Add retry/delayed registration or server reconciliation before relying on HC mode for runtime load.
HC registration duplicate risk Server_HandleSpecial.sqf:127-128 appends group _hc to WFBE_HEADLESSCLIENTS_ID without a visible dedupe guard; disconnect cleanup at Server_OnPlayerDisconnected.sqf:22-28 removes one stored group reference. HC idempotency debt. Add an explicit dedupe guard before retry/reconnect work, otherwise the retry fix can create duplicate delegation candidates.
Client-FPS delegation trust updateavailableactions.fsm:121-125 sends ["update-clientfps", getPlayerUID(player), avgFps]; Server_HandleSpecial.sqf:75-83 trusts the UID/FPS payload, and Server_FNC_Delegation.sqf:153-158 uses stored values to pick delegators. Mode 1 authority-light. Validate sender/UID/rate or keep this mode out of hostile public deployments.
Server init duplicate binds DR-43b is branch-split as of 2026-06-14: current docs head a0a86da2 is source-unchanged from 2f2132f8 for checked server-init paths, and docs/Miksuu b8389e74 keep live duplicates in both maintained roots; stable origin/master cf2a6d6a and release a96fdda2 keep one live bind per function in both maintained roots; perf 0076040f fixes Chernarus while maintained Vanilla remains old-shape. Commented AFK/FPS/MASH remnants are separate cleanup artifacts. Low-risk cleanup where still present. Use Server init bind cleanup; coordinate LogGameEnd with DR-13/DR-36 and do not re-enable commented AFK/FPS/MASH remnants as part of this lane.
MASH marker duplicate compile One MASH marker compile is active and a later duplicate is commented. Cleanup artifact covered by Server init bind cleanup and the MASH owner route in Respawn and death lifecycle; do not re-enable both.
Volumetric clouds WFBE_C_ENVIRONMENT_WEATHER_VOLUMETRIC is exposed in Rsc/Parameters.hpp:210-214, but Common/Init/Init_CommonConstants.sqf:212 and Client/Init/Init_Client.sqf:218 both force it to 0. Intentional locked-off optimization. Do not describe the lobby entry as a live weather choice until forced assignments are removed and smoke-tested.
IR-smoke parameter/runtime name split Rsc/Parameters.hpp:393-397 declares WFBE_C_MODULE_WFBE_IRS, while constants/init/upgrade gates read WFBE_C_MODULE_WFBE_IRSMOKE (Init_CommonConstants.sqf:238, Init_Common.sqf:320, Upgrades_CO_US.sqf:24-25). Config drift. Decide one variable name or add an explicit alias after parameter import; smoke lobby off/on behavior and IR-smoke upgrade availability.
Hidden upgrade-clearance switch WFBE_C_GAMEPLAY_UPGRADES_CLEARANCE is commented out in Rsc/Parameters.hpp:351-356, but constants/server init and boot fallback still consume/set it (Init_CommonConstants.sqf:225, Server/Init/Init_Server.sqf:333-349, initJIPCompatible.sqf:148,152). Operator-facing drift. Treat as internal runtime state unless owner deliberately restores it as a lobby parameter.
Orphan-looking BIS High Command parameter WFBE_C_MODULE_BIS_HC exists in Rsc/Parameters.hpp:381-385, but headless delegation uses WFBE_C_AI_DELEGATION (initJIPCompatible.sqf:151-170, Init_Server.sqf:109, server_town_ai.sqf:17), and no static Chernarus consumer was found. UI/config cleanup candidate. Do not treat it as headless-client enablement; either wire a real Arma High Command feature or hide/remove the parameter.
Modded map generator path SqfFileGenerator.cs:127-135 writes source Chernarus and maintained Takistan/Vanilla, but the modded-terrain write call is commented and ZipManager.cs:15-17 packages only Missions plus Missions_Vanilla. Verify before assuming modded mission regeneration is complete; current release output is source plus generated Vanilla/Takistan unless modded generation/packaging is deliberately re-enabled and validated.
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 TODOs about securing vanilla/removing unused code, refreshing targets, vehicle target content and vehicle/backpack templates. Partial UI cleanup. See Gear, loadout and EASA atlas.
Gear profile template save/import filtering Gear template profile filter owns the branch matrix. Current docs head 72b5f0de98f9 is source-unchanged from the 2026-06-21 43c3ba05 proof for checked Chernarus and maintained Vanilla template paths; docs/source anchors remain Client_UI_Gear_SaveTemplateProfile.sqf:33,52,75 undefined _u_upgrade plus Init_ProfileGear.sqf:17,25 six-field import guard/index-6 read. Current stable origin/master@0139a3468609 fixes the save-filter comparisons in both maintained roots at Client_UI_Gear_SaveTemplateProfile.sqf:34,57,82, but keeps the six-field import guard. Current Miksuu master@b8389e748243, perf 0076040f8a5e, historical release a96fdda28087 and historical EASA QoL a66d46912e2a keep the old save-filter shape; current origin exposes no live release/gear/template rescue head. Branch-split profile-template persistence guard. Patch docs/source or old-shape refs before trusting saved templates to enforce upgrade gates; current stable still needs the import guard/default before the profile-template lane is complete.
Vehicle/backpack cargo equip loop bounds Vehicle cargo equip loop bounds owns the branch split. Corrected 2026-06-22 after direct upstream verification: docs branch docs/developer-wiki-index@b2544207, current Miksuu master@b8389e748243 and historical EASA QoL a66d4691 still carry inclusive loops at Common_EquipVehicle.sqf:27,33,39 and Common_EquipBackpack.sqf:35,41 in both maintained roots. Current stable origin/master@0139a346 and historical release a96fdda2 fix all five loops in both maintained roots; origin/perf/quick-wins@0076040f fixes Chernarus only. Current origin exposes no live release/* or feat/buymenu-easa-qol heads; local d9506078 is origin/claude/* branch evidence, not current Miksuu upstream. Confirmed reliability bug where still old-shape. Do not reopen current stable; preserve/port the count(_items)-1 fix for docs/current-Miksuu/EASA/perf-Vanilla targets that still carry inclusive loops, then smoke vehicle/backpack cargo without claiming economy authority hardening.
Gear template creation gate needs owner decision Gear template profile filter owns the creation/display/save gate matrix. Current docs head 72b5f0de98f9 is source-unchanged from 43c3ba05 for checked template paths. All checked refs keep the AddTemplate Barracks-or-Gear creation gate at Client_UI_Gear_AddTemplate.sqf:136 and Gear-only FillTemplates display at Client_UI_Gear_FillTemplates.sqf:17; current stable fixes only the save-filter _u_upgrade comparison, not this policy split. Owner-decision consistency debt. Decide Barracks/Gear semantics before changing AddTemplate, FillTemplates and SaveTemplateProfile policy together.
Gear/EASA/service purchase authority GUI_BuyGearMenu.sqf applies gear and deducts funds client-side. Current docs head 9b3fc38e is source-unchanged from 8b71e2a1 for checked service/EASA paths; current stable origin/master@0139a346 partially guards service rearm/refuel but leaves repair/heal and EASA exact-funds/client-debit open; current Miksuu upstream b8389e748243 keeps the old direct service debit shape. B69 finalpieces fixes exact-funds EASA only in Chernarus; maintained Vanilla remains strict >. Service menu affordability guards owns the service/EASA branch details and BuyMenu EASA QoL branch audit owns the historical UI-only QoL commit. Client-authoritative legacy path. DR-28 completes the economy authority class: build, buy, sell, supply, upgrade, ICBM and gear/service are all client-authoritative; use the owner pages for patch shape and smoke scope before code work.
Generated EASA/balance output LoadoutManager writes Client/Module/EASA/EASA_Init.sqf and Common/Functions/Common_BalanceInit.sqf; Common_BalanceInit.sqf exits on server while server buy code still calls BalanceInit. Generated/locality risk. Change C# data first, inspect generated diffs, and test spawn versus rearm behavior separately.
Discord sample/config hygiene DiscordBot/preferences_sample.json contains concrete sample IDs and a production-style DataSourcePath; GameData.cs:36-37 uses Preferences.Instance.DataSourcePath or C:\a2waspwarfare\Data, while DiscordBot/FileConfiguration.cs:9-42 is a secondary config helper. Preferences.cs:24-30 also reads/deserializes preferences.json without fail-fast null/parse handling before later command/status code assumes a non-null Preferences.Instance. Governance and reliability cleanup. Replace real-looking sample IDs with placeholders, document one intended config source and add explicit config preflight/fail-fast behavior. No token is committed.
DiscordBot JSON deserialization Claude DR-31 verified DiscordBot/src/ExtensionData/GameData/GameData.cs reads database.json with Newtonsoft TypeNameHandling.All on a 60-second status timer, at startup and from a command path. High local-write-gated RCE risk. Use TypeNameHandling.None for the flat GameData DTO and remove the dead .Auto deserialization helper. Secret hygiene and command auth are otherwise documented as good.
In-repo stats extension vs AntiStack DB extension a2waspwarfare_Extension only implements GLOBALGAMESTATS; AntiStack calls a separate A2WaspDatabase DLL that is absent from the repo. WFBE_C_ANTISTACK_ENABLED defaults on via the lobby/fallback constants, so the deployment choice matters before public hosting. Claude DR-29 verified GLOBALGAMESTATS is not an SQF RCE path today because output is discarded, but it has dormant deserialization and async-write risks. Deployment dependency split. Do not assume building Extension satisfies AntiStack. Either confirm/install A2WaspDatabase and harden return handling, or operate/default AntiStack disabled until the dependency is real. Add extension presence detection/circuit breaker before public deployment; remove/harden the dead TypeNameHandling.Auto load path and fix async void file writes before treating the extension as robust persistence.
WASP HQ recovery locality WASP/actions/Action_RepairMHQDepot.sqf performs funds/HQ/town-SV effects largely client-side before server repair signaling. Authority-light legacy action. Harden server-side before expanding HQ recovery, town-SV reset or commander-spend behavior.
Missing CI/reference validation Only .github/FUNDING.yml exists; no build/reference/generated-drift checks were found. Missing tooling. Add .NET builds, generated-mission drift, SQF reference scans and wiki JSON/JSONL validation when project automation is introduced.
Modded mission conflict markers `rg -l "<<<<<<< =======
Stale old upgrade dialog RscMenu_Upgrade points to missing Client/GUI/GUI_Menu_Upgrade.sqf; the live main menu opens WFBE_UpgradeMenu / GUI_UpgradeMenu.sqf instead. Branch check 2026-06-14: docs checkout d4cfef80 keeps the stale class in both maintained roots at Rsc/Dialogs.hpp:2425,2428; Miksuu b8389e74 and perf/quick-wins 0076040f keep it at :2435,:2438; stable origin/master cf2a6d6a, release a96fdda2 and origin/feat/upgrade-queue-stacking b061c905 have no checked RscMenu_Upgrade / GUI_Menu_Upgrade.sqf hits in maintained roots. Confirmed branch-split stale UI path. Do not revive by recreating the old missing controller or art. Preferred code-owner action for roots that still carry it is consistent removal or explicit aliasing across maintained roots, followed by live upgrade-menu smoke. Canonical lane: UI resource parity cleanup.
Generated version.sqf boot dependency Rechecked 2026-06-14 on docs checkout 85679dba: description.ext:39 and initJIPCompatible.sqf:4 both include version.sqf, but source Chernarus and maintained Vanilla Takistan have no present or tracked generated version.sqf; .gitignore:1,23 ignores those paths. Tools/LoadoutManager/Data/Terrains/BaseTerrain.cs:99-102,346-367 writes version outputs, and FileManager.cs:92-100 treats them as generated/special terrain files. Checked refs 85679dba, stable cf2a6d6a, Miksuu b8389e74, perf 0076040f and release a96fdda2 do not track Chernarus/Vanilla version.sqf. Generated-output/release hazard. Verify the target mission root has the right generated version.sqf before pack/test claims, especially clean checkouts, generated Vanilla and modded/stub terrain folders.
Economy dialog missing controls Branch check 2026-06-14: docs checkout d2a3f995 still writes 23004/23005/23006 at GUI_Menu_Economy.sqf:7-8 in both maintained roots, while RscMenu_Economy declares 23002, 23003 and 23008 at Rsc/Dialogs.hpp:3327,3339,3346. Miksuu b8389e74 and perf 0076040f keep the same stale writes. Stable cf2a6d6a and release a96fdda2 rewrite both maintained-root Economy controllers around dashboard 23020 at GUI_Menu_Economy.sqf:25 and declare 23020 at stable Rsc/Dialogs.hpp:3031 / release :3006. Docs-ready UI parity cleanup for docs/Miksuu/perf targets; preserve stable/release repair when merging. Use UI resource parity cleanup, then smoke Economy disabled state, income controls, sell mode and supply-truck respawn.
Duplicate UI resource IDDs Branch check 2026-06-14: current docs checkout b5219d47 keeps the 2fef1e3d UI resource line shape, and docs/Miksuu b8389e74/perf 0076040f still keep EASA/Economy both on dialog idd = 23000 in both maintained roots. Stable cf2a6d6a and release a96fdda2 move EASA to 24000 and keep Economy on 23000 in both maintained roots. RscOverlay/OptionsAvailable still both use title idd = 10200 everywhere checked; no checked maintained root has a findDisplay 23000/10200 caller. Docs/Miksuu/perf still need UI parity cleanup or a formal waiver for EASA/Economy; every checked target still needs title-IDD cleanup or a waiver. Start at UI resource parity cleanup, then use UI IDD collision repair; smoke EASA, Economy, RHUD/FPS HUD, action icons and endgame stats after any IDD/display-handle cleanup.
RHUD/endgame shared title display handle OptionsAvailable and EndOfGameStats both use GUI_SetCurrentCutDisplay.sqf / GUI_ClearCurrentCutDisplay.sqf and therefore the same uiNamespace["currentCutDisplay"]; docs/Miksuu/perf use Titles.hpp:170-171,539-540, Client_UpdateRHUD.sqf:89-92,183-190, updateavailableactions.fsm:225-230 and GUI_EndOfGameStats.sqf:34-44,86-93; stable/release line-drift to Titles.hpp:174-175,587-588 and Client_UpdateRHUD.sqf:89-92,251-258. All checked refs keep the shared-handle shape in both maintained roots. Patch-ready UI lifecycle bug. Split display variables or gate RHUD/action-icon recreation during endgame, separate from duplicate-IDD cleanup; smoke RHUD/FPS, action icons and endgame stat bars together. Canonical lane: UI IDD collision repair.
Modded missing camp helper file Napf, Eden and Lingor Common/Init/Init_Common.sqf:52-53,127-128 compile Common/Functions/Common_GetTotalCamps.sqf, but only source Chernarus and maintained Vanilla currently track that file. Additional modded-runnability blocker. Do not call those forks runnable until missing helpers, generated inputs and conflict markers are resolved or the forks are regenerated/retired.
Camp flag texture drift Towns/camps/capture owns the refreshed branch split. 2026-06-22 check: docs branch docs/developer-wiki-index@28a7d9c5 still writes captured camp sideID to _newSID at server_town_camp.sqf:132 but flags old _side at :135; Miksuu b8389e74 still flags old _side; perf/quick-wins@0076040f fixes Chernarus only; and current stable origin/master@0139a346, historical a96fdda2, B69 origin/claude/b69@0a1ccb4d plus origin/feat/naval-hvt-objectives@2e1c5931 fix independent capture in both maintained roots. repair-camp still changes side/broadcasts without flag refresh in every checked ref; current-stable line drift is Server_HandleSpecial.sqf:468,471. Branch-split visual/world-state debt. Preserve current-stable/release/B69/naval independent-capture fixes when merging; patch old-owner targets where still relevant; add repair-side flag refresh in all code-owner targets; smoke independent capture and camp repair.
Camp count helper fallback Branch check refreshed 2026-06-22: docs branch docs/developer-wiki-index@ade4d356, current stable origin/master@0139a346, Miksuu b8389e74, perf/quick-wins@0076040f, historical release a96fdda2 and active B69 branch origin/claude/b69@0a1ccb4d all keep Common_GetTotalCamps.sqf:10 and Common_GetTotalCampsOnSide.sqf:16 returning 1 for zero-camp towns in both maintained roots. Affected caller families are capture mode 2/capture-rate math, threeway respawn and depot infantry buys; exact line drift now lives only on Towns, camps and capture atlas. Patch-ready caller-semantics debt. Use Towns, camps and capture atlas; split real-count from safe-denominator behavior or add caller-specific zero-camp guards, then smoke capture mode 2, threeway respawn and depot infantry buys on 0/partial/all-camp towns.
Buy-menu price/key alignment Factory and purchase systems atlas owns the refreshed branch/root matrix. Docs checkout 8d611092, Miksuu b8389e74 and perf/quick-wins 0076040f keep selected-detail price drift, no level-0 UNIT_COST_MODIFIER reset and the uppercase/lowercase driver-default profile key split. Current stable origin/master@0139a346 and historical a96fdda2 fix selected-detail display in both maintained roots and mirror both driver-default keys, but still do not reset UNIT_COST_MODIFIER to 1 for level 0. Historical QoL commit a66d4691 fixes selected-detail display in Chernarus only; current origin exposes no feat/buymenu-easa-qol head. UI/economy correctness debt, partially fixed on current stable / historical release evidence. Reset/localize the modifier path, decide whether dual-key mirroring is the intended driver-default compatibility policy, then smoke list/detail/charge, funds guard, unit-cost levels 0/1/2, crew toggles, max-out and reset.
Patrols v2 current-master route Current stable origin/master@0139a346 Chernarus and maintained Vanilla retire the old server_town_ai patrol launch (server_town_ai.sqf:72,327), add the side-upgrade driver (server_side_patrols.sqf:12,19,48,67,72), compile and dispatch Common_RunSidePatrol.sqf:54,82,87,119,148,245,264, maintain side slots/markers through Server_HandleSpecial.sqf:345-380 and Client/FSM/updatepatrolmarkers.sqf:3,19, and use server_patrols.sqf:31 && in both roots. The old 89ae9dad DR-57/AI1 evidence is historical branch evidence now. Source-present / smoke-pending AI lifecycle feature. Use Towns/camps/capture; smoke Patrols upgrade levels 1/2/3, level-4 convoy/camp-sweep hooks, HC delegate-sidepatrol, friendly marker audience, patrol death, side-slot/cooldown release and Buy Units/RHUD AI-cap text.
Hardcoded live UI help/status text GUI_Menu_BuyUnits.sqf:443-457 hardcodes English vehicle-help hints, and GUI_Menu_Tactical.sqf:604-605 hardcodes artillery ammo request status. Localization/UI polish debt. Move to stringtable keys when polishing Buy Units/Tactical; verify translated clients and no missing-key regressions.
Vote/help/WASP/main-menu UI edge cases Client UI systems atlas owns the branch/root matrix for the vote refresh loops (GUI_VoteMenu.sqf:29,49,61; GUI_Commander_VoteMenu.sqf:58), vote row-color offset (GUI_VoteMenu.sqf:80,82), help load/unload namespace mismatch (Rsc/Dialogs.hpp:3502-3503; release line drift noted there) and orphaned GPS zoom router (GUI_Menu.sqf:202,206). WASP display-54 input-lock polling is tracked separately in the WASP marker wait route; its 2026-06-21 current-head refresh shows stable origin/master@0139a346 still needs the tiny wait/backoff patch in both maintained roots (global_marking_monitor.sqf:57,62,65,69-70,81; launch Init_Client.sqf:309). UI correctness and UX debt, patch-ready but source-unpatched. Fix vote loops plus row coloring, clean the help namespace/onUnload contract, decide remove-vs-revive for GPS 17/18, propagate Vanilla and smoke vote refresh/list coloring, help open/close and main-menu HUD/GPS behavior; smoke WASP marker dialog through its own lane.
Destroyed-factory refund branch split Branch refresh 2026-06-21: current docs branch ebd86fad0 is source-unchanged from 8d611092 for checked buy/build paths and still has local queue increment/debit plus Client_BuildUnit.sqf:211-214 dead/null factory cleanup without refund. Miksuu b8389e74, perf/quick-wins 0076040f and historical QoL commit a66d4691 remain old-shape. Current stable origin/master@0139a346 passes _currentCost into BuildUnit and refunds the real dead/null factory abort at Client_BuildUnit.sqf:276-280 in both maintained roots; historical a96fdda2 has the same dead/null refund at :212-216. Intermediate historical 7ff18c49 only refunded the empty/crewless branch and is superseded. Current origin exposes no release/* or feat/buymenu-easa-qol heads. Source-present on current stable / historical a96fdda2, patch-ready for older roots if they remain targets. Preserve the dead/null refund payload when merging, keep the empty/crewless spawned-vehicle counter cleanup separate, and smoke factory death, buyer disconnect, empty/crewless vehicle abort and normal queue completion. See Factory and purchase systems.
Latent server buy worker is not player-buy parity Stable master compiles AIBuyUnit = Server_BuyUnit.sqf (Init_Server.sqf:10) but has no static caller. Player buys use client WFBE_C_QUEUE_* / unitQueu, while Server_BuyUnit.sqf uses team wfbe_queue and always proceeds into server crew creation (Server_BuyUnit.sqf:92-214). Factory/AI production design debt. If AIBuyUnit is revived, document the intended AI production semantics and queue model instead of treating it as a server replacement for player buying.
Generated version.sqf map/profile contract description.ext:39, Rsc/Header.hpp:5,9,21 and initJIPCompatible.sqf:4,31,111-113 make generated version.sqf drive header metadata and runtime Chernarus/non-Chernarus flags. IS_NAVAL_MAP also gates boat content through IS_naval_map. Generated-output/release hazard. Use Mission config/version include graph; verify target root flags before packaging and do not confuse Missions_Vanilla with the VANILLA macro.
Visible parameter runtime-consumer drift Branch correction 2026-06-22: docs branch origin/docs/developer-wiki-index@ac932fbe, current Miksuu master@b8389e748243, origin/perf/quick-wins@0076040f and historical release a96fdda2 still expose/default WFBE_C_AI_MAX without an active maintained-root runtime reader found, and keep WFBE_C_UNITS_CLEAN_TIMEOUT comment-only in Common_TrashObject.sqf:20. Current stable origin/master@0139a346 is source-present in both maintained roots: AI_Commander_Produce.sqf:89 reads WFBE_C_AI_MAX, and Common_TrashObject.sqf:21 reads WFBE_C_UNITS_CLEAN_TIMEOUT for non-man wreck cleanup while bodies use WFBE_C_UNITS_BODIES_TIMEOUT. Player follower caps still use WFBE_C_PLAYERS_AI_MAX; local d9506078 is not current Miksuu upstream. Branch-split. Use Mission parameters and Dead/stale code register; do not route current stable as no-op/comment-only, but current Miksuu and other old-shape refs still need port/hide/label decisions plus host parameter, AI commander production, player cap UI/RHUD, body/wreck and empty-vehicle cleanup smoke.
Auto-wall construction toggle is global Construction and CoIn systems owns the refreshed branch matrix. 2026-06-22 source correction: docs branch origin/docs/developer-wiki-index@89aadf8c, current Miksuu master@b8389e748243 and origin/perf/quick-wins@0076040f keep RequestAutoWallConstructinChange.sqf:3-7 writing one global isAutoWallConstructingEnabled, initialize it false at Init_Common.sqf:201, and consume it without structure exclusions at SmallSite :110 / MediumSite :125. Current stable origin/master@0139a346 still uses one global, initializes it true at :213, and consumes it at :123 / :160 with AARadar plus related structure exclusions. Historical a96fdda2 only adds the AARadar guard; B69 origin/claude/b69@35547c47 matches the current-stable global-scope behavior. No checked ref scopes it by player, side or requester. Workflow/authority risk. Key by side/requester if it is meant as a player preference, or explicitly document/smoke global behavior.
Salvage cleanup, payout typo and authority edge Construction and CoIn systems owns the refreshed branch matrix. 2026-06-22 recheck: docs branch docs/developer-wiki-index@fb8d4ebc, current stable origin/master@0139a346, current Miksuu master@b8389e748243, origin/perf/quick-wins@0076040f and historical release commit a96fdda2 all keep lowercase ChangePlayerfunds in both payout paths while Init_Client.sqf compiles ChangePlayerFunds. Current origin exposes no release/* or feat/*salvage* heads; Miksuu still exposes historical EngineerSalvageAbility@99bfaeb8 and SalvageRuTranslationFix@291c6cb4 as inherited feature-debt heads. Current stable line drift is Skill_Salvage.sqf:38, updatesalvage.sqf:51, Init_Client.sqf:72,110 and Client_BuildUnit.sqf:343; docs/Miksuu/perf use updatesalvage.sqf:50, Init_Client.sqf:53,91 and Client_BuildUnit.sqf:267, while historical a96fdda2 drifts the launch to Client_BuildUnit.sqf:270. All checked roots keep the updatesalvage.sqf:10 `
Empty supply trucks linger by design Marker cleanup/restoration owns the refreshed branch matrix and exact collector/handler line proof. 2026-06-22 recheck: docs head b4e10b5f, current stable origin/master@0139a346, direct current Miksuu master@b8389e748243, origin/perf/quick-wins@0076040f, B69 origin/claude/b69@0094647d and B69 finalpieces 80d3267c all keep the 24-hour supply-truck handler shape in both maintained roots. Current origin exposes no live release/* or cleanup/supply feature heads; historical a96fdda2 matches the same 24-hour policy, but is not current release proof. Owner-decision logistics/cleanup behavior. Decide whether 24-hour supply-truck persistence is intended support/logistics state or should become shorter/parameterized; if patched, propagate source Chernarus plus maintained Vanilla and smoke ordinary empty vehicles, medical/repair double-timeout vehicles and supply mission/logistics use.
Clickable-text sound config branch split Client UI systems owns the current branch matrix. Current stable origin/master@0139a346 now keeps valid RscClickableText.soundPush[] = {"", 0.2, 1}; at Rsc/Ressources.hpp:556 in both maintained roots, matching :92; Chernarus blame points to 1a5e0b40, maintained Vanilla propagation to 9b49883c, and current master derives 14 controls from that base class at the matrix line refs. Older docs/source b5219d47, Miksuu b8389e74, origin/perf/quick-wins 0076040f, release a96fdda2 and UI theme evidence remains branch-scoped for the former malformed value until rechecked or merged. Source-present on current stable; smoke-pending for release wording. Do not reopen the base-class edit on current master. For older target branches that still carry {, 0.2, 1}, port the current valid value, propagate maintained Vanilla and smoke representative clickable controls in gear, WF menu/HUD toggles, construction/CoIn, artillery and economy.
Buy gear partials GUI_BuyGearMenu.sqf includes self-documented TODOs for target refresh, vehicle target content and template scope. Partial UI cleanup; avoid expanding templates until gear/vehicle/backpack behavior is mapped.
Fast travel fee Current-stable refresh 2026-06-22: current stable origin/master@0139a346 still implements paid fast travel locally in both maintained roots, reading fast-travel mode/range at GUI_Menu_Tactical.sqf:22-23, hiding unaffordable destinations and drawing marker-price text at :185,195-196,215, then recalculating/debiting locally at :403-404; constants are Init_CommonConstants.sqf:388,398-400. The stale fee-policy TODO is absent on current stable. Docs branch docs/developer-wiki-index@a489e6ff, Miksuu b8389e74, perf 0076040f and historical release a96fdda2 keep the old TODO at GUI_Menu_Tactical.sqf:147, the same fee/debit shape at :186,196-197,216,404-405, and constants line drift at docs/Miksuu/perf Init_CommonConstants.sqf:218,228-230 versus release :231,241-243. Current origin exposes no live release/* or fast-travel feature heads on 2026-06-22. Working/partial UX, docs-ready owner decision. Use Client UI systems; do not reopen stale-TODO removal on current stable. Decide hide-vs-disabled/prompt policy, add a final local funds/context recheck if desired, propagate Vanilla and smoke modes 0/1/2, insufficient/exact/sufficient funds and HQ/town/command-center starts.
Stable low-priority TODO cluster Branch check 2026-06-06: current source Chernarus, maintained Vanilla, stable origin/master, Miksuu upstream, perf/quick-wins and release all keep the same three TODO-only shapes: side-presence logic detection followed by fixed resistance defender setup (Init_Common.sqf:273-285), CoIn border recreation tied to area-size changes but not logic-position moves (coin_interface.sqf:114,419-425) and town-attack waypoint polish comments for combat/speed/radio/camp behavior (Server_AI_SetTownAttackPath.sqf:74-78). Consolidated from three vague rows. These are not confirmed broken features by themselves. Routes: Architecture overview for common init/side presence, Construction and CoIn for border relocation, and AI runtime/HC loop map for attack-path revival/polish.

Scout-Harvest Routing / Archived Findings

The 2026-06-04 mini-scout waves are now treated as harvested source-check history. Keep exact chronology in Agent worklog, Subagent discovery swarm, agent-feature-status.jsonl, agent-events.jsonl and git history; do not repeat row-by-row scout output here after canonical owner pages carry the evidence.

Finding family Current owner route Register status
Generated version.sqf, mission config and terrain output contract Mission config/version graph, Content structure and maps, Tools/build Documented; keep release-footgun rows above when they affect current packaging.
Latent AIBuyUnit, factory queue/debit/refund and purchase semantics Factory and purchase systems atlas, Factory queue cleanup, Economy authority first cut Keep one live status row for the latent server buy worker; do not re-describe it in every scout harvest.
UI/HUD/dialog issues such as help unload state, GPS zoom routes, vote rows, service affordability, EASA exact funds, gear templates and buy-menu cost display Client UI systems atlas, Player UI workflow map, Gear/loadout/EASA atlas, Service menu affordability guards Owner pages track exact controls and smoke packs; Feature Status should only keep high-risk rows.
AI commander, autonomous flag, spawned-unit order inheritance and branch-only AI commander supervisor work AI commander autonomy audit, AI runtime/HC loop map Stable master remains partial; branch-only revival evidence must stay branch-scoped.
Headless delegation, static-defence accounting and cleanup loops Headless delegation/failover, AI/headless and performance Owner pages track payload-shape and lifecycle debt.
Construction base area, CoIn null guards, auto-wall toggle and structure logic list cleanup Construction and CoIn, Construction logic list cleanup Keep as source-unpatched construction debt; avoid duplicating implementation walkthroughs here. Branch check 2026-06-22: docs 3406ffa0, current stable origin/master@0139a346, Miksuu b8389e74, origin/perf/quick-wins@0076040f, historical release a96fdda2 and active B69 origin/claude/b69@0a1ccb4d all keep SmallSite add/add at Construction_SmallSite.sqf:70,99 while MediumSite removes at Construction_MediumSite.sqf:70,114 in both maintained roots. Current origin exposes no release/* or construction feature heads for a live rescue branch.
Respawn penalties, threeway defender respawn, HandleAT handler lifecycle and respawn candidate caveats Respawn/death lifecycle, Towns/camps Owner pages carry exact conditions and smoke targets.
Supply mission completion PV/state, player-object matching, truck/heli branch scope, PR #10-#12 history and side-supply reason logging Supply mission architecture, Supply mission authority cleanup, Public variable channel index, Economy/Towns/Supply Docs checkout 15563691, current Miksuu b8389e74 and perf 0076040f remain truck-only; current stable origin/master@0139a346 carries the supply-heli/cash-run branch shape in both maintained roots. Historical release commits a96fdda2 / 7ff18c49 remain release-line evidence because current origin exposes no live release/* head.
Side-supply authority, reason-drop parsing, commander assign/vote and economy hardening Economy authority first cut, Server authority migration map, Hardening roadmap Keep authority risks live; route repeated fix-shape details to owner pages.
Runtime cleanup, SideMessage, dropped-item scans, tool analyzers, LoadoutManager and integration footguns Server gameplay runtime atlas, Marker cleanup/restoration atlas, Performance opportunity sweep, Tools and build workflow, External integrations Runtime/tooling pages own exact script and C# references.

Broken Feature Candidate: AI Supply Logistics

AI_UpdateSupplyTruck.sqf remains the clearest abandoned logistics feature. Docs branch ea0e0f1b, Miksuu and perf still raw-spawn the missing worker when truck supply plus AI commanders are enabled. Current stable origin/master@0139a346 has the safety wrapper: Server/Init/Init_Server.sqf:43,462-463 keeps the compile disabled, leaves the truck-supply + AI-commander branch visible, initializes wfbe_ai_supplytrucks and logs that legacy AI supply-truck logistics are disabled instead of spawning UpdateSupplyTruck. The old worker still references missing Server/FSM/supplytruck.fsm, so simply restoring the compile would fail later on the missing FSM. Use the AI commander matrix before merging raw-spawn branches.

Canonical routes: Economy/Towns/Supply, AI commander autonomy audit, Abandoned feature revival review, Current PR #1 supply helicopters.

PR #1 Supply Killed-Handler Status

Old wording that called PR #1 a confirmed unguarded handler-stacking defect is stale for current stable and historical PR #1/release-line source checks. Current stable origin/master@0139a346 sets wfbe_supply_killed_eh_set at supplyMissionStarted.sqf:15-16 before adding the Killed handler at :17 in both maintained roots; older PR/release evidence should stay historical until live feature/release heads return.

Still open before release-ready wording: repeated load/deliver/destroy runtime smoke, persistent guard behavior, handler-ID/removal or re-arm policy, cash-run semantics, JIP cooldown behavior and clear branch wording that docs/source remains truck-only typed, current stable carries the heli shape, current Miksuu/perf remain old-shape, and release/PR evidence is historical without live heads. Canonical routes: Current PR #1 supply helicopters, Supply mission architecture, Supply mission authority cleanup.

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: Hardening roadmap

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

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

Docs rule: source-backed claims only; Arma 2 OA scripting docs only; gameplay edits start in Missions/[55-2hc]warfarev2_073v48co.chernarus.

Sidebar

Clone this wiki locally