Nodes

The built-in catalog is 610 nodes across 27 categories. A category is the grouping you navigate in the palette, so these pages are organised the way the editor is.

How to read a node

Each node is written like this:

Delay

blueprint.flow.delay · Latent

The first line under the heading is the node's type id — the value stored in the document, and what you would register from a plugin. After it come the flags that are true for that node:

Pure does not by itself mean the node works inside a Blueprint Value. That is a separate, narrower rule: the node must be pure and non-latent and belong to one of the allowed categories — Data, List, Math, Time, Text, Slider, Displayable, Element, Game — plus a short list of specific exceptions (Init and On Flush heads, non-latent Flow, local variable access, Call Fn, comments, Return Value, and four Page state reads). A Self node scoped to widgetMain is excluded regardless of its flags; inside a Blueprint Value you reach a widget through an Element literal and the Element-category reader.

Then the pin table:

Exec pins carry execution; data pins carry values. Accepts an on-card literal means you can type the value into the node card instead of wiring an edge. Some nodes have dynamic pins — projected from a selected variable, a chosen function signature, or a case you appended — and those are described in prose, because there is no fixed table to print.

Availability

A node appearing in this catalog does not mean it appears in your palette. Three filters apply:

• Graph kind. function graphs refuse effectful and latent nodes.
• Owner and widget capability. Self nodes only show in the blueprint of a widget that has that capability; a Set Slider Value is not offered inside a Text widget's blueprint.
• Present bindings. An Element node only appears once the graph already holds a compatible Element, Element Flush, or Element Click node to wire it to.

Categories