MC-65290/execute kill requires arguments
Running a command such as
/execute @p ~ ~ ~ kill
requires arguments to be added to kill, despite /kill not requiring any arguments when ran by a player.
A good example would be a command that kills any entity standing on a specific block.
/execute @e ~ ~ ~ detect ~ ~-1 ~ dirt 2 kill @e
This command kills every entity on the map, so ideally we would drop the arguments to kill, so entities kill themselves, but you cannot.
Environment
Windows 7 64-bit
Linked Issues
is duplicated by1
Created Issue:
/execute kill requires arguments
Running a command such as
/execute @p ~ ~ ~ kill
requires arguments to be added to kill, despite /kill not requiring any arguments when ran by a player.
A good example would be a command that kills any entity standing on a specific block.
/execute @e ~ ~ ~ detect ~ ~-1 ~ dirt 2 kill @e
This command kills every entity on the map, so ideally we would drop the arguments to kill, so entities kill themselves, but you cannot.Environment
Windows 7 64-bit
is duplicated by
relates to
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
[Mojang] Grum (Erik Broes)A comment with security level 'global-moderators' was removed.
Duplicate of MC-65290
Confirmed for
- 1.8.4 it will give you first the syntax error: Syntax:/scoreboard teams join <team> [<player>] and then the error message that it failed executing the command
Confirmed for every command with optional player argument, so /kill, /gamemode MODE and maybe some more.
Maybe relates to: MC-78779
And partwise duplicates: MC-65290
This has been fixed for relative coordinates in 16w21b. I would like to sincerely thank Mojang for actually fixing the bug instead of taking the approach they did with MC-108. I can now finally get my teleporters working the way they should.
Unfortunately, the other bug detailed in this report (needing an argument in an execute command when a command actually run by the player doesn't need one) has not yet been fixed. I suggest that they are split into 2 separate reports- change this one to be about relative coordinates, and make MC-65290 about the unnecessary arguments.
Works as Intended.
/kill actually does require a selector. Try it in a command block, you'll see a target has to be selected.
/kill itself only works by typing in chat.
Also, your dirt command will kill everything in the world if one entity is on dirt, that's how the command you've entered is interpreted. You'd have specify the selector more accurately to only target those on the podzol.
Intended.
kill is a universal command anyway. Why would you need an execute for it?
Does anyone think that this is an issue, or is the community consensous that this is intended?
Intended.
Confirmed for
Duplicates very likely
MC-79677