Log in
Login Sign up Blog Tools

Roblox Animation Graphs Explained: State Machines and Luau Expressions Are Fully Released

State Machine and Luau Expression nodes are now fully released in Roblox's Animation Graph Editor. Build character animation without the boilerplate script — here is how, and where the graph still needs your code.

Roblox Animation Graphs Explained: State Machines and Luau Expressions Are Fully Released
In this guide What a Roblox Animation Graph Is What Just Shipped Building Your First State Machine Driving Transitions With Luau Expressions What Expressions Cannot Do What Changed Since the Beta When to Keep Using Priority Select A Practical First Graph Frequently Asked Questions Are State Machines in Roblox Animation Graphs fully released? How do I add a State Machine to an Animation Graph? What can a Luau Expression node do? Can an Expression node read the character's position? Does a State Machine replace Humanoid states? Should I still use the Priority Select node? Related Guides on RBXMods Sources

On Friday, November 20, 2026, Roblox fully released State Machine nodes and Luau Expression nodes in the Roblox Animation Graph Editor. The two features came out of a beta that began in late October 2026, and from today they work in live games — no beta flag, no waiting to ship. If you animate characters in Roblox, this is the change that lets you stop writing boilerplate scripts to switch between looping animations, and instead draw the logic as a graph.

Key takeaways

  • State Machine and Luau Expression nodes are fully released in the Animation Graph Editor as of Friday, November 20, 2026, and work in live games. Graphs built during the beta keep working.
  • A State Machine node knows which state it is in and only changes state when a transition tells it to — no more tracking character state in a Luau script and passing it to a Select node.
  • Expression nodes do small calculations inside the graph, driven by graph parameters. They cannot use loops, tables, require, method calls or DataModel access, and they can only read graph parameters.
  • A State Machine controls character animation, not gameplay. It does not replace Humanoid states, and a script is still needed to set graph parameters from the world.
  • Since the beta, Roblox has fixed duplicate graph names, lost graphs after deleting an instance, and a crash on undo — and added the One Shot node, Server Authority, and negative Y values for Blend2D.

What a Roblox Animation Graph Is

An Animation Graph is a node-based way to control how a character moves, built inside the Animation Graph Editor in Studio. Instead of writing a script that says "if the character is walking, play the walk animation; if it is running, play the run animation," you connect nodes on a canvas: animation clips, blend nodes that mix between clips, and select nodes that pick one clip based on a value. The graph runs on the engine side, which keeps the animation logic close to the animation itself and out of your gameplay scripts.

The editor itself came out of beta in July, and it has been gaining nodes since. The two that matter today are State Machines and Luau Expressions, in beta from late October 2026 and fully released now. Together they solve the two jobs that used to force creators back into scripts: remembering what state a character is in, and doing the small maths that decides when to switch.

What Just Shipped

Two node types are now fully released. The State Machine node holds a set of animation states — Idle, Walk, Run, Jump — and knows which one it is in at any moment, moving only when a transition says so. The Luau Expression node lets you write a short Luau expression inside the graph, so a small calculation — a speed threshold, a blend weight — happens in the graph instead of in a script.

The release matters because of what it replaces. Before State Machines, switching between looping animations based on character state required custom Luau scripting. The existing Priority Select node re-checks all of its conditions every frame, so creators had to track the character's state themselves in a script and pass the result into a Select node. That split the animation logic in two places: the graph held the clips, and a script held the decisions. A State Machine puts the decisions back in the graph, beside the clips they control.

Building Your First State Machine

A basic locomotion graph — Idle, Walk, Run — is the fastest way to learn the workflow, and it takes a few minutes once you have the clips ready.

Insert the node. In the Animation Graph Editor, right-click the canvas and choose Insert Node, then State Machine. The node appears on the canvas with a New Input pin.

Connect your poses. Connect any node that outputs a pose — usually a Sequence node holding an animation clip — to the State Machine's New Input pin. Each connection becomes a state in the machine. Connect your Idle clip, your Walk clip and your Run clip, and you have three states.

Create the states. Click Open on the State Machine node, then Create State in the State Machine window. Each connected input becomes a named state you can arrange and inspect.

Draw the transitions. Drag from one state to another to create a transition, then set its Transition Settings. There are four settings to know: Wait For, which is either an Expression or Finished; Length, the blend time in seconds; Curve, how the blend eases between the two clips; and Priority, which must be unique per state — if several transitions are valid at the same moment, the highest Priority wins.

Set the special states. Two states are built in. (Entry) is the state the machine starts in — usually Idle. (Any) is a transition source that can fire from any state, which is the clean way to handle something like a jump or a hit reaction that can interrupt whatever the character is doing.

That is the whole structure. The machine starts in (Entry), sits in a state until a transition fires, blends over the Length you set, and stays there until the next transition. Because the machine remembers its state, no script needs to watch the character and tell the graph what to play.

Illustration of an animation graph editor canvas showing a state machine node with Idle, Walk and Run states connected by transitions

Driving Transitions With Luau Expressions

Transitions need conditions, and that is what Expression nodes are for. To add one, drag a wire out of a property pin and choose Expression, or right-click the canvas and choose Insert Node, then Expression. Inside the node you write a short Luau expression, and the graph evaluates it live.

Expressions read the graph's parameters, such as a Speed number or a boolean like IsGrounded. A typical setup is a Speed parameter your gameplay script updates every frame, with transitions that read it: Idle to Walk above a small value, Walk to Run above a higher one, and back down again when it falls. The expression does the comparison; the graph does the switching; the script only keeps the Speed parameter honest.

