Events and flow

Every interactive feature starts with an event. Wires from its then port run steps in sequence, with each step’s then leading to the next. All logic runs on the server.

Steps

When a flow output connects to several steps, they run one after another from top to bottom on the canvas.

If checks its condition and continues through either true or false.

For each nearby runs the steps after each once for every player or mob inside a box extending Within blocks from its position in every direction. Wire its Player (or Entity) output into those steps to act on each target. Only steps inside the loop can read that output, and execution stops after the loop finishes, so place any single-run steps before it. Enable Exclude one to skip the entity wired into Excluded (or the event’s own player or mob when left unwired).

Count nearby returns how many players or mobs are inside that same box. Use it when a step should run once based on crowd size, such as sending a warning when players gather. When counting players, the triggering player is included.

Waiting

Wait runs the steps after it once Seconds have passed, while the rest of the game goes on. For example, to explode a block three seconds after it is placed, run Wait from When block is placed, then Explode.

The steps after a Wait read their values when they run, not when the event happened: Player position gives where the player is by then. To use a value from the moment of the event, pass it through Keep value before the Wait. Cancel event and Change damage can’t run after a Wait, since the event is over by then. If the player has left the game before the wait ends, steps that act on them may not run, and waiting steps are dropped when the world closes.

Values

Value wires pass a player, entity, world, position, number, boolean (true or false), item, or block into an input. A single output can feed multiple inputs.

Select outputs Then when If is true, and Else otherwise. Its output type matches whatever you wire into it.

Values are recalculated each time an input reads them. Wiring Random chance into two If nodes rolls twice, and reading Health after Heal reflects the updated health. To compute a value once and share it across several steps, place Keep value in the flow beforehand: it captures the input value as the flow passes through, and every wire from it reads that saved result.

You can also wire a Player or Entity output directly into a Position input. This uses the block coordinates at their feet (just like Player position) and labels the input accordingly, such as Position of Player from When item is used. Like any other value wire, it is evaluated each time a step reads it; to capture where a player stood before Teleport moves them, pass the player through Keep value first.

Unwired inputs

Input Default when unwired
Player The event’s player
Entity The event’s entity, or its player if there is no separate entity
World The event’s world
Position The event’s position output, such as Killed entity position or Block position
Number The number set on the node

If an event has no position of its own (such as When item is used), wire a Position into the step, such as the event’s Player output to use the player’s current position.

Inside a function, unwired inputs default to the function’s own input of that type.

Mob filters

Leaving an event’s Mobs list empty makes it run for every mob, animal, and player. (When mob steps on block always excludes players.)

Ticks

There are 20 ticks in one second.

Every N ticks runs once for each online player every Ticks ticks. When For players is set, it runs only for players holding or wearing one of the listed Items (armor must be equipped in its matching armor slot). Keep Ticks as high as your feature allows, and see Performance for tips on keeping tick logic fast.

Every N ticks for mobs works the same way for every loaded mob and animal, or only the types listed in Mobs.

Every N ticks for blocks runs for each placed block from Blocks in loaded chunks, providing its Block position. Use it for beacons, generators, and blocks that heal or damage nearby players. On Java Edition, blocks only begin ticking once placed, so naturally generated blocks like ores and trees won’t tick. Vanilla ticking blocks such as buttons, pressure plates, doors, leaves, and falling blocks like sand manage their own ticks and cannot be listed here.

When player steps on block runs every tick while a player stands on one of its Blocks, and When mob steps on block does the same for mobs and animals. Because these run every tick, keep their steps lightweight; see Performance for details.

Jumping, sleeping, and chat

When player jumps runs when a player leaves the ground. Pressing jump again in mid-air isn’t detected, so it cannot be used for double jumps.

When player falls asleep runs once when a player gets into bed. When player wakes up runs whenever they leave the bed, whether morning has arrived or they got up early. To grant a reward only after a full night’s sleep, check World is day afterward.

When player chats runs when a chat message contains its filter text (case-insensitive), or on every message when the filter is empty. Cancel event suppresses the message. This event isn’t available on Bedrock Edition.

Picking up and dropping items

When player picks up item runs when a player picks up one of the listed Items from the ground, or any item if none are listed. When player drops item runs when a player tosses an item from their inventory. Player position is where the player stands, and neither event can be canceled.

Changing dimensions

When player changes dimension runs when a player arrives in another dimension through a portal or teleport, matching either a chosen To dimension or any dimension. World and Player position give their arrival location. On Java Edition, leaving the End through the exit portal and respawning after death count as respawning rather than changing dimensions, so this event does not run.

Sneaking

When player sneaks runs once when a player starts sneaking, rather than repeating while they hold the key. Use Is sneaking to check whether they are currently sneaking.

Left-clicking blocks

When block is left-clicked runs when a player starts hitting one of the listed Blocks, in both survival and creative. It can run again while they keep hitting a block that doesn’t break. On Java Edition it runs before the block breaks, and on Bedrock Edition after the hit. To run something when the block breaks, use When block is broken.

Keys

When key is pressed adds a key to the game’s Controls screen, listed under your mod’s name as its Name. Key is the key it starts on, chosen from keys Minecraft leaves free, and each player can rebind it in Controls. It runs once per press, for the player who pressed it, and holding the key doesn’t repeat it. Give each key node a different Name and Key. For an ability with a wait between uses, check Is on cooldown first, then run Start cooldown after it.

Bedrock Edition has no custom keys, so the node isn’t available there. Use When player sneaks or When player jumps instead.

Crafting and levels

When player crafts item runs when a player takes a crafted item from a crafting table or inventory crafting grid, matching either the listed Items or any item when the list is empty. This event isn’t available on Bedrock Edition.

When player levels up runs when a player’s experience level increases, with Level reached providing their new level. Gaining multiple levels in a single tick (for example, from /xp) triggers the event once.

Names and game modes

Set name gives an entity a name, shown when a player looks at it, as with a name tag. An empty Name removes it. On Java Edition players keep their own names; on Bedrock Edition the name replaces the one above the player’s head.

Set game mode switches a player to survival, creative, adventure, or spectator mode. Entity is with In game mode returns true when the entity is a player in the chosen mode (for example, check survival so that players in creative mode are left out).

Taking items

Take item removes up to Count matching Items from a player’s inventory (including equipped armor), or removes as many as they have if they carry fewer. Item count returns how many matching items the player is carrying. To build a shop or require an item cost, compare Item count with Compare first, then run Take item and grant the reward.

Numbers in messages

Send message and Show title have a Value input. Write {value} in the text (or the title) where the number should appear, for example Coins: {value}. Whole numbers show without decimals and other numbers are rounded to one decimal place. If the text has no {value}, the number is added at the end.

Pulling items

Pull items moves every dropped item within Radius blocks onto a position. A player standing there picks them up after the usual pickup delay. To build a magnet, run it from Every N ticks at the player’s position.