Embed RHS 1.9 compatibility; record Workshop 0.0.141
continuous-integration/drone/push Build is passing
continuous-integration/drone/push Build is passing
This commit is contained in:
@@ -1,5 +1,93 @@
|
||||
# Current development status
|
||||
|
||||
**5 November 2026 — Workshop 0.0.141 published:** Escape now embeds the two
|
||||
RHS 1.9 script replacements, with the original RHS dependency retained and no
|
||||
separate compatibility addon required. Native compilation and normal player
|
||||
spawn passed; the uploaded PAK contains the exact tested replacements. Workbench
|
||||
confirmed upload and backend processing through its command-line updater.
|
||||
See [publication evidence](evidence/rhs-1.9-embedded-2026-11-05/README.md).
|
||||
Fresh checkouts must run the documented [RHS preparation](../compatibility/rhs-1.9/README.md).
|
||||
The WCS BMP-1 tyre issue remains unresolved in this release. The user confirmed
|
||||
the server starts after removing optional Cessna/Propeller Flight Core; no
|
||||
Propeller patch was made. Full multiplayer and vehicle handling remain unqualified.
|
||||
|
||||
**5 November 2026 — refreshed editable development handoff:** a new
|
||||
[source ZIP](/tmp/escapistsrereintroduced-development-source-20261105.zip)
|
||||
contains all **718 authored addon files**, including the recent HQ, objective and
|
||||
medical fixes. The existing bundler validates the dependency/resource closure;
|
||||
independent inspection verifies exact ZIP membership and every payload hash.
|
||||
This is editable source, not a compiled PAK, installed update or qualified release.
|
||||
The temporary ZIP may expire; its manifest and digest are retained in
|
||||
[the handoff evidence](evidence/development-source-2026-11-05/report.json).
|
||||
|
||||
Three existing stock/station checks passed. Bounded map, action and maintenance
|
||||
reviews found no demonstrated new defect. Native validation remains deferred:
|
||||
the private test prefix is absent, and the source Tools prefix has live processes,
|
||||
so it was left untouched. No windows were opened, no processes or audio changed,
|
||||
and nothing was installed or published. Manual/multiplayer/FPS acceptance remains open.
|
||||
|
||||
**5 November 2026 — strong injectors reject treatment with no benefit:** a
|
||||
conscious, nonbleeding player with only mild blood loss could be offered combat
|
||||
epinephrine even though its effect left that condition unchanged. Blood-only
|
||||
eligibility now uses the same native fainting threshold as the existing effect.
|
||||
Unconscious patients remain eligible for its waking effect, and bleeding,
|
||||
resilience loss and physical injury treatment remain available. Standard
|
||||
injectors, treatment strength and finite supplies are unchanged.
|
||||
|
||||
Seven affected medical/lifecycle regression programs pass on unchanged final
|
||||
inputs. The new actual-method case fails against the prior source; a separate
|
||||
control verifies unconscious treatment remains accepted. The earlier full-suite
|
||||
checkpoint predates this two-file code/test change. No engine run was attempted:
|
||||
the established private prefix is absent. Native consumption/animation, manual
|
||||
play, multiplayer and FPS remain unverified. Existing missions, installed builds,
|
||||
Git index and earlier evidence were preserved; nothing was published.
|
||||
[Fix, independent review and evidence](evidence/epinephrine-eligibility-2026-11-05/report.json).
|
||||
|
||||
**5 November 2026 — full offline integration check restored:** the complete
|
||||
repository validator passes on 1,229 unchanged recorded input files, including
|
||||
the earlier HQ recovery-hold and objective-guidance changes. Two stale test
|
||||
contracts were repaired: observer ownership doubles now expose the committed
|
||||
hint debounce/quiet-call interface, and preparation checks expect the committed
|
||||
120-second results countdown. Gameplay code and the countdown itself are
|
||||
unchanged by this continuation. Current terrain-takeover documentation agrees.
|
||||
|
||||
Initial sandbox socket, observer compilation and obsolete countdown failures
|
||||
remain archived. Independent base-loop reviews found no demonstrated defect in
|
||||
intel progression, radio occupancy or reconnect/partial-result identity. This is
|
||||
offline validation only. No engine was launched; this continuation did not change
|
||||
installed builds or publish. Manual escape, multiplayer and FPS acceptance remain open.
|
||||
[Exact inputs, failures and results](evidence/integration-check-2026-11-05/report.json).
|
||||
|
||||
**5 November 2026 — persistent objective guidance matches progression:** radio
|
||||
search instructions now explain keeping undeciphered documents and identifying
|
||||
other distinct non-radio sites first; starting clue markers do not count. This
|
||||
replaces the misleading promise that collecting more starting folders alone
|
||||
reveals the radio. The guidance stays conditional because the server owns the
|
||||
round's configured requirement. Identified-radio instructions and close-view
|
||||
identification remain available. The airborne extraction objective now states
|
||||
30 continuous seconds for all rescue transports, matching the current rule.
|
||||
|
||||
The player-route guide is updated. Four existing objective/intel/rescue checks
|
||||
pass unchanged on the recorded inputs. Only wording changed; native UI rendering,
|
||||
multiplayer and performance were not tested. No engine was launched, installed
|
||||
builds were not replaced, and the earlier HQ fix was preserved.
|
||||
[Evidence](evidence/objective-guidance-2026-11-05/report.json).
|
||||
|
||||
**5 November 2026 — depleted squads can receive their recovery hold:** HQ already
|
||||
planned a reserve hold after a withdrawal reached shelter, but its radio delivery
|
||||
gate rejected that order when the squad had no ammunition. Delivery now permits
|
||||
that hold only for a coordinated squad whose existing judgment still requires
|
||||
recovery. Ordinary tactical reserve and attack orders retain the ammunition gate;
|
||||
exact task identity, current belief, expiry and force-ownership checks still apply.
|
||||
|
||||
Nine focused HQ regression programs pass on unchanged relevant inputs, including
|
||||
actual delivery and coordinated-admission methods; the prior source compiles but
|
||||
fails the new recovery-hold assertion. Eight base-loop regressions also passed
|
||||
before the change. This is a source-only correction: native radio/physical movement,
|
||||
multiplayer and performance remain unverified. No engine was opened, and this
|
||||
continuation did not install, publish or alter original missions. Concurrent garage
|
||||
work was preserved. [Evidence](evidence/hq-recovery-reserve-2026-11-05/report.json).
|
||||
|
||||
**7 October 2026 — shorten the initial airport survey:** the latest live
|
||||
Chernarus log spent 48.5s between terrain-survey start and airport completion,
|
||||
then admitted the player after the prison/aircraft and client scene were ready.
|
||||
|
||||
Reference in New Issue
Block a user