Visual Scripting

No-Code Editor

Wire up game logic from a node graph — 67 nodes, no code. The graph is not interpreted at runtime: the server compiles it to WebAssembly.

How it works

The No-Code Editor uses a visual graph system where each node represents an action, computation, or value. You connect nodes together to define how your game behaves.

A graph has two kinds of wire. Flow wires set the order things happen in and carry no value. Value wires carry a typed value out of an expression node and into an input, and take no part in the ordering.

Every chain of work hangs off a trigger — one of the five “On…” nodes. A script can hold several, each starting its own chain, and a node no trigger can reach never runs. A script with no trigger at all will not compile.

Each input takes one wire; an output can fan out to as many as you like. Wires only ever move forward: a graph that loops back on itself is rejected. Scripts attach to an object and drive that object, so the transform nodes need no target — they act on whatever the script is attached to.

Wire types

The editor colours every pin by what it accepts, and refuses a connection between two that do not agree. A pin that takes more than one type is drawn as a slice of each.

flow
Execution, carries no value
int
Whole number
float
Decimal number
number
Whole or decimal number
bool
True or false
string
Text
any
Any single value type
array
A list of values

int and float never mix. They are distinct types and nothing converts between them on its own, so an int heading for a float input has to pass through a To Float node first. It is the single most common reason a graph refuses to build.

Node Reference

View all nodes