Combo judgement depends on time windows between inputs, not absolute time

What it is

A combo timing window judges whether a continuous sequence holds by the relative interval between two consecutive inputs, rather than requiring a press at some absolute instant on a global clock. A player can enter this sequence from a different starting state, a different animation playback speed, or a different network condition; as long as each subsequent input falls within an acceptable time relationship to the one before it, the combo should still resolve — the judgement is based on how long ago the previous input happened, not on which millisecond of system time the current input landed on.

Why it happens

A combo's sense of rhythm comes from the causal link between one action and the next — a player watches the prior action reach a certain point and decides, based on that, when to issue the next input. If adjudication is tied to an absolute instant, that instant is itself invisible to the player and constantly shifting with system state; network latency, frame-rate fluctuation, and branches inherent to the animation itself can all give an identical psychological intent from the same player a completely different result across different play sessions. A relative time window re-grounds this adjudication in exactly the abilities a player can actually control and practice — observing the prior action, choosing the next input, and sustaining an overall rhythm — rather than asking the player to guess at an engine-internal clock they have no way of perceiving. That is precisely why it can support a combo system that is stable and genuinely learnable through practice.

Where it stops holding

Rhythm games, or genres with an extremely strict synchronization requirement, can deliberately choose to use an external absolute reference such as a musical beat — there is nothing wrong with that design as such, provided it gives clear visual or audio feedback for players to align against that external reference, and provides a calibration mechanism to compensate for a given player's own perceptual delay. The existence of a relative window also does not mean the interval can stretch indefinitely: once the gap between two inputs has already exceeded what this sequence's own meaning allows — say, the character's animation state has long since moved on to a different phase — the system should actively reset the sequence judgement, so a stale input from long before cannot unexpectedly trigger an action the player never anticipated.

Applying it

• For each specific combo sequence, separately define the predecessor state it requires, the minimum and maximum allowed interval, whether input buffering is supported, and its cancellation rules — and test whether this judgement stays stable across every animation variant, such as different characters or different equipment.
• In a dedicated training mode, show players the actual rhythm between their inputs and the currently available timing window directly, rather than only telling them a given combo attempt "succeeded" or "failed."
• How to check: replay the exact same relative-timing sequence repeatedly across different frame rates, devices, and starting states. If the identical relative sequence produces inconsistent results across these conditions, the adjudication logic likely has some absolute-clock dependence that should not be there, and needs to be specifically tracked down.

Related

• Same group: 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 · W3.05.4 Input-history hints help explain combo failure
• Nearby: W3.02 Input buffering and forgiveness · W3.01 Input latency · W3.05 Chords, combos, and input windows
• Search terms: combo timing window · relative timing · input sequence · action chaining