← ClaudeAtlas

unity-animationlisted

Animator in 2D and 3D: stuck or self-playing states, sliding feet, blend trees, IK, root motion.
tipoLi5890/unity-dev-skills · ★ 2 · Web & Frontend · score 75
Install: claude install-skill tipoLi5890/unity-dev-skills
# unity-animation — the game's state is the truth, and the Animator renders it > **An Animator is a state machine, and the game already has one.** Every "stuck in the jump", > "attack played twice", "hitbox stayed on" report is the two disagreeing. They cannot disagree > when one of them is a copy: the game owns the state, one bridge writes it into parameters > once per frame, and nothing in gameplay waits on an animation unless a **named** event says so. ## Symptom → where to look | The report | Go to | |---|---| | "the animation is stuck", stuck in the jump, a renamed parameter froze the character | *The contract*, `reference/parameter-contract.md` | | "the attack plays by itself" later | `reference/parameter-contract.md` (triggers) | | "the feet slide", feet floating on slopes | `reference/blend-trees.md`, `reference/ik-and-rigging.md`, `reference/sim-driven-animation.md` §4–6 | | "the swing contact is late", a simulation owns the character | `reference/sim-driven-animation.md` | | "a knee pops", the prop misses at contact | `reference/foot-lock-and-prop-ik.md`, measured by `reference/motion-metrics.md` | | "the sprite flickers between directions", a 2D jump shows late | `reference/sprite-state-graph.md` | | "the hitbox stays on", footsteps fire twice | `reference/events-and-windows.md` | | Moves twice or slides back each loop | `reference/root-motion.md` | | A cutscene never gives the character back | `reference/timeline.md` | | Starting values for fades, damping, wind