Animation Priority: The Hidden Rule That Decides Whether Combat Feels Fair

There's a moment in Dark Souls that every player remembers. You press the roll button. Your character doesn't roll. You get hit. You die.

You press the estus flask button. Your character does nothing. You get hit. You die.

You press attack. Your character swings. The enemy swings at the same time. Your attack lands first. The enemy flinches. You live.

What decided those outcomes? Not your reflexes. Not your timing—at least, not entirely. What decided them was animation priority: a set of rules that determines which actions can interrupt which other actions, and in what order.

This is the hidden grammar of combat. It's what makes a game feel "responsive" or "sluggish," "fair" or "cheap," "tight" or "floaty." And it's almost never explained to the player.

I. The Sensation

You know the feeling. You're in the middle of a fight. You see an enemy wind up for an attack. You press dodge. Nothing happens. You take damage. And you think: "I pressed the button. Why didn't the game respond?"

Or the opposite: You're mid-swing. The enemy attacks. Your attack lands first—just barely—and interrupts them. You think: "I got lucky." But you didn't. The game decided, in that split second, that your attack had priority over theirs.

Or you're healing. You press the button, and your character slowly—too slowly—raises the flask to their lips. The enemy closes the distance. You can't cancel. You can't dodge. You're committed. You die.

That feeling—the feeling of being locked into an animation, or of being able to break out of one—is the direct, visceral result of animation priority rules. It's not about lag. It's not about input buffering. It's about what the game allows you to do, and when.

II. The Suspected Machinery

Animation priority is a hierarchy. At its simplest, it looks something like this:

1. Interruptible animations can be canceled by certain inputs—usually dodge or block.

2. Non-interruptible animations must play out completely before any new action can begin.

3. Hyper-armor animations can't be interrupted by enemy attacks, though they may still take damage.

4. Invincibility frames (i-frames) override collision detection entirely during specific animation segments.

But the real complexity lies in how these rules interact.

Attack Priority: The Frame Race

When two characters attack simultaneously, the game must decide whose attack lands first. This is typically determined by:

• Startup frames: How many frames pass between button press and hitbox activation.

• Active frames: How long the hitbox remains dangerous.

• Recovery frames: How long the character is vulnerable after the attack.

A weapon with a 10-frame startup will consistently beat a weapon with a 15-frame startup—provided both players press the button at the same time. This isn't a matter of "skill" in the traditional sense; it's a matter of knowing the game's hidden frame data.

But it's not just startup frames. Some attacks have priority flags that override the usual timing rules. In Elden Ring, certain boss attacks have an "input-reading" property—they begin their attack animation in response to the player pressing heal, not before. The game isn't reading your controller inputs in the sense of cheating; it's responding to the state change of your character entering a heal animation. The boss's attack priority is effectively "when the player heals, I attack immediately."

Input Buffer and the Queue

Most modern action games use an input buffer: a queue that stores your button presses for a few frames, even if the character isn't ready to act yet. In Monster Hunter, this buffer is generous—you can queue a dodge during a long attack animation, and the dodge will execute the moment the attack ends.

But the buffer has limits. If an animation is non-interruptible, the buffer can't override it. The game will store your input, but it won't execute it until the current animation finishes. In Dark Souls, the estus flask animation is notoriously non-interruptible for the first few frames—press dodge during those frames, and the input buffer may not save you.

This is where the frustration lives. The game registered your button press. It just didn't allow you to act on it yet.

Hyper-Armor vs. Poise

Some games use a poise system: a hidden stat that determines whether an attack will stagger you. In Elden Ring, poise is a number—high poise means you can take a hit without being interrupted. Low poise means you'll flinch.

Hyper-armor is different. It's a property of a specific animation, not a character stat. When an enemy is in a hyper-armor state, it simply ignores your attacks—no stagger, no flinch, no interruption. The game is telling you: "You cannot stop this attack. Your only option is to avoid it."

Bosses in Elden Ring frequently use hyper-armor during their "cinematic" attacks—the ones with huge wind-ups and devastating payoff. The design intention is clear: these attacks are meant to be solved, not traded against. If you try to interrupt them, you'll fail, because the game has hard-coded that failure.

III. Field Test

I tested this across three games: Dark Souls III, Elden Ring, and Monster Hunter Rise. The methodology was deliberately simple:

• Test 1: Press attack and dodge simultaneously. Record which action takes priority.

• Test 2: Attempt to heal mid-enemy-windup. Record whether the heal completes before the attack lands, and whether it can be canceled.

• Test 3: Trade blows with an enemy. Record which character's attack lands first and whether either flinches.

Dark Souls III was the most rigid. The input buffer exists but is tight—miss the window to cancel an animation, and you're committed. Healing is a death sentence at close range because the non-interruptible frames are long enough for most enemies to close the distance.

Elden Ring introduced more flexibility—some weapon arts have hyper-armor, allowing you to trade blows more aggressively—but the estus flask remains non-interruptible for the first 15 frames, preserving that classic Souls tension.

Monster Hunter Rise is a different philosophy entirely. You can roll out of almost any animation, and the input buffer is generous enough to queue actions predictively. The challenge isn't in committing to animations; it's in positioning so you don't need to cancel them.

IV. Competing Explanations

It's tempting to call animation priority a "difficulty" setting—the tighter the rules, the harder the game. But that's incomplete.

Explanation A: It's about risk/reward. Games with high commitment—long, non-interruptible animations—reward knowledge and prediction over twitch reflexes. The "skill" is in knowing when it's safe to act.

Explanation B: It's about genre expectations. Monster Hunter is a game about stamina and positioning; you're not supposed to be animation-locked, because the challenge comes from resource management. Dark Souls is a game about consequence; every action must have weight.

Explanation C: It's emergent. Some animation priority rules aren't "designed" in the sense of intentional difficulty—they're artifacts of the animation system itself. A 20-frame startup might exist because the attack animation looks right at 20 frames, not because the designer wanted to punish players.

All three are true, depending on the game and the specific attack. But they all point to a deeper truth: animation priority is the language of consequence in combat. Whether you feel like you're "in control" depends on how well you understand that language.

V. Conclusion

When you die in a game and think, "That wasn't fair," you might be right—but not in the way you think.

The game isn't cheating. It's not ignoring your inputs out of malice. It's following a set of rules that were designed before you ever picked up the controller. Those rules determine whether you can cancel a heal, whether your attack interrupts theirs, whether your dodge succeeds or fails.

The question isn't whether the rules are "fair." The question is whether the rules are communicated.

Dark Souls doesn't show you its frame data. Elden Ring doesn't explain hyper-armor. Monster Hunter doesn't tell you the input buffer duration. You learn these rules through death—over and over, until the pattern becomes muscle memory.

That's not bad design. In fact, it's often excellent design. But it is a design choice—and it's one that profoundly shapes whether you feel the combat is "tight," "responsive," or "cheap."

The game is fair. The question is: do you know the rules?