Skip to content

Release Source Intake Map

rayswaynl edited this page Jul 1, 2026 · 18 revisions

Release Source Intake Map

Round32 snapshot: 2026-07-01T23:18:00+02:00.

This page maps public source inputs for the WASP Warfare release loop. It is deliberately lightweight: no large archives, passworded files, private server logs, SSH paths, player identifiers or private runtime material were downloaded for this pass.

External sources can suggest or corroborate release work, but release-ready claims still require repo evidence plus stamped Chernarus and Takistan runtime proof.

Current Sources

Source Reachable Use Constraint Next task
rayswaynl/a2waspwarfare Yes Public fork baseline and branches. Local release worktree is authoritative for the current release candidate. Compare after freeze or push planning.
rayswaynl/a2waspwarfare wiki Yes Public release and evidence summaries. Wiki is secondary evidence; source/runtime proof wins. Keep release evidence index updated.
Miksuu/a2waspwarfare Yes Upstream source and branch lineage. Live server mission may differ from visible Git history. Target AI commander, HC/performance and terrain branches.
Jerry bIdentify files Yes Armaholic-era archive index and historical mission metadata. Mixed availability; avoid bulk downloads. Keep intake to named single archives and hash-verified metadata.
Jerry Warfare bucket Yes Warfare BE, Gossamer and Takistan CTI references. Some entries are missing or point to dead historical links. File 5420 baseline matrix is recorded below; do not promote it to runtime proof.
Miksuu Google Drive mission dump Reachable as embedded listing Potential old mission/mod archive filenames. Passworded/protected archives; no bulk extraction without approval. Inventory filenames and sizes only, then request explicit single-archive approval if needed.
Miksuu War Room Yes Public live server status and stats surface. Dynamic; player data should be anonymized in public wiki. Use timestamped captures as supporting evidence, never as an RPT substitute.
Miksuu War Room API Yes Machine-readable online/stale/server/currentRound/serverFps fields. Latest public sample checked 2026-07-01T21:44:04Z was online=true, stale=false, map Chernarus, 0 players, 2 HCs; dynamic/anonymized, not release proof. Re-sample during runtime proof and correlate with RPT timestamps.
Direct stats backend Private ops-only reference Possible direct stats backend. Do not publish raw backend IPs; lightweight check timed out. Prefer the domain endpoint unless diagnosing routing privately.
BI Forums Yes Primary community lineage for Warfare BE, BECTI and WASP expectations. Forum history is supporting context, not code proof. Create source cards separated into direct A2 evidence versus lineage/analogy.

2026-07-01 Command-Center Intake Update

This pass was run for draft PR #125 / codex/release-command-center-20260630 while release runtime proof is still pending.

  • rayswaynl/a2waspwarfare, the public wiki and Miksuu/a2waspwarfare are reachable. The fork's AICOM layer is the largest release-relevant delta from the original public mission repo.
  • Jerry/bIdentify is reachable. The Arma 2 OA Warfare bucket is sparse but still useful; WarfareV2_073LiteCO.zip is the best public Benny 2.073 lineage baseline for mission structure and release-regression comparisons. Round32 downloaded this single named archive into scratch, verified its published SHA256, extracted only Chernarus/Takistan PBO internals for file-shape comparison, and kept Zargabad out of the PR #125 release path.
  • Miksuu War Room is reachable, but live data is JS/API-driven and should only be used as supporting, timestamped public context. It is not a substitute for exact RPT evidence.
  • The Google Drive mission dump could not be safely enumerated in this environment, and the direct stats backend timed out. SSH/server RPT collection still requires explicit approval plus a usable session or credentials.
  • Wiki freshness check: Chernarus and Takistan map pages exist, but release notes should treat their older source-verification hashes as stale until the current release head is rechecked.
  • Release docs must keep Chernarus/Takistan runtime status as runtime-pending until the exact ten-file packet passes: server, HC1, HC2, start-client and late-JIP for both terrains.

