What causes a Godot AnimationTree transition that never auto-advances?

The transition uses an Advance Condition expression referencing a condition parameter that is never set to true, so the automatic transition never triggers.

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 a Godot AnimationTree State Machine Not Advancing Because the Advance Condition Is False

Quick answer: Set the named advance condition parameter to true via the AnimationTree, or call travel() on the state machine playback to move explicitly.

State machine transitions can auto-advance using a named condition. If the machine sits in a state forever, that condition is never set true. Here is how to drive the transition.

How to fix it

1. Set the condition parameter

If the transition's Advance Condition is is_moving, set anim_tree.set("parameters/conditions/is_moving", true) when appropriate. Unset conditions read false and block auto-advance.

2. Use travel() for explicit control

Get the playback with anim_tree.get("parameters/playback") and call playback.travel("Run") to move directly, which finds a path through the graph regardless of auto conditions.

3. Check Switch Mode and Auto Advance

Ensure the transition has Auto Advance enabled if you expect it to fire on the condition. A transition set to At End waits for the current animation to finish first.

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.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.