Yes. In Kingdom Hearts 1, casting Time (Stop) on an enemy does not block your damage. All physical attacks, magic, and summons you land on a stopped enemy deal full damage and register normally, because Stop halts the target's movement and AI without granting immunity frames. The target simply cannot act, dodge, or retaliate while frozen, so your hits connect and the health bar drops exactly as it would against an active enemy. The real constraints are MP cost, duration, and which enemies the spell can even affect.
Kingdom Hearts 1 gives you a small toolkit of status magic, and Stop is the one most often misunderstood. Players freeze a Heartless, swing a few times, and then second-guess whether those hits actually counted. This explainer covers the underlying mechanic, the numbers behind Stop's duration and MP economy, the enemies that resist it, the myths that persist in old forum threads, and how to build a practical rotation around it. Everything here applies to the original 2002 PlayStation 2 release and the Kingdom Hearts HD 1.5 ReMIX version, which preserve the same combat logic.
The damage pipeline and why Stop does not interrupt it
Kingdom Hearts 1 resolves a melee swing in stages. The game checks whether your weapon's hitbox overlaps an enemy's hurtbox, then applies damage, then applies hitstun or knockback. Stop modifies an enemy's movement state and its behavior script. It does not touch the hurtbox, the damage formula, or the hit-detection step. That separation is the whole answer. A frozen enemy is still a valid target because the spell never flags it as untargetable or invulnerable.
The engine treats Stop as a status effect with a timer. While that timer runs, the enemy's AI script is suspended and its animation is locked to a frozen pose. Your attack still queries the same collision data it always does. The result is that a stopped Shadow or Soldier takes the same keyblade damage it would take while walking toward you. The hit spark plays, the damage number appears, and the health bar depletes. Nothing about the freeze removes the enemy from combat calculations.
A useful way to picture it: Stop pauses the enemy's turn, not its hitbox. If you have played turn-based games, think of a stop effect that skips the enemy's action but leaves it fully vulnerable. Kingdom Hearts 1 implements that concept in real time. The practical consequence is that Stop is an offensive setup tool, not a defensive stall.
The one nuance is hitstun. Because the enemy is already frozen, your attacks cannot produce visible flinch reactions. The damage still applies, but the feedback looks different, which is exactly why players doubt it worked. Watch the health bar and the damage numbers rather than the enemy's body language.
Quantified context: MP cost, duration, and the math of a Stop window
Stop costs 15 MP at base in Kingdom Hearts 1. Your maximum MP grows as you level and as you equip accessories, and the spell's duration scales with your Magic stat and the spell tier. Stop, Stopra, and Stopga are the three tiers, each costing more MP and lasting longer. Duration is measured in seconds and is not a fixed number across the whole game, because the Magic stat and enemy resistance both shift it.
The damage you deal during a Stop window depends on your attack speed and combo length. Sora's ground combo lands several hits in roughly two seconds, and the air combo adds more. If a Stopga window lasts long enough for two full combos, you are effectively getting free uninterrupted damage on a target that cannot block, dodge, or interrupt you. Against enemies with evasive AI, that reliability is worth more than the raw MP cost suggests.
MP economy matters more than raw duration. Kingdom Hearts 1 regenerates MP slowly on its own, and Ethers and Elixirs restore it in chunks. Spending 15 MP to guarantee a clean combo on a dangerous mid-boss is usually efficient. Spending it on a single common Shadow that dies in two hits is not. The spell's value scales with how much trouble the target's AI causes you.
| Spell tier | Base MP cost | Relative duration | Best use case |
|---|---|---|---|
| Stop | 15 MP | Shortest | Locking a single fast enemy for one combo |
| Stopra | Higher than Stop | Medium | Mid-bosses with evasive or aggressive AI |
| Stopga | Highest | Longest | Crowd control in dense encounters |
| No Stop | 0 MP | None | Trash mobs that die in one combo anyway |
| Ether (item) | Consumable | Restores MP | Refueling between Stop casts |
Exact MP costs and second-by-second durations for Stopra and Stopga vary with your build and the version you play, so treat the table as a relative comparison rather than a fixed spec sheet. The tier ordering and the "spend it on dangerous targets" logic hold in every version.
Which enemies Stop actually affects
Stop is not universal. Kingdom Hearts 1 assigns status resistance to many enemies, and bosses frequently resist or ignore Stop entirely. Common Heartless like Shadows, Soldiers, and Powerwilds are generally susceptible. Larger or armored enemies and most story bosses are not, or they shake off the effect almost instantly. If the freeze does not visibly take hold, the enemy is resisting, and further casts waste MP.
Flying enemies and enemies with scripted behaviors sometimes behave oddly under Stop. A stopped flying enemy will hang in the air, which can actually make it easier to hit with jumping attacks. A stopped enemy that was mid-charge will freeze in place, which removes its threat but also changes where its hurtbox sits. Adjust your positioning rather than assuming the freeze behaves like a stun.
Summons and party AI interact with Stop in ways that surprise players. Donald and Goofy continue attacking a stopped target and their damage registers normally. Summon abilities that rely on the enemy moving, however, can whiff. The freeze is a state change, so any attack or ability that checks for a specific enemy animation may fail to trigger. Plain melee and direct-damage magic always work.
The professional caveat here is that Stop's reliability is encounter-specific, not global. Treating it as a universal lockdown tool leads to wasted MP on resistant bosses. Treating it as useless because one boss ignored it throws away a strong option against fast, fragile enemies. Read the encounter before you commit the cast.
Timeline of a typical Stop window
Understanding the time course helps you plan combos instead of mashing. The sequence below describes a standard cast-to-recovery cycle on a susceptible enemy.
| Phase | What happens | Player action |
|---|---|---|
| Cast | MP deducted, spell animation plays, target flagged | Confirm the freeze visually |
| Freeze start | Enemy AI suspended, animation locked | Begin your combo immediately |
| Active window | Full damage applies, no enemy retaliation | Chain ground and air combos |
| Late window | Freeze about to expire, enemy resumes | Reposition or prepare to block |
| Expiry | Enemy AI resumes at full speed | Disengage or recast if needed |
| MP recovery | MP regenerates or item used | Decide whether another Stop is worth it |
The key takeaway from that timeline is that you should start attacking during the cast animation's tail, not after you mentally confirm the freeze. Every second you hesitate is a second of free damage you did not take. The freeze duration is finite, and the enemy resumes at full aggression the instant it ends.
Recasting Stop before the first window expires is usually wasteful. The fresh cast overwrites the timer but costs another 15 MP or more. Let the window run, land your damage, and only recast if the enemy is still a threat and your MP allows it. This is the single biggest efficiency mistake players make with status magic.
Misconceptions that keep circulating
The most common myth is that stopped enemies take reduced or zero damage. This likely started because the lack of flinch animation makes hits feel ineffective. Players see no reaction, assume the hit missed, and stop attacking. The health bar tells the true story. Damage is full and normal.
A second myth is that Stop only works on weak enemies and is therefore a beginner trap. In practice, Stop's value comes from disabling fast, evasive, or aggressive mid-tier enemies long enough to land a clean combo. Against a slow tank that you can already hit reliably, Stop adds little. Against a teleporting or dashing enemy, it changes the fight.
A third misconception is that casting Stop on a boss wastes MP because bosses are immune. Some bosses resist it, but not all, and the resistance is often partial rather than absolute. Testing a single cast early in a boss fight tells you whether the freeze takes hold. If it does, you have a window; if it does not, stop casting and save the MP. Do not assume from forum posts that every boss ignores it.
Red flag: continuing to cast Stop on an enemy that visibly is not freezing. Red flag: recasting before the current window expires and doubling your MP spend. Red flag: assuming no flinch means no damage and abandoning a free combo. Red flag: building an entire strategy around Stop against a boss you have not tested it on. Red flag: ignoring MP recovery items and running dry mid-encounter.
Practical actions for using Stop well
Treat Stop as a setup spell, not a damage spell. The damage comes from your keyblade and magic during the window, and the spell's job is to guarantee those hits land. Build your rotation around that idea and the spell pays for itself.
First, identify the enemy's threat pattern before you cast. If it dashes, teleports, or attacks relentlessly, it is a good Stop target. If it stands and swings slowly, you can probably just block and counter without spending MP.
Second, cast at the start of the encounter or the moment the dangerous enemy becomes active. Do not wait until you are already losing. The freeze is most valuable when it prevents the enemy's first big move.
Third, begin your combo during the cast animation. Do not wait for visual confirmation if you already know the enemy is susceptible. The freeze timer starts immediately, and hesitation costs you hits.
Steps to a clean Stop combo: Confirm the enemy type is susceptible with a test cast. Cast Stop or Stopra as the enemy closes or winds up. Start your ground combo as the cast finishes. Chain into an air combo if the window is long enough. Reposition before the freeze expires and decide on a recast.
Fourth, manage MP deliberately. Keep at least one Ether or Elixir for emergencies, and do not spend your last MP on a Stop against a weak enemy. MP is a resource with a slow natural regen, so every cast should buy you something concrete: a clean combo, a skipped dangerous attack, or breathing room to heal.
The threshold worth remembering is simple. If the enemy would cost you more than 15 MP worth of healing or trouble to fight normally, Stop is worth it. If it dies in one combo regardless, save the MP. That single rule covers most encounters in the game.
Limitations and what this explainer cannot tell you
This explainer describes the mechanic as implemented in the original release and the HD 1.5 ReMIX version. It does not provide frame-perfect duration values, because those shift with your Magic stat, your equipment, and the specific enemy's resistance, and they are not documented by an authoritative source in a way that would justify quoting exact seconds. Treat any specific duration figure you see online with suspicion unless it comes with a documented test methodology.
The damage-still-applies answer is stable and version-independent for Kingdom Hearts 1, but resistances and boss behavior are encounter-specific. No single article can enumerate every enemy's status resistance table without reproducing a datamine, and doing so would risk presenting unofficial data as fact. Test in-game when it matters.
What you can rely on is the mechanism: Stop suspends enemy AI and movement without removing the hurtbox or granting invulnerability. That is why your damage goes through. Everything else, from MP cost to duration to which bosses shrug it off, is a tuning detail around that core rule. Understand the rule and you will use the spell correctly in any encounter.