We've split up the commands, scripting and mods, and add ons category! Please be sure you get your thread in the right place.

← Commands
3
Follow

On Use

There should be a onuse subcommand added to the execute command. Example syntax:

/execute <target: selector> <position: x y z> use <itemName: Item | all> <command: command>

When the player right clicks (or the equivalent on touchscreen/console) this command would be run. You could then specify an item that the player has to be holding, or use all to allow for any item. (Maybe an array could even be used to allow for multiple items?) Here's an example that would look for any player right clicking a nether wart and teleport them to 10, 5, 7:

/execute @a ~ ~ ~ use nether_wart tp @s 10 5 7

An example setting the block under someone to obsidian if they right click at all:

/execute @a ~ ~ ~ use all setblock ~ ~-1 ~ obsidian

Maybe even allow a ! at the front to allow all but that item (i.e. !air would allow for any item being held except air).

/execute @a ~ ~ ~ use !air say I used an item that wasn't air!

Avatar
Registered User shared this idea

3 Comments

Please sign in to leave a comment.

Date Votes
Sorted by oldest
  • 0
    Registered User commented
    Comment actions Permalink

    The /execute command wasn't meant for scheduling things to happen, it was meant for modifying execution properties. In layman's terms, it modifies the who, what, and where attributes, but wasn't designed to modify the when.

    A better way to do this would probably be to add a scoreboard criteria for these triggers and set up updates - I know this can get a bit cumbersome, but I know that /execute is probably not the best way to go for this.

  • 0
    Registered User commented
    Comment actions Permalink

    ExpertCoder14 the reason I did example syntax at the execute command was just for the Bedrock Edition example, because let’s be honest: are they gonna add scoreboard criteria in Bedrock Edition? If they do, that would have to be an entire thing separately - the introduction of that - and I can’t see that coming the way things are. The most complicated thing like that is the execute detect, which is what I took a spin off of. While it would be better, the Bedrock Team seems to not to want to add things like that and asking for something in that form seems like asking for two things at once.

  • 1
    Registered User commented
    Comment actions Permalink

    No

    The best way is, adding the "use" or "using" item component, and use advancement to detect the use (or a fild in the item component that execute a command if the item is used or it's using)