You press dodge while an attack animation is still playing. The character dodges a moment later, just as you decide to stay still. In some games, an input buffer can explain why a command seems to arrive after the moment you intended.
Think of a short pending request
An input buffer can retain an eligible command for a brief interval so it can be executed when the game permits the action. The exact rules are game-specific. Some actions may be buffered, some may not, and the permitted window can vary.
This is different from a general delay between a controller and a display. A late-looking action may reflect animation rules, network conditions, equipment latency or buffering. One unexpected dodge does not establish which mechanism caused it.
Use a repeatable test
In a safe practice area or training mode, choose one simple sequence. Press the second command once at several points during the first action and observe what happens. Then wait until the first action ends before pressing it. Keep other inputs out of the test.
If the game provides an input display, use it to compare the registered command with the visible action. Consult the game’s official documentation or patch notes for any stated buffering behaviour. Do not transfer a timing value from another title merely because both games use similar combat.
Replace repeated presses with an intention
Rapidly pressing the same button can make it harder to understand which command produced the next action. Practise a single deliberate press, then observe the result. If the game allows relevant settings, change one at a time and keep a note of the original value.
The aim is not to declare buffering good or bad. It can make tightly timed actions more forgiving while also requiring you to understand when a command remains pending. Learning that timing helps you respond to the game you are actually playing.