Node Inspector

The Node Inspector is the right sidebar. It shows the settings for the selected node.

How to Use It

1. Select a node on the canvas.
2. Fill in required fields first.
3. Adjust optional settings as needed.
4. Watch for fields that appear or disappear based on earlier choices.
5. Validate the flow before deploying.

Common Field Types

Field Type	Use it for
String	Single-line text, names, permissions, commands, variables, and IDs.
Multiline	Longer messages, titles, lore, webhook text, and JSON.
Number / Slider	Amounts, durations, coordinates, health, food, XP, and percentages.
Boolean	On/off settings.
Select	Choosing one option from a list.
Multi-select	Choosing multiple options.
String Array	Lists of text values, such as aliases or tab completion entries.
Item Select	Searching Minecraft materials.
Effect Select	Searching potion effects.
Sound Select	Searching sounds and previewing them.
Particle Select	Searching particle types.
Color Select	Choosing colors.
Location	X, Y, Z, and World, or a compact (x,y,z),world value.
Inventory Editor	Editing GUI and inventory slots visually.
Give Item Editor	Configuring custom item material, name, lore, enchantments, flags, and NBT.

Placeholders

Fields with placeholder support can use dynamic values such as %player.name%, %world.name%, or %command.arg[1]%.

Use placeholders when a value should change based on the player, command, event, world, or saved variable.

See Placeholders for the full list.

Conditional Fields

Some fields only appear after you choose a related option. For example:

• Specific username fields appear when the target is Specific Player.
• Permission fields appear when the target is Players with Permission.
• Coordinate fields appear when a location mode uses coordinates.
• Advanced item settings appear when item mode is Item Editor.

Previews

Some fields show previews:

• Message fields can preview Minecraft color codes.
• Sound fields can preview selected sounds.
• Inventory and item editors preview slots and item display data.

Practical Tips

• Required fields must be filled before deployment.
• Do not include a leading / in command fields unless the node specifically asks for it.
• Use clear variable names, such as quest.stage or reward.claimed.
• Prefer placeholders over hard-coded player names when the flow should work for everyone.