Why does rename break state machines?

State references in scripts and saved scenes are by string name. After rename, scripts that called travel(‘OldName’) silently no-op, and the AnimationTree may sit in a non-existent state if it was paused there.

How do I recover a stuck tree?

Get the AnimationTree’s playback object (anim_tree[‘parameters/playback’]) and call playback.start(‘ValidState’). Forces it back to a known node.

After rename, use Find & Replace in Files for the old state name to catch script references. Also test all transitions in editor preview before saving.

Fix: Godot AnimationTree StateMachine Stuck After Rename

Quick answer: Call playback.start("ValidState") from script to recover. Find & Replace old state name across scripts to avoid stale references.

An action game has an Idle/Run/Jump animation tree. After renaming Run to Walk for clarity, characters now stand still during gameplay. AnimationTree silently failed to transition because scripts still call travel("Run").

Diagnose with Editor Preview

Open the AnimationTree node in editor; the state graph shows the current active state highlighted. If it shows an unknown / orphan node, the tree is in a renamed/missing state.

Force a Reset

var playback: AnimationNodeStateMachinePlayback = anim_tree.get("parameters/playback")
playback.start("Idle")

Forcibly switches to a known state, ignoring transitions. Useful in _ready or on level load.

Update Script References

Search the project (Ctrl+Shift+F) for the old state name as a string literal:

playback.travel("Run")   # wrong — now "Walk"

Replace each occurrence. Also check scene .tscn files for cached parameter paths (search them as text).

Use Constants for State Names

Define state names once:

const STATE_IDLE = "Idle"
const STATE_WALK = "Walk"
const STATE_JUMP = "Jump"

playback.travel(STATE_WALK)

Renames now touch one file. Refactor-friendly.

Verifying

Run game; player animates correctly through all states. Toggle each transition (idle → walk, walk → jump). Editor preview during play shows active state matching gameplay.

“State machines reference by string. Rename safely with project-wide search and named constants.”

For complex AnimationTrees, write a smoke test that travels through every state at startup — catches missing-state regressions immediately.