urt-rs / docs /research /QVM_GRENADE_EVENT_PREFIX.md
nmarshall's picture
qvm: grenade trajectory event prelude
96b1c5f
|
Raw History Blame Contribute Delete
1.23 kB

Constructed grenade through trajectory and event prelude

RE-679. Reproduce with python3 scripts/analyze_qvm_grenade_event_prefix.py; check with python3 scripts/test_qvm_grenade_event_prefix.py. The machine report retains source identity and bounded fixtures.

Actual285971 construction with277165/277125 allocation and276433 query feeds223157–223252. Actual27168 computes motion at explicit fixture clocks, source truncates each coordinate toward zero, and278138 rebases origin while clearing trajectory/delta. The callback sets type0 and flag32, encodes up through60317 (index5), publishes event55 via278003 and sets572. Independent whole-record/client-event oracles cover both event storage branches and both constructor modes. Optional client bindings and early/mid/fuse clock offsets are branch fixtures, not proven live callback scheduling. The run stops before223253 special damage selection; full explosion/damage and native collision remain unexecuted.

No original executable/full QVM/native collision/physics/rendering executes. Native responses and legal input domains are supplied or unverified where stated; full runtime/macOS/Linux Rust/Bevy/Solari gameplay remains open.