Input-history hints help explain combo failure

What it is

Input history displays recently issued directions and keys in time order, optionally marking which ones the system accepted, buffered, ignored, or rejected as failed. It solves a follow-on problem left by the previous three entries: no matter how sensibly the timing window, sequence forgiveness, and adjudication rules are designed, if a player cannot see what the system actually received at the moment an action fails, they have no way to connect that failure to any specific, correctable behavior — input history is what turns combo failure from a vague "it didn't come out" into a concrete sequence of events a player can inspect step by step.

Why it happens

The actual cause of a combo failure can be wrong order, a bad interval, incorrect character state, insufficient resources, or conflicting input — these causes differ substantially from each other, yet from the player's subjective experience, the result of "it didn't work" feels identical every time. Without input history, players can only blindly speed up or repeat presses to probe for the problem, an inefficient method that may never actually touch the real issue. A visible input sequence helps the player attribute this failure's outcome to one specific behavior they can genuinely change, and lets them form a testable hypothesis for the next attempt (say, "I pressed too early that time"). It is worth noting that this kind of feedback is not meant to expose every internal adjudication rule without reservation — showing the player what input the system actually received, and what step is currently missing from the sequence, is enough exposure to let the player adjust on their own.

Where it stops holding

Persistently displaying detailed input history on the match HUD can itself obstruct the view and add to the cognitive load a player has to manage in high-pressure moments, and in a competitive context, exposing the details of one's own input to an opponent who is spectating or reviewing a replay may constitute an unnecessary information leak. A better approach is usually to put detailed input history into a training mode, a pause screen, a post-match replay, or an on-demand expansion that appears only after a failed attempt, rather than leaving it floating on screen throughout a match. One point that must be held to without exception: the history shown must match the system's actual parsing result exactly — if the history says "this input was valid" while the system's own adjudication says it failed, that inconsistency damages a player's trust in the entire feedback system more than having no history at all.

Applying it

• Show the specific inputs a player recently issued, the actual relative interval between consecutive inputs, and the parsing result the system assigned to each, using status labels players can easily understand — "valid," "too early," "too late," "wrong order" — to distinguish different causes of failure, rather than one generic "failed" message.
• In training mode and post-match replay, let players step through this input history frame by frame, and give as specific and directly executable a correction as possible for the next attempt, rather than a generic "practice more" prompt.
• How to check: ask players to explain the cause of a failure using only this input history, then have them retry based on that explanation; if a player's explanation and the system's actual adjudication consistently fail to match, the problem lies in how the feedback itself is modeled and presented, and that layer should be fixed before touching the adjudication rules themselves.

Related

• Same group: W3.05.1 Combo judgement depends on time windows between inputs, not absolute time · W3.05.2 Narrow windows make combos viable only for high reaction speed · W3.05.3 Chord-order forgiveness determines whether novices accidentally trigger advanced skills
• Nearby: W2.04.3 Failure must be attributable to a specific action · W3.02 Input buffering and forgiveness · W6.03 Discoverable rules
• Search terms: input history · diagnostic feedback · combo training · actionable feedback