Summary:
The /kick says it allows target selectors in the autocomplete, but the command refuses to use them for unknown reasons.
Steps to Reproduce:
Have someone join your world
Run /tag <player> add example to tag the player as "example"
Run the command: /kick @a[tag=example]
Expected Results:
The player is kicked out of your world
Observed Results:
The command execution fails
Original Title: /kick command does not work with target selectors
Original Description:
The ban system no longer works Inden man /kick @a[tag=ban]
How should a city build run if you can't build an antihacking system because it can't kick anymore when the system detects that it is flying or that an item is hacked
Linked issues
is duplicated by 20
BDS-13966
kick command not working as intended
Resolved
BDS-14226
Kick command with Target selector not working!
Resolved
MCPE-86156
Using /kick with target selectors gives code error
Resolved
MCPE-89420
using /kick command with identifiers gives you a weird "syntax error'
Resolved
MCPE-130323
/Kick command
Resolved
Attachments
Comments 12
I have the same issue on my realm. Can't kick anyone by selectors anymore, which means I need to create individual command blocks for each person, especially if the owner is unavailable to help at the moment.
This may be intended due to the 1.17.0 changelog.
if Mojang does something on purpose then you must be aware that you are chasing away the players, because you can then no longer protect yourself against hackers and why did you / kick only inserted with 1.16 when you added the most important thing to him with 1.17 remove. where is the logic?
Simply, there is a big issue with this.
Mojang want players to buy realms (obviously since they want to make money) that's reasonable, what's not reasonable is taking away target selectors and not giving any alternative or even just a fix for hackers on realms in general. The amount of exploits on realms with no fix is unbelievable, hackers can have access to operator commands and can crash the realm at will (done by sending an invalid packet to the realm, not like its going to be fixed any time soon), and cant even be stopped from doing so. The new spoof mode for hacked clients spoofs the command block as a bee and also uses an invalid item so we cant clear them of that item meaning to counter this we would have to disable bees as well as: beehives, beenests, command block minecarts. This brings me to my main point, the fact that stopping target selectors from working with the kick command was one of the only (and not perfect in any way) to counter this. By detecting if a player was within a certain radius of the command block minecart we could then use /kick @p[r=7] but since we cant even use this anymore, what are we supposed to do, just let hackers ruin the realms we PAY for.
This is not trying to send hate to Mojang or anyone else, I am simply trying to make the realm experience better for players and admins.
I'd like to request ownership because the reporter hasn't been active for more than 2 years, also to continue updates
The other commands that are broke which relates to this issue still in 1.20.81! is the following
/op and /deop please get this fixed really annoying trying to do some stuff with these features and cant because of these bugs please just get them fixed minecraft
The '/ kick' command works properly again with cheats and command blocks disabled and no longer uses target selectors
yes right now it no longer works with selectors not even / kick @a because he wants the name And if someone with a console joint and thus with options for example test1234 is his Microsoft name harald1234 and then you have to enter the Microsoft name so you can not even use autofill because only the console name can be filled
I hope it will be changed again quickly because I don't really want to stop playing minecraft, especially since I've already invested so much time to write the more than 2 million command blocks