Punch right

Purpose and current status

Implemented in legacy MotionIntentEngine.EvaluatePunches, this action emits a trigger for rapid horizontal extension of the corresponding arm. The current Runner has no punch command mapping.

Inputs and required joints

Core torso joints, the corresponding shoulder, elbow and wrist, valid calibration and monotonic capture time are required. Arm availability is independent by side. Losing an arm’s evidence clears its armed state and extension-impulse window.

Features and normalization

RightWristDistanceFromShoulder is wrist-to-shoulder distance divided by calibrated upper-arm length. Wrist distance-change velocity, elbow extension angular velocity and horizontal dominance also contribute. Angles use degrees; angular velocity uses degrees per second; distance-change velocity uses upper-arm lengths per second.

Default thresholds

These are legacy configuration values, not punch accuracy or measured processing latency.

Temporal rules and rearm

Crossing the elbow-extension velocity threshold retains a bounded impulse window. Armed state, distance, angle, wrist velocity, current impulse evidence and horizontal dominance must all qualify before one Triggered event is emitted. Sufficient retraction or elbow bend rearms the action. This is not a simple fixed cooldown.

Confidence and false-positive risks

Arm extension, out-of-plane movement, wrist tracking loss and conflicts with block posture need attention. The recognizer does not measure punching force or physical contact.

Validation and known limitations

MotionIntentEngineTests and legacy conditions were inspected. This is neither a current Runner gameplay feature nor a physically accepted action. Separate upper-body observability research is not a validation result for this punch implementation.