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

Focusing relative and local coordinates

My idea will reduce the amount of code requred to do certain commands, and even add possibilities to what you can do. What I would like to do is create a way to make local and relative (^ / ~) coordinates relative to another entity. Personally, what we could do is that you enter a target, add a colon, then enter the coordinates. It could turn this:

/execute @e[type=snowball] ~ ~ ~ setblock ^1 ^1 ^1 air

into this:

/setblock @e[type=snowball]:^1 ^1 ^1 air

Clearly, we can see that although it does the same thing, the second is much shorter in writing. This way will also allow mobs and players to be relative too, as it turns out that you can't execute anything on behalf of them. The reason why this would work is because you aren't executing as them, but instead executing something relative to them. Here is an example - this wouldn't work...

/execute Player ~ ~ ~ particle evoker_spell ~ ~ ~

...but this would...

/particle evoker_spell Player:~ ~ ~

...and it doesn't take up as many characters.

I really hope you like this idea, and also can't wait to see this in the game!!

Avatar
Registered User shared this idea

3 Comments

Please sign in to leave a comment.

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

    Java Edition does this gracefully with the /execute at command:

    execute at @e[type=snowball] setblock ^ ^ ^1 air
  • 2
    Registered User commented
    Comment actions Permalink

    Oh, I only do bedrock edition, and my examples followed so.

  • 2
    Registered User commented
    Comment actions Permalink

    RegularCube7388 I understand most of the users here are MCBE players. While it would be nice to have the new version of /execute in Bedrock Edition, something tells me that it might not happen for a little while. Your idea with the colon (:), unfortunately, makes the syntax needlessly complicated. Commands are optimized for ease of entry, not for shortest length. Therefore, I have an alternative proposal:

    Allow the entry of a target selector instead of coordinates in the /execute command specifying the position to execute at. Syntax:

    execute <origin: target> <position: x y z> <command: command> # old behaviour
    execute <origin: target> <position: target> <command: command> # allows entity selection
    execute <position: target> <command: command>

    The first two examples are the old behaviour, plus the allowance of selecting an entity by using a target selector instead. The reason I also put a third example is if you want to put it in a command block, because the selector @s doesn't work with that.