That split is the point. The expression handles the maths that belongs to animation — thresholds, blend weights, slope factors — while the script handles the world: reading the character's velocity, checking whether it is on the ground, and writing those facts into the graph's parameters.

What Expressions Cannot Do

Expressions are deliberately small, and the limits are stated in the announcement, so it is worth knowing them before you plan a graph around something they cannot do. Expressions do not support loops, function definitions, tables, require, or method calls. They cannot use any library other than math, and they have no DataModel access at all.

The practical consequence is that an expression can only read graph parameters. It cannot read the character's position, check a part in the workspace, or look at anything else in the game world. If a transition depends on something in the world, a script still has to read that fact and write it into a graph parameter first.

There is a second limit in the same spirit: a State Machine does not replace Humanoid states. Humanoid states are gameplay — whether the character is jumping, falling, swimming or dead — and they belong to the Humanoid. A State Machine is animation — which clip plays for the state the character is already in. Keep the two separate in your head, and you will not try to build gameplay logic in the graph, which is the fastest way to fight it.

What Changed Since the Beta

The full release is not just the beta with the flag removed. Roblox lists several fixes that landed between the beta and today. Graphs no longer get duplicate names, deleting a graph's instance no longer loses the graph, and undoing after deleting a graph's nodes no longer crashes Studio. There are also fixes for edge cases in Blend2D, BlendSpace1D, Sequence and State Machine nodes.

Four things are new since July, when the Animation Graph Editor came out of beta. The One Shot node plays a clip once and stops, which is the natural fit for an attack or an emote inside a graph. Sequence nodes have a new When option, BeforeFinished, for starting the next step just before a clip ends. Server Authority means server-owned graph values no longer replicate to all clients, which keeps server-driven animation data where it belongs. And Blend2D now supports negative Y values, so a blend space can cover movement in both directions on that axis.

When to Keep Using Priority Select

State Machines do not retire the Priority Select node. The announcement says it still has a place, and the distinction is worth keeping straight. A State Machine is for stateful switching: the character is walking, and it stays walking until something tells it to run. A Priority Select is for instant, stateless, priority-based selection: every frame it re-checks its conditions and picks the highest-priority match right now, with no memory of what it picked last frame.

Use a State Machine when the animation has a state that should persist — locomotion, a combat stance, a held tool pose. Use Priority Select when the choice is a pure function of the current moment — an override pose that should win whenever its condition is true, and vanish the instant it is not.

Illustration of a character animation blending from a walk cycle into a run cycle, driven by a speed value in an animation graph

A Practical First Graph

If you want a first graph that teaches the system, build locomotion with three states and one parameter. Create a Number parameter called Speed. Add a State Machine with Idle, Walk and Run states, each holding its clip. Set (Entry) to Idle. Add transitions: Idle to Walk when Speed rises above a small value, Walk to Run when Speed passes a higher one, and the reverse transitions when Speed falls back down. Give the upward transitions a higher Priority than the downward ones where both could be valid, and set a short Length — around 0.2 seconds — so the blend feels responsive without snapping.

Then write the one script the graph still needs: a short loop that reads the character's velocity each frame and writes its magnitude into the Speed parameter. That is the whole contract between your code and the graph. Everything else — the states, the thresholds, the blends — lives on the canvas, where you can see it, tune it, and show it to a teammate without opening a script.

Graphs are built to run smoothly on every player and every device, but no numeric performance limit is stated, so do not treat that as a budget. Keep graphs as simple as the animation needs, and profile a real game before layering several machines onto one character.

Frequently Asked Questions

Are State Machines in Roblox Animation Graphs fully released?

Yes. State Machine and Luau Expression nodes for the Roblox Animation Graph were fully released on Friday, November 20, 2026, after a beta that began in late October 2026. They work in live games with no beta flag, and graphs built during the beta keep working.

How do I add a State Machine to an Animation Graph?

In the Animation Graph Editor, right-click the canvas and choose Insert Node, then State Machine. Connect pose-outputting nodes to its New Input pin — each connection becomes a state — then click Open, choose Create State, and drag from one state to another to create transitions.

What can a Luau Expression node do?

It evaluates a short Luau expression inside the graph, reading the graph's parameters. Use it for thresholds, blend weights and transition conditions. It cannot use loops, function definitions, tables, require, method calls, libraries other than math, or DataModel access.

Can an Expression node read the character's position?

No. Expressions can only read graph parameters. A script must read the world — velocity, grounded state, equipped tool — and write those values into the graph's parameters for expressions to use.

Does a State Machine replace Humanoid states?

No. Humanoid states are gameplay states owned by the Humanoid. A State Machine controls which animation clip plays; it is for character animation, not gameplay logic.

Should I still use the Priority Select node?

Yes, for instant, stateless selection. Priority Select re-checks its conditions every frame and picks the highest-priority match with no memory. Use a State Machine when the animation state should persist until a transition fires.

Related Guides on RBXMods

RBXMods is not affiliated with or endorsed by Roblox Corporation. Roblox and the Roblox logo are trademarks of Roblox Corporation.

Sources

Last checked against Roblox sources: November 20, 2026.

Pawan Nagare
Written by

Pawan Nagare

I'm Pawan Nagare, and I run RBXMods. I write practical Roblox guides about how games are actually made — Roblox Studio, scripting, publishing and growing a game — along with clear fixes for the errors and confusing changes players run into.

Every guide here is researched against official Roblox documentation and checked against the current version of Roblox before it is published — and I update posts when Roblox changes the rules.

My aim is simple: honest, up-to-date help that respects your time — no recycled lists, and no shortcuts that put your account at risk.