mojira.dev

notshige

Assigned

No issues.

Reported

REALMS-7760 Get "No targets matched selector" when use /msg, /tell, /w commands. Fixed

Comments

Can vouch on this bug. WASD keys don't work when I am midair as well. I am using a world from 1.19.2, not a newly generated one. Here's a video of it.

Update: The 1.17.11 hotfix has fixed it for us! We can use /msg, /tell, and /w now.

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.

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. 

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.

Another update:

So a friend of mine made a new realm on 1.16.221, and the bug reappeared.

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.