Include the current addon, terrain integrations, tools, regression tests and recorded development evidence.
14 lines
3.0 KiB
Plaintext
14 lines
3.0 KiB
Plaintext
Finite launcher resupply proposal (no target writes/native runs)
|
|
|
|
Apply fix.patch; 4 production files and 8 existing regression programs. No check.py registration required. baseline.json captures before working/index SHA256; source-manifest.json freezes proposed files. apply-check.log records successful check against current target.
|
|
|
|
Delivered complete ammunition reports now carry LauncherMuzzles: supported positive reloadable magazine-well presence even when a consumed round no longer has an inventory identity. Snapshot copies it; Valid bounds it to Members*32. Demand needs fresh full-member launcher sampling, positive supported muzzles, zero aggregate rounds and zero chambers. Unsupported/disposable/non-reloadable configurations cannot establish demand. Partial sampling remains unknown. Rifle and mounted planning run first, then launcher, then mine supply.
|
|
|
|
Only original existing positive-ammo finite truck magazines are eligible, using exact native magazine-well match, immutable original carrier attribution, native inventory access/custody and shared reservations/spent/replay/cooldown. Availability scans at most96*32 actor/magazine pairs; native runtime performance is unmeasured. Loaded identity, when present, requires exact reciprocal muzzle parent slot; native null storage is supported. Empty muzzle is valid when supported well and both reloadability checks pass. Launcher trips do not return speculative empty fired-round entities. No stock creation or replenishment changed.
|
|
|
|
Submitted unknown launcher moves keep exact truck and recipient claims through Stop. Inline Stop or ownership revocation cannot become success after native return. Exact destination proof/deletion resolves retained uncertainty without resubmission/refund. A terminal negative callback also settles only when pinned original source/destination managers remain unchanged and the item is still exclusively in its exact reciprocal original managed source slot. Detached, foreign, duplicate, unknown or changed-manager evidence cannot settle refusal.
|
|
|
|
Eleven focused actual-method programs pass (final-results.json and final-*.log). Prior original-Compatible and original-HQ-loop negative controls compiled and failed runtime assertions (red-controls.json). Earlier failed C++ adapter logs are retained separately; final-* logs are corrected current-source outcomes. Independent final schema review is requested from hq_memory_review. Native engine, actual projectile firing lifetime, full-suite and multiplayer acceptance remain untested here.
|
|
|
|
Installed evidence is retained in sdk-review.json/sdk-files.json, source hashes sdk-evidence.json. RPG7/GP25/M203 authored round resources are Projectile entities WITH native MagazineComponent and wells, not generated/default-only guesses. RPG75 is explicitly disposable/nonreloadable. Exact fired-round deletion timing is unknown and is not assumed. Existing production IssueMagazines already requests each admitted cargo weapon muzzle's default stock; this patch changes none of that random initial availability.
|