Node Status
See which nodes are core, beta, runtime-only, or extension-adjacent before building a large route. Check node status.
Node Reference
Nodes are how a scene becomes playable. Each node does one focused job, then points to what should happen next.
If you are unsure what node to add, ask what the story is trying to do at that moment: speak, ask, branch, change state, change the stage, wait, touch the Roblox world, jump, or end.
Common node types
Section titled “Common node types”- Dialog shows speaker text and optional typewriter behavior.
- Text Input prompts the player and stores submitted text.
- Choice presents options and routes each option to another node.
- Condition branches based on variable state.
- Jump moves to another scene or chapter.
- End ends the current story path.
- Set Variable updates story state.
- Text Input lets the player enter text into a variable.
- Background changes the scene background.
- Overlay shows, colors, or clears a cover over the scene.
- Sprite Enter / Update / Exit controls character sprites.
- Audio controls longer tracks; SFX plays one-shot sounds.
- Effect applies momentary shake, jump, emphasize, or deemphasize behavior.
- Title Card shows a chapter or scene title card.
- Wait pauses for a fixed duration.
- UI Visibility hides or shows dialog and sprites.
- Roaming lets the runtime enter or leave movement-oriented play.
- Teleport Player moves the player to an instance path.
- Wait For Sprite Activation waits for an interactable sprite.
- World Wait waits for a touch or click trigger in the Roblox world.
Detailed node guides
Section titled “Detailed node guides”Variables & Text
Learn how Store in Variable, text templates like {playerName}, conditions, and character names from variables work. Open the guide.
Dialogue & Logic
Open a specific node: Dialog, Text Input, Choice, Set Variable, Condition, Jump, or End.
Presentation
Open a specific node: Background, Overlay, Sprite Enter, Sprite Update, Sprite Exit, Audio, SFX, Effect, Portrait Link, Scroll Sound Link, or Title Card.
System & World
Open a specific node: Wait, UI Visibility, Roaming, Teleport Player, Wait For Sprite Activation, or World Wait.
A simple scene pattern
Section titled “A simple scene pattern”- Start with a presentation node if the scene needs a background, title card, or audio change.
- Add dialog nodes for the main conversation.
- Add a choice or condition where the story branches.
- Connect each branch to its target node.
- Merge branches back together when the story returns to a shared path.
- End the path or jump to the next scene.
Warnings
Section titled “Warnings”Nodes that depend on missing setup show warnings in the Properties panel and Story Map. For example, a sprite node needs a sprite, and a scene needs a valid starting node.
Warnings are not always errors while drafting. They are the editor telling you, “this node may not be playable yet.”
Missing dependency
A node points at an asset, variable, scene, character, or target that does not exist yet.
Incomplete flow
A scene has no start node, a choice option has no target, or a node expects a next target that has not been connected.
Invalid setup
A property is present but cannot be used safely by the runtime, such as a non-string variable on Text Input.
Defaults worth knowing
Section titled “Defaults worth knowing”- Background and overlay transitions default to
cut. - Sprite enter and exit transitions default to
slide. - Sprite update transitions default to
hop. - Audio defaults to the
bgmtrack andplayaction when unset. - Dialog typewriter speed defaults to project speed, which defaults to
1. - Choice timeout defaults are
5seconds, choice IDtimeout, and textNo choice madewhen the timeout path uses defaults.
Node design rule
Section titled “Node design rule”Nodes should be explicit. Creating a Sprite Enter node should not silently create the sprite asset it references. Creating a scene should not guess a start node forever. If a node needs another asset, variable, scene, or target to work, the editor should show a warning or offer an explicit create action.
This makes projects more predictable:
- Missing dependencies are visible.
- Runtime behavior does not depend on hidden fallback assets.
- Authors can scaffold a scene without the editor inventing story data.
- Validation can catch broken paths before a player reaches them.