Affects Version/s: Minecraft 17w13a, Minecraft 17w13b, Minecraft 17w14a, Minecraft 17w15a, Minecraft 17w16b, Minecraft 17w17b, Minecraft 17w18a, Minecraft 17w18b, Minecraft 1.12 Pre-Release 1, Minecraft 1.12 Pre-Release 2, Minecraft 1.12 Pre-Release 3, Minecraft 1.12 Pre-Release 4, Minecraft 1.12 Pre-Release 5, Minecraft 1.12 Pre-Release 6, Minecraft 1.12 Pre-Release 7, Minecraft 1.12, Minecraft 17w31a, Minecraft 1.12.1 Pre-Release 1, Minecraft 1.12.1, Minecraft 1.12.2 Pre-Release 1, Minecraft 1.12.2 Pre-Release 2, Minecraft 1.12.2, Minecraft 17w43a, Minecraft 17w43b, Minecraft 17w45a, Minecraft 17w46a, Minecraft 17w48a, Minecraft 17w50a
Fix Version/s: Minecraft 18w01a
Environment:Windows 10 Pro 64-Bit (10.0, Build 15063)
The new narrator feature reads the §-based formatting codes generated by the scoreboard (see
1. Leave your current scoreboard team, and create a new empty one (needed to ensure that residual naming properties are not left).
2. Enable narrator.
3. Paste a copypasta; it will be read with your name as normal.
4. Set a color onto the team; the specific one doesn't matter (it can even be reset, and the bug will still happen). Numeric colors such as blue work best.
5. Paste the copypasta. Your name will be read with surrounding color codes, for instance, "9 pokechu r".
As a series of chat messages/commands:
Probably, narrator is implemented using the component's raw text (mcp calls it getUnformattedText. However, due to
MC-112693, format codes can still be put into that text, meaning that narrator would receive a string starting with "<§9pokechu22§r>", and diligently read that.
The ideal fix for this issue would be to fix
MC-112693. Alternatively, the narrator library could strip out §-based color codes, as it already does with < and >.
Here's what it's like without a team color:
... and with a team color: