BC-0252 · TROUBLESHOOTING
Editorial review 2026-09-27 · Official sources conflict
Playtest Controls Feel Different
When test controls feel different, compare the intended action separately from the physical input used to perform it. Check reachability, acknowledgement and movement response in an equivalent game state. A touch gesture and a keyboard hold may not express the same duration or direction, so do not start by changing the movement rule.
Symptom
An intended game action responds differently across observed input contexts.
Immediate action
Describe initiation, continuation and release before comparing the resulting movement.
Diagnostic branches
- The physical inputs express different hold or toggle behavior.
- Clarify the intended action contract before judging response equivalence.
- The target is covered or input is intercepted by an active view.
- Investigate reachability before movement logic.
- Equivalent input reaches the game but release behaves differently.
- Prepare a specific release-boundary repair and preserve successful initiation.
Least-destructive change
Compare existing controls without changing global speed or replacing the input scheme prematurely.
Retest
- Initiation and release are both checked.
- Equivalent game states and input intentions are recorded.
- A visual impression is not promoted into a measured physics claim.
Escalation
Retain the paired action record and actual input context when the mismatch remains unresolved; avoid unsupported device-wide conclusions.
Working notes
Write the action contract: what begins the action, what sustains it and what ends it. A button that toggles movement is different from one that requires a hold. Confirm what the current interface communicates before interpreting a short tap as a failed sustained action.
Observe whether the input reaches the game. Covered controls, an active menu or a gesture beginning outside the target can interrupt the action before movement logic is involved. Record what is visible without claiming a particular event-handler or browser defect.
Match game conditions before comparing response: starting position, movement direction and relevant obstacles. Compare whether the intended path can be followed, not only whether an animation seems faster. View size and camera framing can alter the impression of speed without establishing different world behavior.
A proposed repair should target the evidenced boundary: clarify hold versus toggle, make a reachable control, or adjust a confirmed response mismatch. Preserve other inputs and verify both initiation and release, including returning from an available menu.
Examples
- Input mismatch: creator holds a direction key; recipient briefly taps a displayed direction control. The observed travel distance does not yet compare equivalent sustained actions.
- Release check: movement starts correctly but continues after the input ends. Record the release boundary rather than requesting globally slower movement.