The bug
selector
and score
evaluate as blank on signs
How to reproduce
/tellraw @a {"rawtext":[{"selector":"@a"}]}
→ ✔ You get your name
Now place a sign and type in it
{"rawtext":[{"selector":"@a"}]}
→ ❌ It's blank
Comments 2
I know in Java Edition we can place signs with text on them with commands and on placing they will update the text on it, and will not change until another sign is placed on its place.
But we cannot do that on Bedrock, maybe if structure blocks on load they updated signs to recalculate the score we could work with that.
I would strongly advocate for this behavior to work exactly like Java edition, including the ability to place signs with text.
Ideally, this would also include the superior JSON text schema and ability to run commands on signs, but we all know that will not happen.
Confirmed on 1.17.11 Release
How would this behave on large selectors? If it is @a for example is there are, say 10 players, will it just display the first of them and then cut, same as when text is too long?
What about a score which tracks nearest player, and there are many players, it would need to update the sign somehow constantly.
I know in Java Edition we can place signs with text on them with commands and on placing they will update the text on it, and will not change until another sign is placed on its place.
But we cannot do that on Bedrock, maybe if structure blocks on load they updated signs to recalculate the score we could work with that.
Also worth mentioning on written books, and npcs, selector and scores do not work either.