What causes a Godot AnimationPlayer cutscene playing steps out of order?

You queue the next animation on a timer or in _process rather than awaiting animation_finished, so steps overlap or fire before the previous one ends.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Godot AnimationPlayer Cutscene Steps Playing Out of Order

Quick answer: Await the animation_finished signal (or use queue) before starting the next clip so each step runs only after the prior one completes.

A cutscene whose animations trample each other is starting the next step before the last finishes. Awaiting the finish signal sequences them. Here is how.

How to fix it

1. Await animation_finished

Drive the sequence in a coroutine: anim.play("step1"); await anim.animation_finished; anim.play("step2"). The await guarantees the next clip starts only after the current one ends.

2. Use queue for back-to-back clips

For a simple linear chain call anim.queue("step2") after play("step1") so Godot starts the queued animation automatically when the first completes.

3. Filter the finished signal by name

If multiple AnimationPlayers share the handler, check the anim_name argument the signal passes so you only advance when the intended clip finished, not any clip.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.