Appearance
Editor Overview
The editor is where you change a flow. Most edits happen by adding nodes, selecting a node, changing its settings, and connecting it to the next step.
Layout
| Area | Purpose |
|---|---|
| Header | Save, validate, deploy, share, import, export, open docs, and return to the dashboard. |
| Node Palette | Find and add nodes. |
| Flow Canvas | Arrange nodes and draw connections. |
| Node Inspector | Change the selected node's settings. |
Header Actions
| Action | Use it for |
|---|---|
| Undo / Redo | Step through edit history. |
| Save | Save the current flow. |
| Validate | Check the flow for missing settings or broken structure. |
| Share | Manage collaborators and access levels. |
| Deploy | Publish the current flow to a server. |
| Import / Export | Bring in JSON or create a backup/share copy. |
| Settings | Change editor workspace preferences. |
What You Can Change
The selected node determines what appears in the Node Inspector. Common settings include:
- Command names, aliases, descriptions, usage text, permissions, cooldowns, and sender rules.
- Messages, colors, titles, action bars, boss bars, webhooks, and legacy text.
- Player targets, usernames, permission-based targets, locations, worlds, and coordinates.
- Items, amounts, custom names, lore, enchantments, NBT, GUI slots, and click actions.
- Conditions, comparisons, branch values, chance percentages, and cooldown keys.
- Variables, arrays, maps, text operations, and database collection settings.
Connections
Nodes connect from the right of the output node to the left of the input node:
- Trigger nodes start the flow and have no input handle.
- Most action nodes use a
Thenoutput. - Conditions use outputs such as
Yes/No,Match/No Match, orReady/On Cooldown. - Switch nodes can have one output per case.
If a branch has no more connected nodes, that branch ends. Add a Stop Flow node only when you want to end the execution specifically at that point.
Validation
Use Validate before deployment. Validation helps catch:
- Missing required settings
- Invalid or disconnected node paths
- Connections that would create loops where loops are not expected
Issues are highlighted on the affected nodes so you can fix them before publishing.