input_map_manage(add_action) VALUE_OUT_OF_RANGE — deadzone outside [0,1]

[dsarno]

What telemetry is showing

Callers pass deadzone values outside the valid [0.0, 1.0] range. Observed tight-loop: 28 retries in 88 seconds from one UUID. Docstring does not state the constraint.

Scope

• Window: last 30 days
• Affected installs (7d): 5
• Affected installs (14d): 5
• Total matching events (lifetime in 90d retention): 37
• Platforms / versions: Darwin 2.5.1 (1), Windows 2.5.2 (1), Windows 2.5.1 (1), Linux 2.5.2 (1), Linux 2.5.0 (1)
• First seen: 2026-05-15 00:00 UTC
• Last seen: 2026-05-15 16:00 UTC

Error breakdown (last 30d)

Error code	Count	% of failures
VALUE_OUT_OF_RANGE	37	100%

Representative sample (anonymized)

  install 7e441b49…:  2026-05-15 16:00 UTC  input_map_manage(bind_event)  → VALUE_OUT_OF_RANGE
  install 7e441b49…:  2026-05-15 16:00 UTC  input_map_manage(bind_event)  → VALUE_OUT_OF_RANGE
  install 7e441b49…:  2026-05-15 16:00 UTC  input_map_manage(bind_event)  → VALUE_OUT_OF_RANGE
  install 7e441b49…:  2026-05-15 16:00 UTC  input_map_manage(bind_event)  → VALUE_OUT_OF_RANGE
  install fbf41e5d…:  2026-05-15 14:00 UTC  input_map_manage(bind_event)  → VALUE_OUT_OF_RANGE

Tracked as

F-004 (tier: action) — surfaced from godot-ai
telemetry by the dashboard's findings system.

Notes

Tight-loop trigger: single user x 28 in 88s = sustained struggle. Docs fix is cheap, file issue.

Reproduction

Not directly reproducible — surfaced from production telemetry. Logs and
traces would help diagnose. If this is a caller-side issue (LLM guessing
input shape), a docstring or error-message improvement may be the most
direct fix.

---

Surfaced from godot-ai-telemetry. Per privacy contract: customer_uuids
are anonymized to 8-char prefixes; specific paths and identifiers are
redacted.

[dsarno]

@claude fix