-
Notifications
You must be signed in to change notification settings - Fork 0
Attack Wave Authority Playbook
Implementation playbook for Claude DR-41: ATTACK_WAVE_INIT is a forgeable direct publicVariable channel that can make side-wide unit prices free or negative.
Scope: current source Missions/[55-2hc]warfarev2_073v48co.chernarus plus maintained Vanilla Missions_Vanilla/[61-2hc]warfarev2_073v48co.takistan. Apply gameplay patches in Chernarus first, then propagate maintained Vanilla and generated missions with Tools/LoadoutManager.
| Field | Value |
|---|---|
| Finding | Confirmed high-risk authority bug |
| Finding id | DR-41 |
| Backlog id | attack-wave-authority |
| Primary files |
Common/Functions/Common_AttackWaveActivate.sqf, Server/Functions/Server_AttackWave.sqf, Server/PVFunctions/AttackWave.sqf
|
| Risk | Forged client _supply / _side can apply a side-wide ATTACK_WAVE_PRICE_MODIFIER of 0 or negative; forged ATTACK_WAVE_DETAILS can bypass the init calculation and directly mutate active wave state. |
| Patch type | Server-authoritative direct-PV handler rewrite |
| File | Evidence |
|---|---|
Client/FSM/updateclient.sqf:240 |
Adds the HEAVY ATTACK MODE action on the side HQ. The action condition is client-side only: ((sideJoined) Call GetSideSupply) >= 25000 and nearby cursor target. |
Common/Functions/Common_AttackWaveActivate.sqf:3-8 |
Reads _supply and _side from action arguments, assigns ATTACK_WAVE_INIT = [_supply, _side], then broadcasts publicVariableServer "ATTACK_WAVE_INIT". |
Server/Functions/Server_AttackWave.sqf:1-15 |
Direct PVEH receives ATTACK_WAVE_INIT, trusts payload _supply / _side, and computes _discountPercentage from client _supply. |
Server/Functions/Server_AttackWave.sqf:19-27 |
Writes global ATTACK_WAVE_PRICE_MODIFIER, publishes ATTACK_WAVE_DETAILS, then sleeps for the computed attack-wave length. |
Server/PVFunctions/AttackWave.sqf:19-62 |
Handles ATTACK_WAVE_DETAILS, trusts _side, _priceModifier and _attackLength, stores per-side active/modifier state, spends side supply, sends client HandleSpecial / LocalizeMessage, then resets state when length reaches 0. |
Client/GUI/GUI_Menu_BuyUnits.sqf:90,261 |
Multiplies unit cost by ATTACK_WAVE_PRICE_MODIFIER. |
Client/Functions/Client_UIFillListBuyUnits.sqf:60 |
Displays buy-list price using ATTACK_WAVE_PRICE_MODIFIER. |
Common/Init/Init_CommonConstants.sqf:166,197-199 |
Sets WFBE_C_ECONOMY_SUPPLY_MAX_TEAM_LIMIT = 50000, default ATTACK_WAVE_PRICE_MODIFIER = 1, and active flags false. |
BattlEyeFilter/publicvariable.txt |
Does not include ATTACK_WAVE_INIT; the repo filter only carries the AFK feature rule. |
Checked on 2026-06-24 after git fetch --all --prune. No checked branch or maintained root fixes the direct-PV authority issue. Docs/source HEAD@426de4570993 is unchanged from a764d51107de, 6d263dc21093, 1c1ea55970dc and the older f3e157f2 line-anchor proof for checked Chernarus/Vanilla attack-wave request/detail/client-price paths. Current stable origin/master@f8a76de349da equals origin/claude/b74.1-aicom@f8a76de349da; current B74.2 origin/claude/b74.2-aicom@21b62b04fee3 keeps the same request/detail trust in both maintained roots. Scoped origin/master..origin/claude/b74.2-aicom attack-wave-path deltas touch only source-Chernarus GUI_Menu_BuyUnits.sqf and Init_CommonConstants.sqf, and scoped d472da6a..21b62b04 deltas are empty for checked attack-wave paths. Current origin exposes no live release/*, attack-wave or support rescue heads on 2026-06-24; the visible attack-wave/release/support matches are Miksuu historical/upstream namespaces, so a96fdda2, c20ce153 and 994150da remain historical evidence.
| Ref | Chernarus source | Maintained Vanilla | Result |
|---|---|---|---|
Docs/source HEAD@426de4570993
|
Source-unchanged from a764d51107de for checked paths. updateclient.sqf:240 gates the action client-side; Common_AttackWaveActivate.sqf:6,8 sends ATTACK_WAVE_INIT; Server_AttackWave.sqf:5-6,15,23,27,36,38 trusts payload _supply / _side and publishes details; AttackWave.sqf:19,23-25,40 trusts detail payload and debits side supply; buy-price consumers are Client_UIFillListBuyUnits.sqf:60 and GUI_Menu_BuyUnits.sqf:90,261; constants are at Init_CommonConstants.sqf:166,197-199. |
Same maintained-root line shape. | Patch-ready, current-docs-source-unpatched. |
Current stable origin/master / B74.1 f8a76de349da
|
Same trust shape with line drift: action updateclient.sqf:260, buy-price display Client_UIFillListBuyUnits.sqf:90, purchase/menu paths GUI_Menu_BuyUnits.sqf:99,244-245,416, Chernarus constants Init_CommonConstants.sqf:547,591-593; request/detail lines stay Common_AttackWaveActivate.sqf:6,8, Server_AttackWave.sqf:5-6,15,23,27,36,38 and AttackWave.sqf:19,23-25,40. |
Same request/detail/client-price line shape; Vanilla constants are Init_CommonConstants.sqf:349,393-395. |
Patch-ready, current-stable/B74.1-unpatched. |
Current B74.2 origin/claude/b74.2-aicom 21b62b04fee3
|
Same direct request/detail trust shape. Action line remains updateclient.sqf:260; request/detail lines remain Common_AttackWaveActivate.sqf:6,8, Server_AttackWave.sqf:5-6,15,23,27,36,38 and AttackWave.sqf:19,23-25,40. Source-Chernarus buy-price consumers line-drift to Client_UIFillListBuyUnits.sqf:90 and GUI_Menu_BuyUnits.sqf:105,250-251,422; ATTACK_WAVE_PRICE_MODIFIER is at Init_CommonConstants.sqf:604 after B74.2 pop-tier/AICOM constant drift. |
Same request/detail/client-price line shape as current stable/B74.1; maintained Vanilla buy-price consumers stay Client_UIFillListBuyUnits.sqf:90 and GUI_Menu_BuyUnits.sqf:99,244-245,416, with ATTACK_WAVE_PRICE_MODIFIER at Init_CommonConstants.sqf:393. |
No authority rescue; B74.2 only line-drifts source-Chernarus buy-menu/constants context among checked paths. |
Current B69 origin/claude/b69 8d465fcede7f
|
Same trust shape as current stable for the request/detail/client paths. Chernarus constants drift to Init_CommonConstants.sqf:515,559-561; B69 path deltas 0a1ccb4d..8d465fce and b8530477..8d465fce are empty for checked attack-wave request/detail/client-price paths. |
Same request/detail/client-price shape; Vanilla constants drift to Init_CommonConstants.sqf:349,393-395. |
B69 does not rescue this lane; only unrelated constants/AICOM movement causes line drift. |
Adjacent B74 AICOM spend origin/claude/b74-aicom-spend b23f557fc912
|
Same request/detail/client trust shape as B69. origin/claude/b69..origin/claude/b74-aicom-spend touches only Common/Init/Init_CommonConstants.sqf among checked Chernarus attack-wave paths; constants drift to :528,572-574. |
Same request/detail/client-price shape as B69; constants stay at Init_CommonConstants.sqf:349,393-395. |
No attack-wave authority rescue; adjacent AICOM-spend constants drift only. |
Miksuu upstream miksuu/master b8389e74
|
Same trust shape; action line updateclient.sqf:260; constants at Init_CommonConstants.sqf:166,197-199. |
Same maintained-root shape. | No upstream rescue in current Miksuu head. |
origin/perf/quick-wins 0076040f
|
Same trust shape; action line updateclient.sqf:223; constants at Init_CommonConstants.sqf:166,197-199. |
Same maintained-root shape. | Perf branch side-supply/factory fixes do not touch attack-wave authority. |
Historical AI-commander commit c20ce153 (current origin exposes no feat/ai-commander head on 2026-06-22) |
Same trust shape; action line updateclient.sqf:223; Chernarus constants drift to Init_CommonConstants.sqf:174,205-207. |
Same maintained-root attack-wave shape; Vanilla constants remain :166,197-199. |
Treat as branch-scoped historical AI-commander evidence, not a live head. |
Historical release commit a96fdda2 (current origin exposes no release/* heads on 2026-06-22) |
Same trust shape; action line updateclient.sqf:260; constants at Init_CommonConstants.sqf:166,210-212. |
Same maintained-root shape. | Branch-scoped historical release evidence; no live release head rescues this lane. |
Historical Miksuu upstream/AttackWave commit 994150da
|
Same trust shape; action line updateclient.sqf:203; constants at Init_CommonConstants.sqf:145,174-176. |
Same maintained-root shape. | Treat as inherited feature debt, not a fix branch. |
Fixed-string grep also found no ATTACK_WAVE entry in repo-root BattlEyeFilter/publicvariable.txt for the checked refs; the checked filter still only carries 5 "kickAFK" at line 2. Treat this as still patch-ready current-source debt, not a propagated fix.
The unsafe path exists when all of these are true:
| Condition | Source-backed reason |
|---|---|
A client can broadcast ATTACK_WAVE_INIT
|
The channel is a direct publicVariable, not a registered PVF command. |
Payload contains forged _supply
|
Server_AttackWave.sqf:5 uses _this select 1 select 0 directly. |
Payload contains forged _side
|
Server_AttackWave.sqf:6 uses _this select 1 select 1 directly. |
| Client-side gate is bypassed | The GetSideSupply >= 25000 check is only the addAction condition in updateclient.sqf:260 on current stable. |
| Modifier math accepts impossible supply | Formula is 0.7 * (0.4 + ((50000 - _supply) * (1 / 50000))). At _supply = 70000, modifier becomes 0; larger values become negative. |
| Buy menus consume the modifier | Unit purchase UI multiplies costs by ATTACK_WAVE_PRICE_MODIFIER, so a forged side modifier affects all buyers for that side. |
This is not fixed by PVF dispatcher hardening. ATTACK_WAVE_INIT bypasses WFBE_PVF_* command dispatch entirely.
Wave R direct-PV review also confirmed that ATTACK_WAVE_DETAILS should not be treated as a safe server-internal detail. The intended sender is Server_AttackWave.sqf, but the event handler accepts the direct PV payload and uses it to set active state, pricing and duration. A public-server hardening patch therefore needs either a BattlEye rule that prevents clients from sending this channel or a handler-side acceptance guard that proves the detail was generated by the accepted server request path.
The intended spend model is not a fixed 25,000 supply cost in current source.
| Behavior | Source |
|---|---|
| 25,000 supply is only the minimum action gate. | updateclient.sqf:260 |
| The discount is based on the side supply value sent into the wave. | Server_AttackWave.sqf:15-17 |
| The side spends all current side supply when the wave starts. |
AttackWave.sqf:40, [_side, -(_side call GetSideSupply), ...] Call ChangeSideSupply
|
Default patch stance: preserve this model server-side. Server should re-derive current side supply, require at least 25000, compute the modifier from that real value, then spend the same real value or explicitly document any owner-approved change to fixed-cost attack waves.
Preferred shape:
- Keep
Common_AttackWaveActivate.sqfas a request sender, but stop sending economic truth. Payload should include requester context if useful, not_supply. - In
Server_AttackWave.sqf, treat the payload as untrusted request data. - Server derives
_sidefrom the requester when possible, or validates the requested side against server-known player/group state. - Server computes
_supply = _side Call GetSideSupply. - Reject if
_supply < 25000. - Reject if an attack wave is already active for that side.
- Compute the modifier from server
_supply. - Clamp modifier and duration even after server recomputation.
- Publish
ATTACK_WAVE_DETAILSonly after acceptance. - Ensure the
ATTACK_WAVE_DETAILShandler accepts only server-derived detail state, not arbitrary client detail payloads. - Ensure side-supply debit is based on server-derived
_supplyand happens once.
Pseudo-SQF outline:
"ATTACK_WAVE_INIT" addPublicVariableEventHandler {
private ["_request", "_requester", "_side", "_supply", "_modifier", "_length"];
_request = _this select 1;
_requester = if (count _request > 0) then {_request select 0} else {objNull};
// Arma 2 OA PVEH does not provide a clean sender identity. Treat requester as a hint and validate it.
if (isNull _requester || !isPlayer _requester) exitWith {
["WARNING", "Server_AttackWave.sqf: rejected attack wave request with invalid requester."] Call WFBE_CO_FNC_LogContent;
};
_side = side _requester;
if (!(_side in [west, east])) exitWith {};
if ((_side == west && ATTACK_WAVE_ACTIVE_WEST) || (_side == east && ATTACK_WAVE_ACTIVE_EAST)) exitWith {
["WARNING", Format ["Server_AttackWave.sqf: rejected duplicate attack wave request for [%1].", _side]] Call WFBE_CO_FNC_LogContent;
};
_supply = _side Call GetSideSupply;
if (_supply < 25000) exitWith {
["WARNING", Format ["Server_AttackWave.sqf: rejected attack wave for [%1], supply [%2] below threshold.", _side, _supply]] Call WFBE_CO_FNC_LogContent;
};
_modifier = 0.7 * (0.4 + ((WFBE_C_ECONOMY_SUPPLY_MAX_TEAM_LIMIT - _supply) * (1 / 50000)));
_modifier = (_modifier max 0.28) min 0.98;
_length = ((1 - _modifier) * 1500) max 0;
ATTACK_WAVE_DETAILS = [_side, _modifier, _length, _supply];
publicVariableServer "ATTACK_WAVE_DETAILS";
};The exact requester validation may need adjustment after a live Arma 2 OA smoke test. Because PVEH does not give a trustworthy sender identity, this patch is stronger than the current source but still benefits from BattlEye defense-in-depth on public servers.
AttackWave.sqf currently recomputes (_side call GetSideSupply) when debiting. After the authority patch, prefer one of these explicit choices:
| Option | Shape | Tradeoff |
|---|---|---|
| Preserve all-supply spend | Add server-derived _supplyToSpend to ATTACK_WAVE_DETAILS and debit exactly that once. |
Best preserves current design while avoiding a race between modifier compute and debit. |
| Recompute on debit | Keep [_side, -(_side call GetSideSupply)] Call ChangeSideSupply. |
Simpler but can desync the displayed modifier from the amount spent if supply changes between init and details handling. |
| Fixed cost | Debit 25000 or a named constant. |
Design change; update UI text, roadmap, docs and validation expectations. |
Whichever option is chosen, add an active-side guard before accepting a new wave. Duplicate ATTACK_WAVE_INIT events should not stack multiple sleeps, multiple debits or overlapping price modifiers.
| Edge case | Expected result |
|---|---|
| Legit side with supply >= 25000 | Attack wave starts, side supply is debited once, clients receive attack-wave modifier and message. |
| Side supply below 25000 | Request rejected with compact warning; no modifier, no debit. |
Forged _supply = 70000
|
Ignored; server uses real supply and cannot produce a zero/negative modifier. |
Forged _side = enemy side
|
Rejected or re-derived from requester; cannot start wave for the other side. |
Forged ATTACK_WAVE_DETAILS
|
Rejected or ignored; cannot set price modifier, active flag, wave length or side-supply debit directly. |
| Duplicate requests while active | Rejected; no duplicate debit and no overlapping reset thread. |
| JIP during active wave |
CLIENT_INIT_READY path still informs player for their side with current modifier. |
| Wave end | Modifier resets to 1, side active flag false, clients receive end message. |
| Hosted/listen server | No busy-loop or locality regression; server-side PVEH path still runs. |
| Gate | Check |
|---|---|
| Static source check |
Server_AttackWave.sqf no longer uses client _supply for modifier math and no longer trusts client _side without validation/re-derivation. |
| Static direct-PV check |
ATTACK_WAVE_INIT remains documented as a direct channel outside PVF, or the channel is explicitly migrated to a registered PVF with matching docs. |
| Dedicated smoke | Valid west/east attack waves work, debit supply once and reset prices after the wave. |
| Forgery smoke | Forged _supply >= 70000 and wrong-side payloads cannot set ATTACK_WAVE_PRICE_MODIFIER to 0, negative, or the wrong side. |
| JIP smoke | Late joiner during active wave receives correct modifier/message through CLIENT_INIT_READY; late joiner after end sees normal price. |
| RPT | Rejections log useful WARNINGs without hot-loop spam; no undefined variables or scheduler errors. |
| Generated missions | Run dotnet run from Tools/LoadoutManager in a correctly named a2waspwarfare checkout; missing 7za is packaging-only unless deployment packaging is required. |
| Test evidence | Record planned or actual evidence with agent-test-plan.schema.json. |
- Use Bohemia Interactive Arma 2 OA scripting semantics; do not assume Arma 3 remote execution or owner-sender APIs.
- Use
-LiteralPathin PowerShell when reading or editing[55-2hc]paths. - Keep gameplay changes in the Chernarus source mission first.
- Treat
BattlEyeFilter/publicvariable.txtas defense in depth, not mission authority. - Do not call the PVF dispatcher fix sufficient for this channel; direct PVEHs need their own validation.
- Keep logs compact and outside hot loops.
- Networking and public variables
- Hardening implementation roadmap
- Server authority migration map
- Economy, towns and supply
- Deep-review findings
agent-hardening-backlog.jsonl
Previous: Server authority migration map | Next: Testing workflow
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
- Shelved AICOM concepts - revivable someday ideas (owner-shelved 2026-07-03)
Docs rule: source-backed claims only; Arma 2 OA scripting docs only; gameplay edits start in Missions/[55-2hc]warfarev2_073v48co.chernarus.
- Getting started
- Status and coordination
- Agent context
- Agent collaboration protocol
- Agent worklog
- Agent worklog archive
- Progress dashboard
- PR cleanup and integration lab
- Shelved PR #169: gear price double-count
- Shelved PR #194: Chernarus no-trees
- Coordination board
- Codebase coverage ledger
- Bottleneck removal queue
- Current source status
- Wiki mirror reconciliation
- Navigation inventory
- Registers
- Agent orchestration
- Architecture
- Architecture overview
- Mission entrypoints and lifecycle
- Lifecycle wait chain
- Player join/disconnect and AntiStack lifecycle
- Mission parameters/localization/build inputs
- Stringtable localization key-family catalog
- Source inventory
- Content structure and maps
- Assets/config/localization/parameters
- Mission start parameters index
- Code and networking
- Gameplay systems
- Core systems index
- Gameplay systems atlas
- Commander/HQ lifecycle atlas
- Economy, towns and supply
- Economy system reference
- Balance asymmetries
- Anti-stack skill-balance mechanic
- Empty-side supply income stagnation
- Towns, camps and capture atlas
- Victory and endgame atlas
- Victory conditions reference
- Territorial victory reference
- Marker cleanup and restoration
- Marker loop engine and registries
- Map marker families content catalog
- Marker subsystem function reference
- Client marker FSM updater map
- Support specials and tactical modules
- SCUD TEL tactical munitions
- Naval HVT objectives (carriers/SCUD)
- SCUD saturation strike mechanic
- Takistan airfield FPV drone design
- Construction and CoIn systems
- Structure damage reduction & friendly-fire
- Construction logic list cleanup
- Flak tower & WDDM anchor compositions
- Resistance supply scaffold
- GUER Insurgents faction overview
- GUER Insurgents branch audit
- GUER insurgent player economy
- GUER air-defense loop (Ka-137/Mi-24)
- Upgrades and research atlas
- Supply mission architecture
- Supply mission authority cleanup
- Current supply helicopters PR1
- Respawn and death-loop lifecycle
- Vehicle theft economy pitch
- GUER tunnel network pitch
- Content, reference and catalogs
- Faction unit/vehicle roster catalog
- Auxiliary/SF/civilian unit catalog
- Gear store loadout route catalog
- Upgrade research (cross-faction)
- Gear store price and upgrade catalog
- Gear store catalog (complete, per faction)
- Defense structures catalog
- Artillery reference per faction
- AI squad team templates catalog
- Town AI lifecycle reference
- Town AI group composition catalog
- Class-skill system reference
- Player skill abilities reference
- Default gear template content catalog
- Chernarus map content reference
- Takistan map content reference
- Takistan features
- Takistan parity reference
- Takistan oilfields objective reference
- IRS IR-smoke countermeasure
- Arty module special munitions
- Zeta cargo sling-load reference
- Spawn primitive function reference
- Kill and score pipeline
- Waypoint helper function reference
- Position and proximity function reference
- Side/team state function reference
- Player AI watchdog and recovery
- AICOM stuck-recovery v2
- LoadoutManager data-model contributor guide
- Discord status bot setup and reference
- GLOBALGAMESTATS extension reference
- New player quickstart (player guide)
- Optional client mods (player guide)
- Earning funds and score (player guide)
- Vehicle service and logistics (player guide)
- Commander's handbook (player guide)
- Tactical support menu
- Paradrop player experience
- Supply missions (player guide)
- In-game briefing & Diary field manual
- Playable maps catalog
- Faction root variables reference
- Faction base structures catalog
- Counter-battery radar system
- Bank, Reserve and Artillery Radar structures
- Map ruleset model and object config
- Countermeasures module reference
- Vehicle countermeasure (flares/spoofing)
- UAV terminal and spotter system
- Artillery firing function reference
- Service Point pricing model
- Medic redeployment truck (forward spawn)
- Side-patrol runtime and convoy mechanics
- Day/night cycle and weather system
- Config lookup helper reference
- CIPHER sort utilities reference
- Modded maps status and content
- BattlEye filter setup and OA taxonomy
- Player squad/group join protocol
- AutoFlip vehicle recovery
- Engine stealth fuel toggle
- Valhalla vehicle climbing-assist
- Missile and ordnance Fired-EH reference
- Vehicle equip and rearm reference
- Array and collection utilities
- Server composition spawner reference
- Upgrade queue server loop
- Map boundaries and off-map enforcement
- Namespace/profile/diagnostic utilities
- Group bool getVariable A2-OA trap
- Vehicle weapon balance init
- View distance auto-throttle
- Camp & respawn-camp getters
- Performance audit writer
- Site clearance (bulldozer)
- Factory queue cancel & refund
- AI commander tunable constants
- Experimental feature-flag constants
- Flag system quick reference
- Mission tunable constants catalog
- Gear parsing & cargo capacity
- Structure dressing function
- Paradrop delivery functions
- ICBM nuke client VFX & radiation
- Server HandleSpecial router
- LocalizeMessage chat router
- Gear buy-menu render & price functions
- Server broadcast & telemetry loops
- Per-unit client init pipeline
- Vehicle marking & texture pipeline
- Defense category & budget
- Legacy AI order primitives
- Commander-team driver
- AICOM command verbs
- AICOM behavior fix taxonomy
- AI commander wildcard deck reference
- AICOM aircraft and airfield system
- Static-defense manning
- End-of-game stats screen
- AI commander execution loop
- Deployable bipod / weapon resting
- Town-economy getters
- Server-init deadspawn & airfield probe
- GUER VBIED detonate action
- Resource income-tick engine
- AI commander treasury accessors
- PVF send-helper contracts
- AICOM logging & AICOMSTAT telemetry
- AICOMSTAT v2 event census
- WASPSCALE v2 telemetry
- WASPSCALE v2-ext coverage audit
- Telemetry families reference
- Group lifecycle & entity reaping
- Batch AI spawner orchestrator
- Client funds/income HUD readout
- Server group GC & cap warning
- Town runtime tuning constants
- Client input/hotkey handler
- WASP base-repair system
- WASP DropRPG launcher/ordnance
- CoIn construction-interface client engine
- Town-capture garrison & airfield rebuild
- Map-control & minimap templates
- Client FPS & state telemetry
- Client service-proximity getters
- Airfield-exclusive roster & unit hints
- Unit-camera spectator system
- Town-garrison patrol/defense worker
- RequestTeamUpdate squad-discipline
- Arma2Warfare GPT assistant
- LoadoutManager build configs & defines
- GLOBALGAMESTATS extension logging
- Discord bot instrumented logging
- Eden/Everon & Taviana map content
- Cruise missile strike asset
- AI / HC
- AI headless and performance
- AI mods and pathfinding reference
- Headless client scaling and topology
- AI runtime/HC loop map
- Headless client init and stat loop
- HC delegation target selection
- Player AI caps and role balance
- Old WarfareBE FPS comparison
- AI commander autonomy audit
- Upstream BE 2073 AICOM delta
- Parent 2.073 divergence audit
- AI commander capture & fun plan
- AI commander B69 improvement roadmap
- AI commander B69 implementation sketches
- AICOM V2 cutover status
- Headless delegation and failover
- Commander reassignment call shape
- GUER Director living-resistance pitch
- Quality and operations
- Foundation perf findings & Tier-3 dead-ends
- Dead/stale code register
- Commander vote/reassignment
- Attack-wave authority
- Server runtime and operations
- Server ops runbook
- JIP enrollment & client data delivery (b74.2 lessons)
- Server gameplay runtime atlas
- PerformanceAuditAnalyzer
- Performance opportunity sweep
- Documentation plan
- Knowledge platform roadmap
- Wiki quality audit
- Wiki pruning and relevance ledger
- Audit findings queue (2026-06-03)
- Deep review findings
- Client UI / server-loop perf findings
- Performance gain simulation
- Self-host testing field notes
- Cleanup and work lanes
- Hardening and authority
- UI / player workflows
- Client UI, HUD and menus
- UI HUD and dialogs
- Player UI workflow map
- Client UI systems atlas
- UI IDD collision repair
- UI control class library reference
- UI theme palette and style macros
- UI design inspiration 2026-07
- Available-actions client gate FSM
- Gear/loadout/EASA atlas
- Gear template profile filter
- Vehicle cargo equip loop bounds
- Factory and purchase systems atlas
- Service menu affordability guards
- WASP overlay
- Class-skill system reference
- Skin selector and class swap
- Earplugs audio toggle
- Mission audio catalog
- HQ radio knowledge-base catalog
- QoL trio player hints
- Player vehicle/travel actions
- Tooling / release / integrations
- Tools and build workflow
- Warfare web tools
- Ecosystem & companion repos
- Zargabad tooling parity
- July 2026 release readiness
- Operator monitor and CPU affinity tools
- Tooling release readiness audit
- Source fix propagation queue
- Agent release readiness ledger
- Release source intake map
- Testing/debugging/release workflow
- Current RPT release gate
- RPT telemetry consumer port map
- External integrations
- Integration trust boundary audit
- AntiStack database extension audit
- Community & Dev
- Community & Dev
- Miksuu upstream wiki import / archive index
- Upstream changelog feature leads
- Developer history and upstream lessons
- Upstream Miksuu commit intel
- Upstream mining ledger
- Archive script mining v2
- Upstream BE 2073 AICOM delta
- Parent 2.073 divergence audit
- PR8 and Drone upstream lesson match
- Development lessons learned
- External research reports
- Audit archive 2026-07
- Briefing reference
- Utes invasion concept
- Miksuu archive: Home
- Miksuu archive: Welcome
- Miksuu archive: Big announcements
- Miksuu archive: Changelog
- Miksuu archive: Development process
- Miksuu archive: Discord bot
- Miksuu archive: Gameplay videos
- Miksuu archive: LoadoutManager
- Miksuu archive: Chernarus script architecture
- Base-game visual catalogs
- Compatibility and references
- HC upstream history and lessons
- Player stats branch audit
- BuyMenu EASA QoL branch audit
- Perf quick wins branch audit
- Commander positions branch audit
- Zargabad branch audit
- Quad AI Commander concept
- Arma 2 OA external reference guide
- Base-game config & image reference
- Arma 2 OA compatibility audit
- Arma 2 OA agent traps reference
- Arma 2 OA command versions
- Wiki source consistency
- External Arma 2 OA reference index