mojira.dev
MC-117406

is the execute command broken?

I feel like the execute command is broken now. when I use this command "/execute @a[score_Build=1,score_Build_min=1] ~ ~ ~ /fill ~2 ~-1 ~2 ~-2 ~-1 ~-2 grass" it fills where the command block is. In 1.11 it was where it would execute the player.
I have an idea to fix that though.
When I see ~ ~ ~ I think "where ever they are." so maybe you can add a new command option for execute such as
. If you don't include ~ ~ ~ it will execute the command block
. If you include ~ ~ ~ then it will execute the player
. If you don't include ~ ~ ~ but you do include "detect" then it will execute the command block.
. if you include ~ ~ ~ and "detect" then it will execute the player.
I mean, this may be intentional... but I just don't like it.
How about this though... what if you use "@s." For instance:
/execute @a ~ ~ ~ /execute @s ~ ~ ~ /fill ~ ~ ~ ~ ~ ~ grass
That will execute the player
/execute @a ~ ~ ~ /fill ~ ~ ~ ~ ~ ~ grass
That will execute the command block.
Please fix this "bug" unless its not one...

Linked issues

Comments 1

I realized this too. I made a fireball command but now the fireballs spawn at the command block. This is troubling if they do not fix this. The bug basically erases the execute command's use.

ItsJustShark

(Unassigned)

Unconfirmed

Minecraft 1.12 Pre-Release 2

Retrieved