---
id: controller-input
status: active
supersededBy: []
lang: en
title: Traditional input devices
description: >-
  Controllers turn physical movement into game parameters; range, neutral
  position and feedback should agree.
intro: >-
  Controllers turn physical movement into game parameters; range, neutral
  position and feedback should agree. Each overview separates player actions,
  state changes and alternative rules. Examples are hypothetical design
  scenarios, not claims about a named game. A prototype check states an
  observable question for the next iteration. Existing detailed references
  remain separately linked from the direction map.
updatedAt: '2026-10-21'
sources:
  - title: 'MDN: Gamepad API'
    url: 'https://developer.mozilla.org/en-US/docs/Web/API/Gamepad_API'
    description: >-
      Input API documentation; actual controller capabilities require separate
      verification.
counts:
  families: 2
  branches: 2
  variants: 8
url: 'https://gamemechanics.pro/en/mechanics/controller-input/'
markdownUrl: 'https://gamemechanics.pro/content/mechanics/en/controller-input.md'
license: CC-BY-4.0
codeLicense: MIT
attribution: gamemechanics.pro contributors
provenance: >-
  Original bilingual editorial overviews authored for gamemechanics.pro on
  2026-10-20 and reviewed on 2026-10-21. Scenarios are hypothetical design
  examples; prototype checks describe work to perform, not completed playtests.
  Primary sources support the stated techniques and implementation context, not
  every proposed variant.
---
# Traditional input devices

Controllers turn physical movement into game parameters; range, neutral position and feedback should agree. Each overview separates player actions, state changes and alternative rules. Examples are hypothetical design scenarios, not claims about a named game. A prototype check states an observable question for the next iteration. Existing detailed references remain separately linked from the direction map.

## Mechanics and variants

<a id="mechanics"></a>

### 1. Gamepads, sticks and triggers

<a id="t283"></a>
id: t283
canonicalId: controller-input--t283
url: https://gamemechanics.pro/en/mechanics/controller-input/#t283

Sticks and triggers provide continuous values while buttons switch actions and modes without looking at the device.

#### Mechanic variants

<a id="t283-variants"></a>
- Dead zones separate rest from small movement. <a id="t283-v1"></a>
- Response curves alter precision near the center. <a id="t283-v2"></a>
- Analog triggers modulate action strength. <a id="t283-v3"></a>
- Remapping preserves meaning across different layouts. <a id="t283-v4"></a>

Design example: A light trigger pull draws a bow while a full pull completes preparation without automatically firing.

Prototype check: Test stick drift, reconnection and missing axes; an API name alone does not establish hardware capability.

- [MDN: Gamepad API](https://developer.mozilla.org/en-US/docs/Web/API/Gamepad_API)

### 2. Trackballs, wheels and rotary controllers

<a id="t285"></a>
id: t285
canonicalId: controller-input--t285
url: https://gamemechanics.pro/en/mechanics/controller-input/#t285

Rotary input controls relative change or angle, supporting continuous correction without a normal screen boundary.

#### Mechanic variants

<a id="t285-variants"></a>
- Relative rotation accumulates parameter changes. <a id="t285-v1"></a>
- Absolute angles select a dial position. <a id="t285-v2"></a>
- Inertia preserves motion after input stops. <a id="t285-v3"></a>
- Detents divide continuous travel into positions. <a id="t285-v4"></a>

Design example: A player turns a valve with a trackball, adjusting flow without moving a pointer to the screen edge.

Prototype check: Test direction, units and missed events during fast rotation, including devices with different step counts.

- [MDN: Gamepad API](https://developer.mozilla.org/en-US/docs/Web/API/Gamepad_API)

## Sources and examples

Sources support particular techniques or methodology, not every family variant. Design examples and mechanic combinations are illustrative.

- [MDN: Gamepad API](https://developer.mozilla.org/en-US/docs/Web/API/Gamepad_API): Input API documentation; actual controller capabilities require separate verification.