Animation Not Playing Roblox

What Actually Makes Roblox Animations Stop Working

Most people hit Animation Not Playing Roblox because they don't realize Roblox uses a completely separate animation system than what you see in Blender or Maya. I spent three weeks trying to figure out why my carefully crafted attack animation played as a default idle pose every single time. The problem wasn't the animation file — it was how Roblox prioritizes animation tracks. When you publish an animation to Roblox, it gets assigned an AnimationId that references the asset ID. That asset ID is what you put into scripts. But just having the correct ID doesn't guarantee playback. Roblox checks several conditions before it actually plays anything. The AnimationController needs to exist. The animation's Priority level needs to be higher than any currently playing animation. And the character needs a valid humanoid with the right properties enabled.

Animation Not Playing Roblox — Step-by-Step Fix

First, open your animation in Roblox Studio and check the Priority setting in the Properties panel. This is the most common issue I see. Default priority is usually "Movement," which is relatively low. If your character is walking, running, or jumping at the same time, those animations have equal or higher priority and will completely override yours. Set your custom animation to at least "Core" priority, or "Action" if it's supposed to interrupt movement. Next, verify your script is actually calling the animation. Here's what the basic structure should look like: local animation = Instance.new("Animation")
animation.AnimationId = "rbxassetid://YOUR_ID_HERE"
local player = game.Players.LocalPlayer
local character = player.Character or player.CharacterAdded:Wait()
local humanoid = character:WaitForChild("Humanoid")
local animTrack = humanoid:LoadAnimation(animation)
animTrack:Play()

That last line is where everything usually breaks. If animTrack comes back nil, your animation asset ID is wrong or the animation hasn't been properly published. Go to the Animation Editor, make sure your animation has been saved to the library with a proper name, and grab the correct asset ID from the Properties panel of the animation object itself — not from wherever you pasted it into the script. Also check that AnimSpeed isn't set to zero. I've seen this happen when someone copies an animation from a free model and the speed value gets corrupted during import. It plays the animation but at zero speed, which looks exactly like it's not playing at all.

The Edge Case Nobody Talks About

Here's something I ran into last month that cost me two days. I had an animation that worked perfectly in a blank baseplate test. Same script, same animation asset, same humanoid. But in my actual game, it never played. Turns out another developer on the project had added a global animation filter using Humanoid.DescriptionAnimSpeeds in a server script. It was scaling down all non-movement animations to near-zero speed across the entire game. The fix was finding that script, identifying the problematic entry, and either removing it or adjusting the scale factor. This is the kind of thing that's almost impossible to debug by looking at your animation code alone. You have to trace through every script that touches Humanoid properties in your game, which can be dozens depending on how complex your project is.

Other Things That Silence Your Animations

If you're using Animator objects instead of AnimationController (which is the newer system), the approach changes slightly. Animator was introduced to replace AnimationController, but many older tutorials still reference the outdated method. Check what your character actually has. Right-click the Humanoid in the Explorer and look for either an Animator or AnimationController instance. Load your animation onto the correct one. Motion matching can also interfere. If your game has any kind of procedural animation layer running, it might be overriding your keyframe animations without any visible error. Disable motion matching temporarily to test whether your animation plays. There's also the case where animations simply don't transfer between places correctly. If you're developing in multiple places or have a pipeline where assets move between games, the animation data might not have replicated to the destination. Re-upload the animation asset directly to the target place.

Known Limitations

Even when everything is set up correctly, Roblox animations have hard constraints. They only support up to 96 bones per animation. They don't blend smoothly with physics-based character movement unless you explicitly write blending logic. And they only play on characters that have a standard Roblox Humanoid — custom rigs without one won't work no matter how many fixes you try. If you need complex animation layers, root motion control, or professional-grade blending, you're better off switching to an external animation system like Animation rigging with custom scripts or using a framework like Animation State Machine. The built-in system is fine for simple actions, but it has real ceilings. For now, go through your animation priority, verify the Asset ID, check for AnimSpeed anomalies, and hunt down any global Humanoid modifiers in your scripts. That covers roughly ninety percent of the cases I deal with weekly.