18 KiB
Current development status
Updated 19 September 2026, 20:27. The new finite aircraft retention service now passes its first native route:40assertions, actual destination hold/contact landing/engine shutdown, zero captured errors, unchanged197-file source and verified cleanup. The first compiler failure remains archived; four status getters were corrected. The default-inert command maintenance hook compiles in this checkpoint and has offline lifecycle coverage; the airborne service Stop also passes42native assertions through retained control, frozen-point landing and engine shutdown. Actual empty-server maintenance and operational HQ aircraft remain separate qualification.
The explicit one-wheel prison selection path and independent raw-log validators are implemented and pass offline checks. Two native attempts remain failed before reaching selection: 201104 exceeded the unchanged0.35-degree camera-return threshold; 201352 refused changed private window/process identity. Neither sent a wheel or F. The documented exit-after-init packaging control reproduced the same25shutdown errors with an empty addon. Its original cleanup failure remains recorded alongside separate exact-prefix cleanup; packaging now uses the shared narrow cleanup adapter.
All seventeen first-release acceptance cases remain pending. The ordinary held lock action/full escape, real multiplayer, improved FPS and clean native packaging remain unqualified. Aircraft HQ activation also needs authored enemy aircraft/destinations and a useful field-length controller; the proven route remains approximately20m.
The route gain comparison measures one native20m route per gain: translation through arrival hold improved155.365→69.293seconds, and final target error improved0.130→0.099m. The candidate passed38assertions, physical contact landing and engine shutdown. This is an isolated flight-controller result, not an FPS comparison or operational HQ air support; the production callback bridge has separate native evidence, while retained-service qualification and longer routes remain pending.
Ordinary prison approach191750 now passes end to end using actual private mouse/W input:14turns,9walking pulses,4.741m path,27.199s native interval, stationary0.490m from the interior waypoint. A disposable2560x720 viewport provides pointer travel while retaining every containment/ownership check. No gate action was sent; the exact lock/context remains unselected from the final view. Earlier pointer-edge, cross-position-API, calibration-return and legacy-summary failures remain archived. The first physically completed route191342 has a separate hashed raw-log review, not a rewritten runner verdict. The later 194128 alignment attempt acquires the native gate context with the lock available, but does not select the lock; it remains failed. Read-only selected-action diagnostics precede any action cycling or heldF proof.
The relative-look observer now passes an ordinary Chat run: actual +24/−24 pixel input produced a measured 1.935° yaw response and return within 0.149°, with stationary body, then verified W/Tab input. Zero captured errors, source unchanged and cleanup confirmed. The earlier run remains failed because its independent checker assumed identical SAMPLE/READY milliseconds; its separate corrected review preserves the raw archive. The current-source Core attempt reached 292 assertions without errors but exhausted an undersized 180-second budget; its timeout remains a failure. The later 184647 run used a 600-second budget and completed both rounds with614 assertions; the earlier timeout remains failed. No gate interaction or full normal-input escape is qualified.
The primary deliverable is an independently authored replacement for the abandoned Escapists base mission, with companion behavior integrated through its interfaces. Five successor addon projects have their own identities, authored Everon sites and vanilla asset references. The first release targets up to twelve players completing prison → scavenging/intel → radio defence → helicopter extraction without the original mod or dependent extensions. Scripted development checkpoints exist; a dependable, manually playable multiplayer release is still unfinished.
Established development checkpoints
| Area | Evidence | Practical limit |
|---|---|---|
| Integrated base loop | Core 130347 completes two rounds, 612 assertions and zero errors, including canonical participant rejection/restored document recovery, rough/exact native markers, radio feedback, extraction and restart. Companion 131041 completes two rounds, 96 assertions and zero errors at its source snapshot. | Scripted local integration with deliberate state/position changes, not a normal-input escape. These earlier archives share their captured source snapshot; the new Core/companion/ordinary runs linked above qualify the later native-end correction. The earlier flight mechanism remains separately source-bound. Future addon edits require fresh qualification. Earlier failures remain archived. |
| Ordinary game startup | Chat 125906 loads all five addons in the regular game, verifies the header/MissionSystems and admits the real local controller to a living canonical prisoner, then observes a clean ready interval. Native screenshots show the real prisoner view and the correct escape objective; the stock-scale yard decal creates a larger irregular bare patch, with substantial wheat remaining. | Explicit diagnostic noSplash and a scoped standalone round-local identity; no complete ordinary route or remote identity proof. The latest bounded keyboard cycle described above passes with visible inventory, while the earlier failed cycles remain archived. Admission design. |
| Packed addon consumption | Packed Core 110729 passes ordinary startup from the archived project/PAK/resource database plus installed vanilla: exactly three expected addons, real canonical prisoner, a 15-second ready interval and zero captured errors. Package and log hashes are retained. | Artifact-bound startup with explicit noSplash; no loose successor addon was loaded. The artifact predates current mortar edits. Archived packed Chat 131942 passes startup from all five 1317 packages, with no loose successor source, a real prisoner and zero captured errors. All 151 PAK entries match the captured 183-file addon snapshot before the native-end correction; all fifteen runtime artifacts retain exact hashes. Native packaging remains unqualified: an empty-addon control reproduces the same UI resource-leak errors, without fixing or suppressing them. |
| Native game-over | Preparation 133847 and active 134044 each pass two rounds/21 assertions: actual inherited game-over, unchanged native data, one shutdown, cancelled preparation/tick/binding, inert stale callbacks and vanilla restart. | Local fixture; pending native preloads and real clients are not arranged. Existing successor extraction results remain covered by normal escape/restart regressions. |
| Prison and scavenging | Prisoner capacity uses one real player plus eleven physical characters, exact starter kits and native clue transfers. Prison boundary 100148 covers the gate/progression corrections. | Extra physical actors are not twelve connected clients. Native action completion and deliberately repositioned boundary crossings do not prove held input or walking through the gate/debris. Equipment scarcity and combat balance need playtesting. |
| Medicine and extraction casualties | Medical treatment demonstrates finite supplies and native recovery at its earlier snapshot. Casualty 102037 passes 101 clean assertions at the committed checkpoint: grounded-aircraft checks, real incapacitation, helper rejection, seat/LOS constraints, one owner-handshake load and idempotent stop. Native removal proves the inherited exit mechanism. | Casualty loading explicitly adapts helper membership and invokes action completion. Held input, real remote ownership, competing rescuers and disconnect/death/deletion races remain separate. The older medical snapshot retains its historical catalog errors. |
| Infantry and HQ | Actual perception response carries an original soldier's observation through both physical radio legs and HQ to a different original squad, which physically moves. Patrol/preemption/resumption are implemented. | The prisoner is arranged and temporarily protected. Broader combat and interrupted/captured support require additional qualification; no response force is created for this test. |
| Finite support | Mortar expiry verifies fresh native commitments followed by stale-report withholding without duplicate orders. Courier 095513 passes 154 clean assertions through actual radio, original-patrol walking, exact depot-shell delivery and patrol restoration. | Mortar observations are synthetic; impact accuracy and genuine late callbacks remain unproved. The new refresh now passes the bounded 112900 fixture: three actual radio updates, eight physical launches, native event completion, 19 surviving original shells and 25 seconds without replay. The current 114751 expiry regression also passes 48 clean assertions. 115232 crew registration proves all four physical crew receive their one Intel carrying roll after setup, then exercises inventory depletion/loss; broader support-loss checks remain separate. Courier depletion is arranged by physically sequestering the original 27 rounds, not firing or replacing them. Broader losses and multiplayer remain unqualified. |
| Aircraft mechanism | Flight 114504 passes 81 assertions with zero captured errors: signed actor-local collective consumption, native autohover, powered takeoff, five-second 7–9m hover, stable contact landing and an engine-off check with finite fuel. The same aircraft and living AI pilot remain inside the original physical limits. | Translation 120245 additionally passes 85 clean assertions for a fixed four-metre target, five-second hold and landing. The reusable production controller separately passes 123439, 37 assertions including actual post-spawn qualification and its own complete vertical operation. Airborne cancellation 124915 passes 39 assertions with retained control through contact landing and engine-off. The same reusable controller then passes fixed-target movement 130038, 38 assertions including a physical 2.9m translation and landing. These are isolated flight mechanisms; rotors still coast after engine shutdown. The fixed 20 m route now passes one unloaded flight, target hold, contact landing and engine-off with 38 assertions. Useful field-length navigation, operational HQ support, repeated-flight reliability and manual/multiplayer piloting remain unqualified. Earlier input, drift, hover and shutdown failures remain archived. |
| Shared field map | Map ownership 120633 passes native replacement-view, delayed-callback, mode-clear and spare/interrupted deletion checks. The fixture observes actual cleanup and waits for native component references to expire. | Camera restore authorization is observed; no public native render-state getter exists. Visible held-map usability, previously focused stock gadget callbacks and remote presentation remain separate. |
| Independent runtime controls | Archived packed Linux Chat 132456 compiles the integrated game scripts, loads all five packages and prepares the empty prison mission in an isolated network namespace. Its four resource errors also occur in the earlier vanilla control. All fifteen packed inputs remain unchanged. Vanilla ordinary 102533 reproduces the initial splash unknown-class error with exactly two vanilla addons and no successor. | No real dedicated client joined. The vanilla ordinary control remains failed despite entering the menu; it does not test scenario reload or input. Splash diagnosis. |
Immediate work
- Prove the ordinary player route. The inventory first-open path is now visibly demonstrated without its former slot errors. Next implement the bounded normal-input gate exercise, verify reopen/refresh/item transfer, and use normal document/map, radio and medical interactions; travel the authored route, board and pilot the actual extraction helicopter, and verify partial escape. Keep finite supplies, vanilla recovery and explicit round abandonment intact. Direct-completion fixtures cannot settle these usability questions.
- Extend the proven bounded flight mechanism. Signed actor-local collective and native autohover now pass vertical takeoff, hover, landing and engine-off checks. A bounded four-metre translation and one fixed 20 m route now pass too. Longer routes and operational HQ support still need implementation and native qualification. The reusable controller now passes a native vertical operation; airborne cancellation also passes; optional fixed-target movement now passes too. Operational allocation and useful field-length paths remain next; the later gain experiment shortened the sampled translation/hold interval to69.293s within the existing160s stage. Keep unqualified flight modes out of operational HQ support, retain failed observations, and re-run applicable integration checks after source changes.
- Establish real multiplayer behavior. Test accepted client identities, simultaneous/late joins, preload cancellation, reserved-body reconnect/expiry, spent lives, spectator streaming, remote task/map/radio/result updates and seat contention. Local controller injections and helper actors are not substitutes for connected clients.
- Broaden support-loss and observer checks. Refreshed full salvo, current expiry and late crew registration now have source-bound native evidence; wider support-loss regressions remain. Spectator reason messages and survivor-cycling guidance have been added and compiled; visible behavior and real-client streaming remain unverified. Exercise actual interrupted reports, captured/dead couriers, pending inventory callbacks and support losses. Preserve stock and original patrols; retain historical failures alongside source-bound successful regressions.
First-release qualification
The acceptance ledger still requires the complete ordinary escape loop, death/unconsciousness/recovery, reconnect/respawn/spectators, partial escape, defeat/restart, interrupted/stale reports, support/ammunition losses and duplicate-free cleanup with up to twelve connected players. A passed development checkpoint does not promote those pending cases.
Collect matched original/successor workloads with repeated client-frame and server-tick measurements. No FPS improvement is demonstrated; the comparison tool has synthetic regression evidence only. Complete provenance/dependency review, obtain a clean native build and satisfy the release checker. The packed Core startup is now demonstrated for its exact archived PAK, while the packaging shutdown/control failures remain unresolved and unqualified. The development source bundle provides editable projects; it is separate from that native candidate and from a qualified release. No release package is published.
Private test cleanup now verifies Proton’s trailing-slash prefix spelling, checks idle state under the shared lock, and reaps only positively identified adopted test-device helpers after owned shutdown. The latest companion and ordinary runs record verified cleanup. Earlier strict-byte idle checks could miss those helpers; their historical logs are retained unchanged.
Original missions remain untouched. Engine tests use private profiles/prefixes, hidden displays and muted test audio. RHS, additional terrains, complete original feature parity, alternate starts and distant-unit simulation remain later scope. The validation ledger preserves the detailed historical checkpoints and failures.