Unable to /kill players in creative mode
When trying to /kill creative players, it'll say "No targets matched selector".
Created Issue:
Unable to /kill players in creative mode
When trying to /kill creative players, it'll say "No targets matched selector".
Deleted Comment:
This is because Bedrock is different from Java edition. You can't kill players in creative because in this game mode they are completely invincible. Notice how when jumping into the void the player doesn't take damage while on Java edition it does. If you wish for there to be parity for this feature I recommend making a post on the feedback site.
Added Linked Issues:
duplicates
the recent update, 1.9, has made it possible for players in creative mode to be killed using /kill(i'm assuming it's the same in the beta). are you typing in "/kill creative players" literally? because that's not the command lol. it's "/kill @e[type=player,m=c]" to kill all players in creative mode
@Khamanei Ainsworth yes I know, before the 1.9 update it used to say "Killed [Player]" even though the player didn't get killed. In 1.9, we were able to kill players in creative mode. I'm not sure if this happened in 1.10 or not, but in 1.11 the command simply doesn't work and says that "No targets matched selector".
Im confused, are you using this command:
/kill "PlayerName"
I'm using /kill @e[type=player]. Creative players won't die, only survival/adventure players will.
Is the /kill command still killing players in release 1.10?
Why is this marked as a duplicate of
MCPE-16732?MCPE-16732was that the game tries to kill players in creative mode and the message says that the player was killed without actually killing it. In 1.9 that bug actually was fixed. You could kill them like any other player. In 1.10 this got broken. It always only targets players that are not in creative mode even when not specifying that in the command. It simply says "No targets matched selector". Since you used to be able to target players in creative mode using the kill command, this is actually a different bug. I don't understand, why this is marked as a duplicate.