Input Rebinding Conflict Checker

Validate exported Unity Input Actions for duplicate paths, risky overlaps, and actions missing bindings.

We parse maps, actions, and bindings when you paste JSON, or simple Action: <path> lines in manual mode. Related: persistence generator, glyph mapper.

Unexpected end of JSON input

Issues: 0 · Bindings: 0

  • No conflicts detected (heuristic).
Full Markdown report
# Input binding conflict report
- **Source:** json
- **Parse error:** Unexpected end of JSON input
- **Bindings parsed:** 0
- **Issues:** 0
## Issues
## Bindings
| Map | Action | Path | Groups |
|-----|--------|------|--------|
Does this replace playtesting?
No. It catches structural issues in exported assets; edge cases still need device testing.
My JSON fails to parse — why?
Export the .inputactions asset as JSON from the Unity Input System; trimmed or hand-edited files may be invalid.
What about composite bindings?
We match full binding paths; composite parts may need manual review if you use complex composites.