jakub
6a667d8deb
Include the current addon, terrain integrations, tools, regression tests and recorded development evidence.
3.4 KiB
Inventory injury display compatibility correction
The observed installed client reported seven UpdateHitZoneState argument errors after opening inventory. The retained excerpt contains only the inventory and error records. The SDK damage-state invoker supplies one argument, while the stock widget subscribes a callback whose second boolean default is not supplied by ScriptInvoker.
The successor now substitutes a one-argument callback in its mission only, forwarding explicitly to the existing native update with attachment refresh enabled. Native initialization and its batching flag stay unchanged. Owned subscriptions are removed on reinitialization, detach and destruction; callbacks from an old mode are inert. No health, damage or treatment behavior is changed. The independent review binds the exact source/test/patch hashes and confirms blood cannot also enter the character-hitzone registration branch.
Validation and limits
The actual-method focused regression passes; its unadapted baseline compiles and fails at the missing-boolean boundary. The initializer and invoker are test doubles, not native UI proof. The source bundle preview passes. The new test is registered as the 308th program.
The full suite passed 134 programs before the 135th, offline external packaging, failed with Disk quota exceeded in shared /tmp. Inputs remained unchanged. An outside-sandbox retry also failed; moving temporary files to a disk-backed scratch directory allowed most cases to run but correctly violated the existing requirement that synthetic compat prefixes reside under /tmp (three errors and one assertion failure). No guards were relaxed and no other task's temporary files were deleted. A complete 308-program pass is not claimed. The actual new adapter regression separately passes using disk-backed disposable compiler files.
Native compilation and BMP check loaded the unchanged current addon and completed 48 assertions before two explicit BMP fixture failures. It compiled this compatibility class but did not open or exercise the inventory injury widgets. Runtime callback delivery, rendered medical UI and multiplayer remain unverified. A bounded next-check plan is retained, not implemented or executed.
Separate native BMP finding
The original slot-4 BMP is now actually reached. Its snapshot is numerically valid but incomplete: 288 rounds, capacity 290, two chambered rounds; Armament_Empty.et fails mount-item-slot-mismatch. The log cannot distinguish a missing inventory item from a missing or different parent slot. Completeness and custody guards remain unchanged. Radio proof is not reached. The failed run retains all 15 error entries: two fixture failures and 13 previously known resource/engine entries. It confirms unchanged source/dependency inputs and hidden, muted cleanup.
Preservation
All 533 tracked original reference files, the five sealed development candidates, the staged diff and the installed successor runtime are unchanged. Only the new adapter, regression and test registration change executable inputs. The observed installed PAK differed from the pre-fix source in two Workbench diagnostics; it now also lacks this new adapter. The current installed package has not been patched or republished. No manual escape, multiplayer, physical BMP support, performance or clean-release qualification is added by this checkpoint.