Internal VORIVOX development. Candidate package: remaining gates are listed under compatibility.
Develop without a physical range
Component mock mode
Enable Mock When Manifest Missing. In the Editor, you can generate hits with the mouse or a test script.
Mock Launcher
python3 -m pip install websockets
python3 tools/mock_launcher.py --manifest ./mock-launch.json
./MyGame.x86_64 \
--vorivox-manifest ./mock-launch.jsonHit scenario
Mock Launcher can be extended with a scripted sequence:
[
{"delay_ms": 700, "x_mm": 1250, "y_mm": 703},
{"delay_ms": 900, "x_mm": 1800, "y_mm": 900},
{"delay_ms": 500, "x_mm": 400, "y_mm": 300}
]Mock mode validates game integration, but it cannot replace testing on real hardware. Latency, calibration, and edge behavior must be verified on the physical target.
Teaching samples are scripts requiring a Unity scene and assigned references. Production needs pause/countdown guards, connection-loss handling, shot_id deduplication and listener disposal. Older samples may require adaptation; complete gameplay is not claimed.
Playground demonstrates the shared contract in a browser. It is not a Unity Player or a C# package test.