Actions & Requirements

Actions

Actions run in order. Any action reference can also carry per-action modifiers — a delay in ticks, a chance percent, and a fallback to run if the chance roll fails — when written as a block instead of a bare string.

The table below is the common set; the engine ships around sixty action ids in total (plus aliases), and modules and the Menu API can register more. Use /menu dump <menu> to see exactly what a menu resolves.

Requirements

A requirement decides whether a click's actions run, or whether a tile is even visible. Every requirement is a condition reference; a leading ! inverts it.

mcMMO levels. mcmmo-level: takes the skill name mcMMO itself uses (mining, woodcutting, axes, ...) then the level: mcmmo-level:mining:50 shows the tile only to players who have reached mining 50. mcmmo-power:1000 checks the power level, the sum across every skill. An unknown skill name is false, not an error.

Per-gesture click blocks

A gesture can be a bare action list, or a block that gates its actions behind requirements and runs a deny list (or an else fallback) when the gate fails.

click {
  # Simple form: always runs on left-click.
  left = ["command:kit starter", "close"]

  # Gated form on right-click.
  right {
    requirements = ["perm:uxmessentials.vip", "has-money:100"]
    minimum = 2                       # both must pass (see below)
    actions = ["take-money:100", "command:kit vip"]
    deny = ["message:<red>VIPs only, and it costs 100."]
  }

  # 'any' fires alongside whichever gesture the player used.
  any = ["sound:UI_BUTTON_CLICK"]
}

minimum — how requirements combine

The minimum key turns a requirement list into AND / OR / N-of-M without a separate flag:

View requirements

The same block gates a tile's visibility. A flat list is an all-must-pass AND; the block form lets you use minimum and inversion.

# Flat form — hide unless BOTH hold.
view = ["perm:uxmessentials.vip", "!world:spawn"]

# Block form — show if the player meets ANY one of the three.
view {
  requirements = ["perm:uxmessentials.tier1", "perm:uxmessentials.tier2", "has-money:1000"]
  minimum = 1
}

A tile whose view fails is not drawn at all — it does not appear greyed-out, it simply isn't there.

Next Steps

• Custom Menu Engine — the full spec and a worked example.
• Menu API — register your own actions, conditions and placeholders.
• Permission Reference — nodes for perm: conditions.
• Bedrock Forms — how these menus render for Floodgate players.