Server code
Kumi
Kumi draws server code as nodes and wires. Plugins, loops and rooms can be written in Luau or drawn in Kumi, the editor of each has a Code and a Kumi switch above it.
Kumi is not a second language on the server. It writes Luau from the graph, the same code a programmer would write, and the server runs only that code: the sandbox, the limits and the logs are the same as for code written by hand.
Nodes and wires
| What it is | |
|---|---|
| Events | Where a run starts: On call for an rpc, On hook, Every few seconds, On start, On tick, On stop, On join, On leave and On message |
| White wires | What runs after what. A white output goes to one node, Sequence runs several one after the other |
| Colored wires | Values. The color is the type: number, text, true or false, table, vector, world and body |
| Flow | Branch, Sequence, For each, For range, Return and Fail |
| Values | Numbers, text, vectors, math, comparisons, tables and the values of the event, like the player of a call |
| The API | Every function of Player Data, the Realtime Database, Files, the Cache, rooms, physics and lag compensation is a node |
A wire only goes where its type fits. Let a wire go on empty canvas and Kumi lists the nodes that take it, the chosen one comes wired.
An input that no wire reaches holds a value of its own, a number or a text typed into the node. A node of two values, like A > B, always reads A above and B below.
Variables
Variables live on the side panel. In a loop or a room they keep their value between ticks, so a world of physics made in On start is stepped in On tick:
On start → Make world → Set world
On tick → Step (world, seconds)A wire carries one value. A value that changes inside a Branch or a loop and is read after it, like the damage of a shot that is bigger for a head, lives in a variable: Set damage on both sides, Get damage after them. Code → Kumi says so when a local of the code changes like that.
A plugin runs fresh on every call, its variables start over each time.
Mistakes
What Kumi can see before saving shows on the node and in the Problems list: an input that needs a value, a node no event reaches, a white wire that goes round in a circle, a value of one event read in another. A click on a problem shows its node.
An error of the server, from a publish or a test run, names a line of the code Kumi wrote. Kumi knows the node of every line and marks it.
Code and Kumi
Kumi → Code keeps the Luau Kumi wrote, from then on it is written by hand.
Code → Kumi draws the code that is in the editor. Kumi draws what its nodes write: events, local values, if, elseif and else, numeric for and for ... in, +=, every call of the API, physics, math, comparisons, .., and tables with names as keys. Variables at the top of a loop or a room become variables of the graph, a value made at the top is made in On start.
Code that no node writes, like while, repeat, a function of its own or a list written as { 1, 2 }, isn't drawn. Kumi names the first line it can't draw, change it or start from an empty graph.
The Luau part of the side panel shows the code of the graph at any time.
Keys
| Key | What it does |
|---|---|
| Backspace, Delete | Removes the chosen nodes and wires |
| Ctrl or ⌘ + S | Saves the draft |
| Arrows and Enter | Pick in the list of nodes that opens at the end of a wire |
| Esc | Closes that list |
Updated November 21, 2026