Source Card: Jerry / Benny 2.073 Baseline

  • Jerry bIdentify file 5420 / WarfareV2_073LiteCO.zip is the best public Benny 2.073 lineage lead from this pass; treat it as metadata-first public archive evidence, not current WASP behavior.
  • Existing old-mission comparison remains Old WarfareBE Performance Comparison, based on BennyBoy-/ArmA2_WarfareBE@aeb71bb and scoped to Takistan Lite OA unless another package is explicitly checked.
  • 2026-07-01 Round32 controlled extract: file 5420 downloaded from bIdentify's hash endpoint, matched SHA256 212048B93831A711BF896679069CF1DFF9B3726B28238DAC52CA82729CA58E0A, and contained exactly three PBOs: WarfareV2_073LiteCO.Chernarus.pbo, WarfareV2_073LiteCO.Takistan.pbo and WarfareV2_073LiteCO.Zargabad.pbo. Chernarus and Takistan each extracted to 603 PBO entries with the scratch extractor; Zargabad stayed indexed only because PR #125 packages Chernarus and Takistan.
  • The extract closes the metadata matrix part of the Jerry lane. PBO-internal semantic comparison remains intentionally narrow: use it to understand historical structure, PVF/init placement and legacy AI logistics lineage, not to import source directly.
  • Use Jerry/Benny 2.073 for mission-structure, parameter, town-loop, PVF and package-lineage comparisons only. Do not use it as runtime FPS or release-readiness proof.
  • Miksuu/a2waspwarfare is the modern upstream/source lineage repo; it is not proof of the live server package and should be compared against the release worktree before claims are promoted.
  • BI forum threads are lineage and intent context. BI Arma 2 OA command docs remain the command-availability authority; repo source plus current PR #125 RPT evidence remains behavior authority.
  • No bulk archive download, passworded dump extraction, SSH/RPT access or live-server probing belongs in this card without explicit approval.
Field Jerry 5420 / WarfareV2_073LiteCO.zip PR #125 current package
Archive status Single named archive downloaded and SHA-verified in scratch; Chernarus/Takistan PBOs extracted for file-shape comparison only. _MISSIONS.7z package proof generated from release command-center.
Archive SHA256 / bytes SHA256 212048B93831A711BF896679069CF1DFF9B3726B28238DAC52CA82729CA58E0A; 1,654,080 bytes. SHA256 3DB01AC1656329ECCAE9896CE9442680D5D904C563DD44590FFBD20954CF7B87; 7,162,113 bytes.
Entry count ZIP has 3 PBOs; Chernarus PBO has 603 extracted entries; Takistan PBO has 603 extracted entries. 1,885 archive entries.
Mission roots / PBO names WarfareV2_073LiteCO.Chernarus.pbo, WarfareV2_073LiteCO.Takistan.pbo, WarfareV2_073LiteCO.Zargabad.pbo. [55-2hc]warfarev2_073v48co.chernarus and [61-2hc]warfarev2_073v48co.takistan.
Terrain scope Historical Benny 2.073 Lite CO covers Chernarus, Takistan and Zargabad. Zargabad is lineage context only for PR #125. Chernarus and Takistan maintained roots only.
Version marker No generated WASP release marker; this is a 2012 Benny package. `WASPRELEASE
Parameters / mission config mission.sqm, description.ext, Rsc/Parameters.hpp, Common/Init/Init_PublicVariables.sqf and Server/Init/Init_Server.sqf exist in both extracted Chernarus and Takistan PBOs. Required package files present; manifest hashes recorded for mission.sqm, description.ext, Rsc/Parameters.hpp, initJIPCompatible.sqf, stringtable.xml and init files.
PVF / town-loop comparison Public-variable init lives under Common/Init/Init_PublicVariables.sqf; historical AICOM is Server/FSM/aicommander.fsm, not the current Server/AI/Commander tree. Current PR carries PVF dispatcher shape guards, HC delegate allowlist coverage for town AI/static defense/side patrol/AICOM teams, AICOM requester validation, AICOM HandleSpecial short-payload guards, patrol-list shape cleanup and AICOM order-sequence guard coverage in the newer Server/AI/Commander tree.
Legacy AI logistics Both extracted Chernarus and Takistan PBOs ship Server/FSM/supplytruck.fsm, compile UpdateSupplyTruck at Server/Init/Init_Server.sqf:36, initialize wfbe_ai_supplytrucks, and spawn it at :335. PR #125 intentionally comments out UpdateSupplyTruck compile and logs the legacy AI supply-truck path disabled because Server/FSM/supplytruck.fsm is absent.
Release meaning Historical lineage/reference candidate only. Package-proven/source-backed, runtime-pending release candidate; no deploy approval implied.

BI Forum Targets

Release Discipline

  • Treat public archives and forum posts as leads until a source path, branch or runtime artifact proves the claim.
  • Do not bulk-download or extract passworded archives without explicit approval.
  • Keep live server statistics anonymized and timestamped.
  • Runtime release proof remains the source-map-built exact ten-file Chernarus/Takistan RPT packet plus scorer summary from the current release candidate; private source maps and generated run ledgers stay out of public wiki output.

Continue Reading

Previous: Current source snapshot | Next: Agent release readiness ledger

Main map: Home | Progress: Progress dashboard | Testing: Testing workflow

Sidebar

Clone this wiki locally