> For the complete documentation index, see [llms.txt](https://docs.fullscreen.no/info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fullscreen.no/info/game-creator-2-assets/nodeflow/graph-basics.md). # Graph Basics ### Opening NodeFlow Quests Graph *(Quest Graph only)* Opening the NodeFlow Quests Graph can be done in two different ways.\ You can either double-click a Quest Scriptable Object in your Project folder, which automatically opens the graph, or manually open it through the Unity toolbar by navigating to `Window > NodeFlow > Quests` *** ### Opening the NodeFlow Dialogue Graph *(Dialogue Graph only)* The NodeFlow Dialogue Graph can be opened through the Unity toolbar by navigating to: `Window > NodeFlow > Dialogue` After opening the graph editor, you can load a Dialogue Component in two different ways: * Select a Dialogue Component using the Dialogue Field at the top of the editor. * Open a GameObject in the scene that contains a Dialogue Component. The graph editor will automatically load the assigned dialogue graph. *** ### Node Numbering Each node displays a number in its header that represents both its position in the graph hierarchy and its execution order. Main nodes use numbers such as: `1`\ `2`\ `3` Child nodes use hierarchical numbering based on their parent node: `1.1`\ `1.2` For example: * Node `1` executes before Node `2` * Child nodes `1.1` and `1.2` executes before Node `2` * Node `1.1` executes before Node `1.2` The numbering updates whenever nodes or child nodes are rearranged. *** ### Node Flow Preview When selecting a node, NodeFlow displays dotted preview lines that visualize the execution flow between nodes. These dotted lines help show which node will execute next based on the current hierarchy and node order. For example: * Selecting node `1.1.1` will display a dotted line pointing to node `1.2` * If multiple main nodes exist, the last child node of a hierarchy will point to the next main node * For example, node `1.2` will display a dotted line pointing to node `2` These flow preview lines are only visible while the related nodes are selected, helping keep the graph clean and uncluttered during normal editing. *** ### Dialogue Story Flow Dialogue nodes display how the story continues after the current node finishes. Each dialogue node can use one of the following story flow types: * **Continue** - Continues to the next node in execution order. * **Exit** - Ends the dialogue. * **Jump** - Jumps directly to another tagged node in the graph. The currently selected story flow type is displayed directly on the node. #### Continue If a node is set to **Continue**, clicking the flow label will automatically select and pan to the next node in the dialogue flow. For example: `Node 1.2 > Continue to Node 2` Clicking the label will move the graph view to Node `2`. #### Jump If a node is set to **Jump**, the node displays the tag of the target node. For example: `Node 1.2 > Jump to #Start` If Node `1` contains the tag `#Start`, clicking the label will automatically pan to and select that node. When the node is selected, a dotted line will also appear between the current node and the target tagged node, making the jump connection easier to visualize inside the graph. *** ### Tagged Nodes *(Dialogue Graph only)* When a dialogue node has been assigned a tag, the tag will be displayed directly in the node header. This makes it easier to quickly identify important story jump points and navigate through larger dialogue graphs. For example: `Node 1 #Start` Tags are commonly used together with the **Jump** story flow type, allowing dialogue nodes to jump directly to tagged nodes within the graph. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.fullscreen.no/info/game-creator-2-assets/nodeflow/graph-basics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.