Capture current mission, AI, map and administration development
Include the current addon, terrain integrations, tools, regression tests and recorded development evidence.
This commit is contained in:
+226
-81
@@ -1,123 +1,268 @@
|
||||
# Development playtest build — 20 September 2026
|
||||
# Combined-addon development playtest build
|
||||
|
||||
**Current layout:** all owned modules now live in `addons/core/addon.gproj`.
|
||||
Use [single-mod setup and commands](single-mod.md) for current builds. Both
|
||||
Workbench fixture selectors (`core` and `chat`) load that same project and require
|
||||
the external dependencies. Five-addon and vanilla-only build instructions/results
|
||||
below describe the historical layout.
|
||||
**4 October 2026 — refreshed UI/BMP development handoff:** [package and editable source](../.build/playtest-2026-10-04-ui-bmp/README.md).
|
||||
|
||||
The combined addon includes the inventory hit-zone callback correction and mounted BMP ammunition-accounting corrections, alongside selectable static crash starts and the existing finite base escape loop. Prison remains the default. **439 authored files, 378 exact PAK payloads and 3 runtime files** match the handoff. The exact code/tests/tools bind to the completed **309-program regression pass**, with any later checkpoint prose changes recorded separately. The exact-source normal escape completes **64 assertions and 1 completion**, with zero script/runtime failures and **13 retained engine errors**. Ordinary startup of these exact runtime bytes reaches the normal mission and local prisoner with zero script/runtime failures and **17 retained engine errors**.
|
||||
|
||||
For the latest five-addon source and packages with RHS/WCS/BMP, use the separate [road-interception handoff](../.build/playtest-2026-09-20-road-interception/README.md) and its player route. Core starts cleanly; the full external diagnostic reaches local prisoner admission but retains known localization errors. The instructions and evidence below describe an older vanilla-only snapshot.
|
||||
This is an **unqualified development candidate**. Strict packaging/startup failures remain recorded. Synthetic inventory notifications and bounded BMP inventory/status diagnostics do not establish natural-injury/manual UI behavior, physical interception, human escape, multiplayer/JIP/reconnect, comparative FPS or clean release acceptance. Existing missions and all five prior sealed candidates remain unchanged. No installed runtime is replaced and nothing is published.
|
||||
|
||||
The handoff below is the historical `5e74269` vanilla-only candidate. Current AI/Chat source requires the audited RHS/WCS/BMP closure; use [the external development build workflow](packed-external-development.md) for a fresh build. Do not identify this older handoff as the current mission.
|
||||
**3 October 2026 — refreshed crash-start development handoff:** [package and editable source](../.build/playtest-2026-10-03-crash-start/README.md).
|
||||
|
||||
This refresh targets `/home/jakub/devel/escapistsrereintroduced/.build/playtest-2026-09-20` from gameplay source commit `5e74269`. It adds mission-owned Chat administration and menu, the owned Intel migration, and fairer HQ contact selection to the previous playtest. **The refreshed handoff is ready for human testing.** All 216 authored files match commit `5e74269`, all five PAK payloads match those sources, and all fifteen copied runtime files are verified. [Packed Core](evidence/packed-core-2026-09-20-playtest/report.json) and [packed full scenario](evidence/packed-chat-2026-09-20-playtest/report.json) pass ordinary startup with zero captured errors, unchanged inputs and verified cleanup. Consult [the exact build record](evidence/playtest-2026-09-20/build.json) and the handoff's raw `checks/`. This remains a development candidate for human testing, not a qualified release.
|
||||
The combined addon now packages the static crash-start choice, memory-based HQ searches, BMP interception implementation and recent configuration/resupply fixes. Prison remains the default. **437 authored files, 376 exact PAK payloads and 3 runtime files** match the handoff. The unchanged code/tests/tools reuse the completed **307-program regression pass** with three recorded subsequent documentation changes. The exact-source scripted default escape completes **64 assertions and one round**; ordinary startup of the exact package reaches the normal mission and local prisoner. Both have zero script/runtime failures, while retaining **13 and 17 engine errors**, respectively. The earlier 66-assertion crash route predates two terrain Game Master edits; that source difference remains recorded.
|
||||
|
||||
The source baseline already has native menu/owner-RPC and scripted escape evidence, including the final journal rendering/follow correction; see [Chat integration](chat-integration.md) and [AI/Intel migration](owned-ai-intel-migration.md). Full human play, remote multiplayer and comparative FPS remain unverified. Manual launch scripts use separate profiles and `/home/jakub/devel/escapistsrereintroduced/.local/playtest-compat-20260920`, keep sound muted, and refuse an unfinished handoff. They have not been launched visibly by this refresh. The previous `playtest-2026-09-19` folder remains untouched.
|
||||
This is an **unqualified development candidate**: strict packaging/startup failures, human play, multiplayer, physical support reliability, comparative FPS and clean release qualification remain outstanding. Tests stayed hidden and muted. Prior packages and existing missions are preserved. [Start controls](mission-starts.md) · [Exact handoff evidence](evidence/playtest-refresh-2026-10-03-crash-start/README.md).
|
||||
|
||||
## First playable checks
|
||||
**3 October 2026 — depot-mines development handoff:** [package and editable source](../.build/playtest-2026-10-03-depot-mines/README.md).
|
||||
|
||||
Use the handoff's [short player route](../.build/playtest-2026-09-20/player-route.md) for prison → clues → radio → helicopter → results/restart. Check these migrated behaviors during that route:
|
||||
**423 authored files**, **364 exact PAK payloads** and **3 runtime files** match the editable source and handoff manifest.
|
||||
|
||||
- `/esc menu` works in Core itself. Test saved values, unfinished drafts surviving polls/page changes, normal Close/Escape behavior, and disabled controls for absent companions. Record each original setting and restore it after an Apply check; clock/date/weather choices apply next round.
|
||||
- With Intel loaded, `/esc intel show`, `/esc intel reroll` and `/esc intel reroll show` expose batch progress. Recovered folders and discovered locations must survive a reroll. Distinct recovered clues update team discovery feedback; repeatedly moving the same folder must not reveal another clue.
|
||||
- With AI loaded, check readable HQ journal entries, pause/resume, following at the bottom, and Jump to latest. Reports still need radio delivery before physical orders. Multi-target fairness needs a separate two-player observation: both targets remain visible to the same squad, and successive valid reports should not persistently favor only its first target. A solo run cannot establish that result.
|
||||
This snapshot adds ten finite startup PMN4 mines across five original camp caches. An existing original responder can carry one inert original mine to an existing ammunition truck after separately tracked mine expenditure; magazine expenditure cannot request mines. The loader also selects a compatible eligible porter from the original roster instead of letting an incompatible first member block magazine loading. Exact cargo identities, typed delivery proof, fixed deadlines and cancellation quarantine remain enforced. Earlier finite engineer-post reuse, compatible-stock supply, mine-flank safety and paired interception are included.
|
||||
|
||||
The full scenario retains its Chat entrypoint identity and loads Core, AI, Intel, Map and the thin Chat assembly. Chat administration is implemented in Core classes; the assembly is not required for the base menu.
|
||||
The unchanged authored source, tests and tools reuse the completed **301-program regression pass**; 3 later documentation-only differences are separately reviewed. The unchanged-source archived normal Everon route completes **64 assertions and 1 round**, with zero script/runtime failures and **13 retained engine errors**. The normal-route read-only stock witness confirms **ten distinct original inert PMN4s in five camp caches**; it does not prove courier travel or transfer. Ordinary startup of the exact new runtime bytes verifies the normal mission and local prisoner, with zero script/runtime failures and **17 retained engine errors**. Strict packaging/startup failures remain recorded.
|
||||
|
||||
## Build and retain the candidate
|
||||
This is an **unqualified development candidate**. Native repeated mining and route avoidance, mine placement/arming/detonation, physical resupply/interception and survivor retasking remain unverified, as do complete human escape, real multiplayer/JIP/reconnect/twelve-player play, manual UI behavior, comparative FPS and a clean release. An intermittent zero-radius engine diagnostic remains unresolved; the opt-in trace preserves native behavior and is not a fix or proof of the caller. Qualification binds the exact tested depot-mines snapshot. Concurrent welcome-voice additions and later source or test changes, including the BMP sampler correction, are preserved live but excluded from this frozen handoff and its qualification. Earlier packages and original missions remain preserved.
|
||||
|
||||
Run these commands from `/home/jakub/devel/escapistsrereintroduced`, after the intended gameplay changes are frozen and the private runtime is idle. The existing runner owns its hidden display, muted audio, disposable source copy/profile and prefix lock. Do not run another native test alongside it.
|
||||
## Previous ground-supply handoff (historical)
|
||||
|
||||
**3 October 2026 — ground-supply development handoff:** [package and editable source](../.build/playtest-2026-10-03-ground-supply/README.md).
|
||||
|
||||
**423 authored files**, **364 exact PAK payloads** and **3 runtime files** match the editable source and handoff manifest.
|
||||
|
||||
This snapshot adds finite engineer reuse at genuinely newer radio-delivered road posts: four consumed attempts per original force and thirty-two per mission, with every new post more than 160 m from consumed posts. Original stock, native movement envelopes, fixed deadlines and unresolved-removal quarantine remain intact. Ordinary small-arms supply now refuses trucks lacking compatible nonempty original magazines before spending a report or claiming forces. Earlier mine-flank safety, paired interception and player-recovery changes remain included.
|
||||
|
||||
The unchanged authored source, tests and tools reuse the completed **300-program regression pass**; 2 later documentation-only differences are separately reviewed. The unchanged-source archived normal Everon route completes **63 assertions and 1 round**, with zero script/runtime failures and **13 retained engine errors**. Ordinary startup of the exact new runtime bytes verifies the normal mission and local prisoner, with zero script/runtime failures and **17 retained engine errors**. Strict packaging/startup failures remain recorded.
|
||||
|
||||
This is an **unqualified development candidate**. Native repeated mining and route avoidance, mine placement/arming/detonation, physical resupply/interception and survivor retasking remain unverified, as do complete human escape, real multiplayer/JIP/reconnect/twelve-player play, manual UI behavior, comparative FPS and a clean release. An intermittent zero-radius engine diagnostic remains unresolved; the opt-in trace preserves native behavior and is not a fix or proof of the caller. Qualification binds this frozen snapshot; later live edits are excluded. Earlier packages and original missions remain preserved.
|
||||
|
||||
## Previous mine-safety handoff (historical)
|
||||
|
||||
**3 October 2026 — mine-safety development handoff:** [package and editable source](../.build/playtest-2026-10-03-mine-safety/README.md).
|
||||
|
||||
**422 authored files**, **363 exact PAK payloads** and **3 runtime files** match the editable source and handoff manifest.
|
||||
|
||||
This snapshot adds engineer mine flanks with at least 15 m clearance from nearby road centerlines and more than 200 m from named settlements. Mine dispatch also respects the group’s current native movement envelope before starting and throughout the job. Original items, fixed deadlines and cancellation quarantine remain intact. Earlier paired interception, finite supply and player-recovery changes remain included.
|
||||
|
||||
The unchanged authored source, tests and tools reuse the completed **299-program regression pass**; 2 later documentation-only differences are separately reviewed. The unchanged-source archived normal Everon route completes **63 assertions and 1 round**, with zero script/runtime failures and **13 retained engine errors**. Ordinary startup of the exact new runtime bytes verifies the normal mission and local prisoner, with zero script/runtime failures and **17 retained engine errors**. Strict packaging/startup failures remain recorded.
|
||||
|
||||
This is an **unqualified development candidate**. Native mine placement, arming and detonation, physical resupply/interception and survivor retasking remain unverified, as do complete human escape, real multiplayer/JIP/reconnect/twelve-player play, manual UI behavior, comparative FPS and a clean release. An intermittent zero-radius engine diagnostic remains unresolved; the opt-in trace preserves native behavior and is not a fix or proof of the caller. Qualification binds this frozen snapshot; later live edits are excluded. Earlier packages and original missions remain preserved.
|
||||
|
||||
## Previous mounted-pair handoff (historical)
|
||||
|
||||
**3 October 2026 — mounted-pair development handoff:** [package and editable source](../.build/playtest-2026-10-03-mounted-pair/README.md).
|
||||
|
||||
**420 authored files**, **361 exact PAK payloads** and **3 runtime files** match the editable source and handoff manifest.
|
||||
|
||||
This snapshot adds event-time capture cancellation for original active hunter vehicles, the current inherited terrain presentation, and paired radio interception by two original convoy escorts. Both real order receipts precede detours; finite forces, crew identities, stock and fixed deadlines are preserved. Earlier convoy-survivor, radio interruption and finite-transfer corrections remain included.
|
||||
|
||||
The unchanged authored source, tests and tools reuse the completed **294-program regression pass**; four later prose-only documentation updates are separately reviewed. The unchanged-source archived normal Everon route completes **63 assertions and 1 round**, with zero script/runtime failures and **13 retained engine errors**. Ordinary startup of the exact new runtime bytes verifies the normal mission and local prisoner, with zero script/runtime failures and **17 retained engine errors**. Strict packaging/startup failures remain recorded.
|
||||
|
||||
This is an **unqualified development candidate**. Native survivor radio delivery and physical retasking remain unverified, as do physical resupply/interception, complete human escape, real multiplayer/JIP/reconnect/twelve-player play, manual UI behavior, comparative FPS and a clean release. Qualification binds this frozen snapshot; later live edits are excluded. Earlier packages and original missions remain preserved.
|
||||
|
||||
## Previous convoy-survivors handoff (historical)
|
||||
|
||||
**2 October 2026 — convoy-survivors development handoff:** [package and editable source](../.build/playtest-2026-10-02-convoy-survivors/README.md).
|
||||
|
||||
**420 authored files**, **361 exact PAK payloads** and **3 runtime files** match the editable source and handoff manifest.
|
||||
|
||||
The snapshot retains eligible original enemy convoy survivors in their existing HQ registration when travel or boarding ends. Exact ownership, roster and force identity still apply; no new soldiers, equipment or contacts are created. Radio-hop interruption, finite-transfer cancellation and deleted-mortar-shell fixes remain included.
|
||||
|
||||
The exact source passes **291 registered regression programs**. The unchanged-source archived normal Everon route completes **63 assertions and 1 round**, with zero script/runtime failures and **13 retained engine errors**. Ordinary startup of the exact new runtime bytes verifies the normal mission and local prisoner, with zero script/runtime failures and **17 retained engine errors**. Strict packaging/startup failures remain recorded.
|
||||
|
||||
This is an **unqualified development candidate**. Native survivor radio delivery and physical retasking remain unverified, as do physical resupply/interception, complete human escape, real multiplayer/JIP/reconnect/twelve-player play, manual UI behavior, comparative FPS and a clean release. Qualification binds this frozen snapshot; later live edits are excluded. Earlier packages and original missions remain preserved.
|
||||
|
||||
## Previous transfer-fixes handoff (historical)
|
||||
|
||||
**2 October 2026 — transfer-fixes development handoff:** [sealed package manifest and editable source](../.build/playtest-2026-10-02-transfer-fixes/handoff.json).
|
||||
|
||||
**420 authored files**, **361 exact PAK payloads** and **3 runtime files** match the sealed source.
|
||||
|
||||
This snapshot includes the radio-hop interruption checks, cancellation guards for finite supply transactions, and the deleted-mortar-shell settlement fix. Earlier terrain/admin integration and bounded HQ travel-history planning remain included.
|
||||
|
||||
The exact frozen source passes **290 registered regression programs**. The normal Everon route completes **63 assertions and 1 round**, with zero script/runtime failures and **13 retained engine errors**.
|
||||
|
||||
Ordinary startup verifies the normal mission and local prisoner with zero script/runtime failures and **17 retained engine errors**. Strict packaging/startup failures remain recorded; this is an **unqualified development candidate**.
|
||||
|
||||
Qualification covers this frozen snapshot, not later live edits. Physical resupply/interception, manual UI behavior, complete human escape, real multiplayer/JIP/reconnect/twelve-player play, comparative FPS and a clean release remain unverified. Existing packages and original missions remain unchanged.
|
||||
|
||||
The current project is **Co10 Escape Reintroduced**, `ERR_Core`, GUID
|
||||
`2528466DE220D91C`, in `addons/core/addon.gproj`. Mission, AI, Intel, Map and Chat
|
||||
are included in this one addon. There are no separate companion projects to
|
||||
build or enable. See [the combined layout](single-mod.md).
|
||||
|
||||
## Earlier handoff (historical)
|
||||
|
||||
The previously retained handoff was [2 October — HQ travel memory](../.build/playtest-2026-10-02-hq-memory-menu-fix/README.md), at `.build/playtest-2026-10-02-hq-memory-menu-fix`.
|
||||
|
||||
409 authored files, 351 exact PAK payloads and three runtime files match editable source and `handoff.json`. A startup guard now skips automatic terrain takeover in mode-less menu worlds; ordinary supported scenarios and unsupported-mode diagnostics keep their existing behavior. This snapshot includes observer recovery/defeat guidance, finite resupply of supported reloadable launchers, and one original armed convoy escort receiving a radio interception order ahead of delivered player travel history. Earlier finite logistics, controller ownership and authored discovery/mine-warning map presentation remain included. The frozen snapshot includes the earlier parallel task’s automatic terrain takeover behavior; newer concurrent terrain-name/presentation edits remain in the live workspace and are not in this package; this handoff’s fresh scripted route targets Everon.
|
||||
|
||||
All **285 registered regression programs pass**. The fresh normal-route fixture completes **63 assertions and one round**, with zero script/runtime failures and thirteen retained engine errors. Fresh ordinary startup of this exact package verifies the normal mission and local prisoner with zero script/runtime failures and 17 retained engine errors. Strict packaging/startup failures remain recorded.
|
||||
|
||||
This is an **unqualified development candidate**. Physical launcher delivery, native interception movement/holding/rejoining, a complete human escape, real multiplayer/JIP/reconnect/twelve-player play, comparative FPS and a clean release remain unverified. Historical standard-map visual checks do not prove physical held-map rendering or current remote UI behavior. No new native flight or prison-input experiments are included.
|
||||
|
||||
See [current status](current-status.md). The earlier objective-map package and all previous candidates remain unchanged. Later source edits are not automatically present in this snapshot.
|
||||
|
||||
## Identities and required dependencies
|
||||
|
||||
| Role | Project or dependency | GUID |
|
||||
| --- | --- | --- |
|
||||
| Single successor addon | ERR_Core / Co10 Escape Reintroduced | `2528466DE220D91C` |
|
||||
| Direct base dependency | Arma Reforger | `58D0FB3206B6F859` |
|
||||
| Direct external dependency | RHS: Status Quo | `595F2BF2F44836FB` |
|
||||
| Direct external dependency | WCS Armaments | `629B2BA37EFFD577` |
|
||||
| Direct external dependency | WCS BMP-1 | `5E524E4FEECCA92B` |
|
||||
| Direct external dependency | Parachute Framework | `65930CB4CD0237B2` |
|
||||
| Transitive external dependency | RHS Content Pack 01 | `1337C0DE5DABBEEF` |
|
||||
| Transitive external dependency | RHS Content Pack 02 | `BADC0DEDABBEDA5E` |
|
||||
| Transitive external dependency | WCS SpaceCore | `5E389BB9F58B79A6` |
|
||||
|
||||
Install the seven external addons separately. The audited versions, descriptor
|
||||
hashes and dependency graph are in [external-addons.json](external-addons.json);
|
||||
a source bundle includes this as `EXTERNAL-ADDONS.json`. The private runners
|
||||
expose only that audited closure. Original Escapists and its extensions are not
|
||||
part of the successor's dependency graph. Third-party assets are not bundled.
|
||||
|
||||
The normal scenario is `{C1E20667DCE324ED}Missions/ERR_Everon.conf`
|
||||
(“Co10 Escape Reintroduced — Automatic terrain”). Diagnostics use the same
|
||||
entry. The duplicate Base header was removed from current source on 2026-10-04;
|
||||
older frozen packages still contain it and are not the current publishing input.
|
||||
|
||||
## Build from frozen source
|
||||
|
||||
Run from `/home/jakub/devel/escapistsrereintroduced`. Replace the example prefix
|
||||
and installed-addon paths below, and use fresh names for every private session,
|
||||
profile and output ZIP. The compatibility directory must be an existing idle,
|
||||
disposable Tools prefix under `/tmp`, not the installed Steam prefix.
|
||||
|
||||
```sh
|
||||
python3 tools/native_package.py --project chat \
|
||||
--session /tmp/erri-playtest-packages-20260920 \
|
||||
--compat /tmp/erri-headless-compat --timeout 300 \
|
||||
--silent-workbench --continue-on-failure
|
||||
ERRI_COMPAT=/tmp/YOUR-IDLE-DISPOSABLE-TOOLS-PREFIX
|
||||
ERRI_EXTERNAL=/path/to/installed/workshop/addons
|
||||
|
||||
python3 tools/headless_game.py --compat "$ERRI_COMPAT" --inspect-processes
|
||||
python3 tools/check.py
|
||||
```
|
||||
|
||||
`chat` builds **Core, AI, Intel, Map, Chat** in that order. Each output is already at `session/packages/<folder>/{addon.gproj,data.pak,resourceDatabase.rdb}`. No repacking or dependency-assembly tool is needed. Sessions must be new; never overwrite a failed run to reuse its name.
|
||||
The inspection is read-only. If a game, Tools session or another native runner is
|
||||
active, leave it untouched and wait before building. The existing runners manage
|
||||
their own hidden display, muted audio, isolated source/profile, prefix lock and
|
||||
cleanup. Do not bypass their refusal or cleanup checks or launch another native
|
||||
job concurrently. They do not require opening windows on either physical monitor.
|
||||
|
||||
Known native packaging shutdown resource/UI errors also reproduced in the empty-addon control. The runner retains those errors and its failed verdict; `--continue-on-failure` permits subsequent addon attempts without waiving them. It still stops for incomplete execution, unsafe cleanup or source changes. A failed build verdict is not a clean build, but inspected artifacts that subsequently pass packed startup can be supplied for this explicitly limited development playtest. See [packaging control](native-packaging-control.md).
|
||||
|
||||
Create the separate editable source ZIP while the same source is frozen:
|
||||
With source frozen, package the one project:
|
||||
|
||||
```sh
|
||||
python3 tools/native_package.py --project core \
|
||||
--session /tmp/erri-playtest-package-NEW \
|
||||
--compat "$ERRI_COMPAT" --external-addons "$ERRI_EXTERNAL" \
|
||||
--timeout 300
|
||||
|
||||
python3 tools/source_bundle.py --mode development \
|
||||
--output /tmp/erri-playtest-source-20260920.zip
|
||||
--output /tmp/erri-playtest-source-NEW.zip
|
||||
```
|
||||
|
||||
This is source only. Compare its `BUNDLE-MANIFEST.json` authored hashes with the packager's source snapshot before identifying it as the packages' matching source. The ZIP tool refuses an existing output and writes outside the checkout.
|
||||
The packager accepts `--project core`; the removed `--project chat` packaging
|
||||
recipe does not apply. Output is exactly
|
||||
`packages/core/{addon.gproj,data.pak,resourceDatabase.rdb}`. The ZIP is editable
|
||||
source only and must be written outside the checkout. Compare its
|
||||
`BUNDLE-MANIFEST.json` authored hashes against the packager's frozen source
|
||||
snapshot before describing it as matching source.
|
||||
|
||||
After reviewing the build and startup results, copy only the fifteen runtime files into the durable handoff's `packages/` directory. Also retain `source.zip`, these instructions, raw build/startup reports and logs, and artifact SHA-256 hashes in separate sibling paths. Keep reports, loose sources and generated caches out of `packages/`. Never redistribute installed vanilla/runtime files. Extract the matching ZIP into a new `source/` directory for the Tools workflow below.
|
||||
`--silent-workbench` and `--exit-after-init` are optional, mutually exclusive
|
||||
packager lifecycle experiments. `--continue-on-failure` is diagnostic only; it
|
||||
does not turn a failed build into a pass. Keep resource/localization, shutdown
|
||||
and cleanup failures in the retained reports. Native exit code 0 alone is not
|
||||
build qualification. See [packaging control evidence](native-packaging-control.md).
|
||||
|
||||
## Check those exact packed bytes
|
||||
## Check the normal route and exact packaged bytes
|
||||
|
||||
These existing commands perform **hidden, bounded startup checks**; they close their own game and are not human play launchers. Use the newly built package directory, not an older archive:
|
||||
These commands launch **hidden, muted, bounded diagnostics**, then close their
|
||||
own processes. They are not human play launchers. Run them sequentially while
|
||||
the frozen source and private runtime remain idle between jobs.
|
||||
|
||||
```sh
|
||||
python3 tools/headless_game.py --project core \
|
||||
--packed-core /home/jakub/devel/escapistsrereintroduced/.build/playtest-2026-09-20/packages/core \
|
||||
--packed-session /tmp/erri-packed-core-playtest-20260920 \
|
||||
--compat /tmp/erri-headless-compat --timeout 180
|
||||
python3 tools/headless_workbench.py \
|
||||
--compat "$ERRI_COMPAT" \
|
||||
--profile /tmp/erri-playtest-route-NEW \
|
||||
--external-addons "$ERRI_EXTERNAL" \
|
||||
--project chat --smoke normal-escape-route --rounds 1 --timeout 360
|
||||
|
||||
python3 tools/headless_game.py --project chat \
|
||||
--packed-addons /home/jakub/devel/escapistsrereintroduced/.build/playtest-2026-09-20/packages \
|
||||
--packed-session /tmp/erri-packed-chat-playtest-20260920 \
|
||||
--compat /tmp/erri-headless-compat --timeout 180
|
||||
--packed-addons /tmp/erri-playtest-package-NEW/packages \
|
||||
--packed-session /tmp/erri-packed-chat-playtest-NEW \
|
||||
--compat "$ERRI_COMPAT" --external-addons "$ERRI_EXTERNAL" \
|
||||
--timeout 180 --failure-grace 120
|
||||
```
|
||||
|
||||
Their default fifteen-second readiness interval must remain unchanged. Retain both complete private sessions, including provenance, raw console, exact copied inputs and cleanup results. Match all fifteen hashes again after copying to the durable handoff. Packed startup proves loading and local admission; it does not prove a complete human escape, remote multiplayer or performance.
|
||||
Workbench `core` and `chat` select diagnostic fixture families, not different
|
||||
addon projects. Both need the external dependencies. `normal-escape-route`
|
||||
checks the normal generated Everon catalog; the older `escape-route` uses its
|
||||
fixture catalog. Scripted movement/actions do not establish human walking,
|
||||
interaction, combat or piloting.
|
||||
|
||||
## Open the editable mission in Tools
|
||||
The ordinary packed command uses schema 4: one successor addon plus seven
|
||||
external addons, ten engine/vanilla/mod/dependency mounts altogether. Keep its
|
||||
default fifteen-second readiness interval. `--failure-grace 120` only retains a
|
||||
failed run for additional logs within the original timeout; it does not waive a
|
||||
failure. Historical `--packed-core`, vanilla Chat v2 and five-addon external v3
|
||||
results do not validate this combined dependency graph.
|
||||
|
||||
Installed Tools executable: `/home/jakub/.local/share/Steam/steamapps/common/Arma Reforger Tools/Workbench/ArmaReforgerWorkbenchSteamDiag.exe`. Open **Arma Reforger Tools through the existing desktop/Steam workflow** when ready to play, rather than using a hidden diagnostic runner.
|
||||
After reviewing both results, retain a new handoff with only the three runtime
|
||||
files inside `packages/core/`. Keep matching `source.zip`, extracted `source/`,
|
||||
raw reports/logs, provenance, cleanup results and SHA-256 hashes in separate
|
||||
sibling paths. Verify all three runtime hashes after copying. Never overwrite a
|
||||
previous candidate or mix newer loose source with an older PAK. Packed startup
|
||||
proves loading, normal mission readiness and local admission; it does not prove
|
||||
remote multiplayer or a full human escape.
|
||||
|
||||
Configure the extracted `source/addons` as the addon search directory. Open `source/addons/core/addon.gproj` for the base mission or `source/addons/chat/addon.gproj` for all five addons. Use the normal World Editor play workflow for `Worlds/ERR_Everon.ent`. Do not enable smoke plugins or pass any `errSmoke`, `errBaseSmoke`, input-exercise or aircraft-fixture flags. Editor play is an editable-source workflow; use the regular game and the scenario header below to test the packaged ordinary mission.
|
||||
## Human playtest
|
||||
|
||||
## Ordinary game launch options
|
||||
Use the matching handoff's `source/addons/core/addon.gproj` for editable Tools
|
||||
work, with its installed external dependencies registered. Select
|
||||
`Missions/ERR_Everon.conf`. For packaged play, enable the single successor addon
|
||||
and its required dependencies in a separate playtest profile, then select that
|
||||
normal scenario. Use the mission header/scenario workflow, not a bare world
|
||||
load. The old five-addon launch scripts and Chat GUID `FA804F411BDDF2C6` are
|
||||
historical and must not be used for the current combined package.
|
||||
|
||||
Installed regular game: `/home/jakub/.local/share/Steam/steamapps/common/Arma Reforger/ArmaReforgerSteam.exe`; installed Proton: `/home/jakub/.local/share/Steam/steamapps/common/Proton - Experimental/proton`. Use the existing normal visible game/Proton launch workflow, with a **separate playtest profile**, passing one of these argument sets. These are arguments, not shell commands that execute the Windows binary directly. `Z:` is the installed Wine mapping for these Linux paths.
|
||||
A visible human session is separate from the hidden commands above. Keep it on
|
||||
the user's chosen right monitor and muted, and quit normally before another
|
||||
native build or test. Do not enable smoke plugins, `errSmoke`/`errBaseSmoke`,
|
||||
input exercises or aircraft-fixture flags for ordinary play. This guide does not
|
||||
supply a new visible launcher or multiplayer server configuration.
|
||||
|
||||
Prepare the two local profile discovery links after the new handoff directory exists. The build owner also prepares the separate local playtest compatibility directory while native testing is idle. These commands write only inside that handoff; they do not alter installed vanilla assets. If either link already exists, inspect it instead of replacing it. This mirrors the existing startup runner's private-profile setup.
|
||||
Follow [the current player route](player-route.md): prison → scavenging/clues →
|
||||
radio defence → helicopter → result/restart. `/esc menu`, Intel commands and the
|
||||
HQ journal are included in the combined addon. Restore settings changed during
|
||||
admin checks. Record the exact candidate, scenario, point of failure and profile
|
||||
log session. Remote joins/reconnects, partial escape, twelve connected players,
|
||||
full human completion and comparative FPS still need their own evidence.
|
||||
|
||||
```sh
|
||||
ERRI_PLAYTEST=/home/jakub/devel/escapistsrereintroduced/.build/playtest-2026-09-20
|
||||
mkdir -p "$ERRI_PLAYTEST/profile-core/addons" "$ERRI_PLAYTEST/profile-chat/addons"
|
||||
ln -s '/home/jakub/.local/share/Steam/steamapps/common/Arma Reforger/addons/data' "$ERRI_PLAYTEST/profile-core/addons/ArmaReforger"
|
||||
ln -s '/home/jakub/.local/share/Steam/steamapps/common/Arma Reforger/addons/data' "$ERRI_PLAYTEST/profile-chat/addons/ArmaReforger"
|
||||
```
|
||||
## Retained candidate evidence
|
||||
|
||||
Base only:
|
||||
The 30 September installed-slot candidate contains 376 matching authored addon
|
||||
files, 321 matching PAK payloads and three verified runtime files. Its normal
|
||||
route completes 55 scripted assertions through extraction/results, with zero
|
||||
script/runtime failures and thirteen installed-resource errors. Its
|
||||
[ordinary packed startup](evidence/packed-2026-09-30-installed-slot/packed-startup-report.json)
|
||||
verifies normal mission readiness and a local prisoner, with zero script/runtime
|
||||
failures and seventeen installed-resource errors. Both strict verdicts remain
|
||||
failed. [Packaging](evidence/package-2026-09-30-installed-slot/package-report.json)
|
||||
emitted matching files and exited 0 but retained localization and shutdown
|
||||
resource-leak errors. Consult the handoff README and hashes for its exact scope;
|
||||
later alarm/memory and mounted-ammunition source evidence does not update these
|
||||
packaged bytes.
|
||||
|
||||
```text
|
||||
-addonsDir Z:/home/jakub/devel/escapistsrereintroduced/.build/playtest-2026-09-20/packages -addons 2528466DE220D91C -profile Z:/home/jakub/devel/escapistsrereintroduced/.build/playtest-2026-09-20/profile-core -errOrdinaryScenario core -noSplash -noBackend -noSound -logconsole
|
||||
```
|
||||
## Historical five-addon handoffs
|
||||
|
||||
Full companion scenario:
|
||||
The vanilla-only `.build/playtest-2026-09-20` candidate was frozen at `5e74269`:
|
||||
216 authored files, five matching PAKs and fifteen verified runtime files. Its
|
||||
[build record](evidence/playtest-2026-09-20/build.json),
|
||||
[packed Core startup](evidence/packed-core-2026-09-20-playtest/report.json) and
|
||||
[packed full startup](evidence/packed-chat-2026-09-20-playtest/report.json) retain
|
||||
that snapshot's zero-error startup evidence. Native packaging/shutdown failures
|
||||
remained separate; human play, multiplayer and FPS were not qualified.
|
||||
|
||||
```text
|
||||
-addonsDir Z:/home/jakub/devel/escapistsrereintroduced/.build/playtest-2026-09-20/packages -addons FA804F411BDDF2C6 -profile Z:/home/jakub/devel/escapistsrereintroduced/.build/playtest-2026-09-20/profile-chat -errOrdinaryScenario chat -noSplash -noBackend -noSound -logconsole
|
||||
```
|
||||
|
||||
The explicit ordinary launcher requests the native mission **header and MissionSystems**, once from the main menu. Do not substitute a bare `-world` load. The two headers are `{AD62322D5213C440}Missions/ERR_Everon_Base.conf` (“Reintroduced: Everon Base (development)”) and `{C1E20667DCE324ED}Missions/ERR_Everon.conf` (“Reintroduced: Everon (development)”). These names also identify the authored scenarios in the normal scenario menu. This local/offline setup uses `-noBackend`; it is not multiplayer hosting instructions. `-noSplash` avoids the separately documented stock splash path. These playtest arguments keep audio muted as requested and send no automated input. Quit through the game's normal menu before running another build/test.
|
||||
|
||||
| Package folder | Project | GUID | Successor dependencies |
|
||||
| --- | --- | --- | --- |
|
||||
| core | ERR_Core | 2528466DE220D91C | none |
|
||||
| ai | ERR_Ai | 5192138CB9D5B911 | Core |
|
||||
| intel | ERR_Intel | D31039C7C53E348A | Core |
|
||||
| map | ERR_Map | 9AAEE9041D79809E | Core |
|
||||
| chat | ERR_Chat | FA804F411BDDF2C6 | Core, AI, Intel, Map |
|
||||
|
||||
Every project additionally requires installed vanilla Arma Reforger `58D0FB3206B6F859`; it is not bundled. Identities and command structure above match the current five projects, scenario headers and ordinary launcher. New package validation belongs to the reports for this handoff. The visible launch recipe still needs the human run itself; editing these instructions performs no native execution.
|
||||
|
||||
For the first session, test the ordinary prison → scavenging/documents → radio → helicopter → result/restart loop. Record the chosen scenario, where progression stopped, and the corresponding `profile-core/logs` or `profile-chat/logs` session. Retain known packaging errors separately from any gameplay failures. Remote joins/reconnects, twelve real players, full human completion and comparative FPS remain unqualified.
|
||||
|
||||
## This candidate's build record
|
||||
|
||||
The source snapshot contains 216 authored files from `5e74269`. All five PAKs, their project descriptors and the matching source ZIP pass exact content-hash comparison. Both packed startup checks pass from the durable handoff's files. The previous September 19 handoff remains unchanged.
|
||||
|
||||
The standard packaging job produced Core with native exit 0, then retained a failed completion verdict because an owned Wine helper remained until cleanup. Separate remaining-addon jobs used the identical source after strict idle verification. AI, Intel and Map produced complete outputs; the first Chat attempt was interrupted by an audio stream disappearing between observation and routing. That failed attempt produced no Chat payload. A narrow helper correction tolerates a failed operation only when a fresh listing proves the exact stream is gone; all 44 focused packaging tests pass. A fresh Chat-only retry produced the matching output. Original failure reports and the retry remain under `checks/packaging-original/` and `checks/packaging-chat-retry/`.
|
||||
|
||||
Native resource/UI shutdown errors remain unchanged relative to the previous Core packaging attempt. Neither the retry nor successful packed consumption waives those errors. This is a development playtest candidate with clean ordinary startup, not a clean native build or qualified release.
|
||||
The later [road-interception handoff](../.build/playtest-2026-09-20-road-interception/README.md)
|
||||
and [five-addon external workflow](packed-external-development.md) also describe
|
||||
an older layout. Their companion GUIDs, five-project build order, vanilla-only
|
||||
profile links and launch commands are not current instructions. Existing
|
||||
historical handoffs, source and failure records remain unchanged.
|
||||
|
||||
Reference in New Issue
Block a user