urt-rs / docs /research /QVM_WEAPON_SELECT.md
nmarshall's picture
qvm: weapon selection request
952b689
|
Raw History Blame Contribute Delete
1.43 kB

Weapon selection request gates and transition effects

RE-572. Reproduce with python3 scripts/analyze_qvm_weapon_select.py; check with python3 scripts/test_qvm_weapon_select.py. The machine report retains source identity and bounded fixtures.

Complete48798 runs through49025 with actual31691 slot search,29913 event queue and39552 timed torso. Before range/presence checks, state3 with a nonempty magazine blocks unless PS220 bit8 is set. Requested integer must be1..27; weapon state2 and state bit1 reject. A missing first16-slot match rejects.

Acceptance emits event30 parameter0, sets PS148=2, sets PS44=0 if the currently selected low-byte ID is0 else300, requests timed torso54, zeros PS204/188/196 and clears state bits64/8/512. Selection itself leaves active slot and every packed weapon record unchanged. Animation durations are supplied321,0 or−1 records; kind3 blocks torso mutation but not duration storage.

76 probes distinguish request validation from the lookup's wider equality contract and preserve unrelated state. Completion49028 and its fallback behavior are the next step; live weapon legality and native animation/audio playback remain open.

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.