Graph Editor

The Flow Graph Editor is the main workspace for adding nodes, connecting execution routes, editing node content, and inspecting a running process. Use it as a workflow surface, not as a static list of controls.

Open a graph

Open Tools > Flow Core > Flow Graph Editor, then select a Flow Graph. You can also open a graph asset directly from the Project window.

The workspace has four practical areas:

• the canvas, where nodes and connections show authored topology;
• the toolbar, where you select the graph and runtime inspection context;
• node content, where summaries, values, Instructions, Conditions, and module fields appear;
• runtime visualization, which shows recent execution for the selected process.

此处插图应该是完整 Flow Graph Editor 的带标注截图；分别框选 Graph 选择区、Debug Context、Canvas、节点内容区和运行调试高亮，并使用 1–5 编号。

Author a readable route

1. Right-click empty canvas space to open node search.
2. Add the start point before adding downstream behavior.
3. Add nodes near the branch that owns them.
4. Drag from an output port to a compatible input port.
5. Read the route from start point to visible result.
6. Add comments when a region’s responsibility is not clear from node titles.

Flow ports describe execution. Typed values are configured inside node or Instruction fields rather than being treated as generic data wires.

Use detail intentionally

Keep Summary and Value details visible while establishing behavior. They expose value sources, target resolution, and important settings without requiring every field to stay expanded. Reduce detail only after the route is verified and the graph remains readable.

此处插图应该是同一个 Action 节点在 Summary 与 Value 展开前后的对比截图；保留 Set LocalScale 的 Blackboard 路径，并标出折叠后仍可阅读的摘要。

Set Debug Context

Debug Context is the scene GameObject the editor uses to resolve Local and Scene data previews and filter runtime visualization. Choose the object whose FlowCoreProcess actually runs the graph.

If several objects share one graph, switch Debug Context when you switch the object you are investigating. The graph asset remains the same; the explained runtime instance changes.

Verify in Play Mode

Use a small visible result while authoring. In Play Mode, confirm:

• the expected Trigger or Entry starts;
• chain movement follows the intended connection;
• async work remains visibly active while waiting;
• node summaries resolve against the selected process;
• the Game view, Inspector, Console, or Blackboard shows the result.

Common mistakes

Symptom	Check
Node summaries are unresolved	Select the correct Debug Context and verify its Blackboard bindings.
A node exists but never runs	Trace a complete connection from a Trigger or Entry.
Runtime highlighting is empty	Confirm the selected process is the one that received the event.
A graph becomes hard to scan	Separate responsibilities into regions and keep long Instruction lists focused.

Related

• Nodes, Ports & Execution Chains
• Debugging Running Graphs
• Explore a Working Flow