13 KiB
Current development status
Updated 19 September 2026. Current addon sources pass the local clean-runtime development gate: Core 130347 completes two scripted escape/restart rounds with 612 assertions; companion 131041 completes two with 96 assertions, both with zero captured errors. Ordinary Chat 125906 and actual fixed-target flight 130038 have the same addon-source manifest. The latest aircraft path adds bounded target movement to the independently authored controller; operational HQ aircraft routes remain unfinished. All seventeen first-release acceptance cases remain pending. The current 1317 packages pass ordinary Chat startup and isolated Linux empty-server preparation. Native packaging still fails with the known UI shutdown errors; Linux retains four installed-asset errors reproduced by its vanilla control. These are artifact-bound development observations, not release qualification.
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. The current Core, companion, ordinary startup and fixed-target flight archives share one exact addon-source snapshot. 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, remote identity or manual input proof. 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. Current 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 current addon source manifest; 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. |
| 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. Longer route navigation, operational HQ aircraft 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 | Current 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. Use normal gate, inventory, 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 now passes 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. Longer paths remain the next implementation step. 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.
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.