So we updated to the new version of Minecraft, and suddenly we all can't use /msg. When I /msg someone, it just says "No targets matched selector." When I @ everyone it would say <insufficient permissions for selector expansion,> despite being the admin myself. We didn't mess with gamerules as well. We just updated.
Edit: This doesn't happen in local worlds.
Also applies to /w and /tell commands.
Linked issues
is duplicated by 2
Attachments
Comments 11
Can confirm even on v1.16.221, can't refer any player even with "player" or just player with any command requiring targets
I am still unable to reproduce this in a Realm in 1.16.221 Hotfix.
We need more information to be able to reproduce this. Specifically, we need to know how what each person's gamemode and permissions are set to, which person owns the realm, which person issued the command, and what exact command results in the error message. You don't have to give people's real gamertags if you don't want to, just give them letters so we can keep track of who did what.
Unfortunately, until we find a way to reliably reproduce this, we can't send it on to the devs for a fix because they can't fix something that they can't see.
Hello! Here's the specifics:
We're hosting a 1+10 friends realm, and a friend of mine is the owner. Upon creating the world, we only specified a world seed (-783901070). Around 9-10 of us were connected on the first hour of the realm. On that time, a member of the realm, Z, tried using the /msg command to O (/msg O something), and it would just say "No targets matched selector". After this, he told all of us if /msg is still broken. We all tried it on each other, including the realm owner, and it's broken on all of us, regardless if we specify a person or use @a.
Regarding gamemodes and permissions: We're all on survival, and only the server owner has the operator permissions. On gamerules, we only enabled coordinates. We also haven't restored from a backup or added resource packs (we couldn't even add them because it would just give us a "could not be applied" error).
EDIT: We're all from Asia if that matters.
No need to look into this, we're all using standard characters on our gamertags.
As for the second paragraph, sure, I'll get them to upvote this.
EDIT: I'll be adding this in case it comes into play, but "O" has a space on their username. Specifically, it's "O____ ____1523". I don't know how this affects everyone else's ability to /msg different players, but adding it regardless.
By "space in their username" you mean in their gamertag, right? I didn't realize that was possible, and it might be an important clue. It would be very interesting if the problem doesn't happen when they aren't joined, or especially if they're removed from the Members list (they could rejoin afterward if you wanted to experiment with this idea).
There is another ticket reporting this problem, which is linked as a duplicate, so I have enough information to confirm this ticket and pass it along to the devs. We would still appreciate any additional information related to it, however. The kind of information we're looking for is something you do that most players/realms would be unlikely to do the same way, because it would be very helpful if we knew why more players aren't affected by this bug.
Alright, we tried /msg without O on the realm, and it still wouldn't work. Removing him on the members list doesn't fix it, even after closing and reopening the realm.
Update:
After updating to v1.16.221, we can all use /msg now. However MCPE-126266 seems to be having this same problem on the new version as well.