MC-41410Random text does not work in unicode
When the unicode option in language is on the random text (§r) doesn't work.
/tellraw @p {"text":"Test☂","obfuscated":true}
Fix by Marcono1234 can be found in this comment.
Linked Issues
is duplicated by3
Created Issue:
Random text don´t work in unicode
When the unicode option in language is on the random text (§r) don´t work.
Environment
Windows XP SP3 32-bit Home Edition
Java 7U45 32-bit
Attachments2
This ticket is incomplete without the requested information, no response has been received within a reasonable time and we are assuming this is no longer an issue. If you are still experiencing this issue, we can reopen it at your request.
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
When the unicode option in language is on the random text (§r) don´t work.
Could you please include this?
relates to
When the unicode option in language is on the random text (§r) don´t work.
/tellraw @p {"text":"Test☂","obfuscated":true}
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
Random text don´t work in unicodeRandom text does not work in unicode
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
When the unicode option in language is on the random text (§r) do
n´t work./tellraw @p {"text":"Test☂","obfuscated":true}When the unicode option in language is on the random text (§r) doesn't work.
/tellraw @p {"text":"Test☂","obfuscated":true}Fix by Marcono1234 can be found in this comment.
When the unicode option in language is on the random text (§r) doesn't work.
/tellraw @p {"text":"Test☂","obfuscated":true}
Fix by Marcono1234 can be found in this comment.
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
[Mojang] Nathan Adams
Updated issue, excuse me for long waiting time.
Please do not mark unreleased versions (anything starting with "Future Version") as affected. You don't have access to them yet.
I can confirm for 1.8.1-pre3.
It also doesn't display the random text in chat on unicode.
It's §k for random text though.
Steps to reproduce:
1. Get a writeable book and open it.
2. Copy paste "§kTest" into it. You should now see random text. (Unless you did step 3 already)
3. Go to the language settings and enable "Force Unicode Font"
4. Open the book again and see that the text is not random now.
Reopened and Confirmed, thanks
Its definitely confirmed. Also, here's another way to reproduce:
Call any commands that supports "json". e.g. /tellraw. Adopt the "Obfuscated" style by something like /tellraw @a {"text":"","extra":[{"text":"MAGIC!","obfuscated":"true"}]}. You'll first see the magical effect on the chat window. Attempt to turn on "Force Unicode Font" (or switch to a language that uses Unicode font), and then the effect is lost. The text will only appear static and as same as what you've entered.
Confirmed for
This was partwise fixed as the default characters will be displayed now in unicode, however characters that are unicode characters by default are still not random.
The reason for this was in 1.8 that the renderStringAtPos(String p_78255_1_, boolean p_78255_2_) method in the /Client/src/net/minecraft/client/gui/FontRenderer.java class (MCP 1.8 names) first tested is a character is in a default character (bold ones), if so it would pass the index to the rendering method or -1 if it is not contained. Because unicode rendering is based on the unicode value of a character the rendering method needed a character being passed as well. However the character passed was always the non randomized character (this seems to be fixed now).
The problem is still that unicode characters are not randomized because they are not default characters so the game will not choose a random character for them. For 1.8 you could change the method so it would in case unicode is not forced first try to find a default character with the same width and in case it fails choose a unicode character.
Note: This and the rendering code could be improved by only finding the default character position if it is not already -1 or if unicode is not used.
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w42a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time.
1.12 Pre6 snapshot
I put the following code in a command block then had it give me a sign:
give @p minecraft:sign 1 0 {BlockEntityTag:{Text1:"{\"text\":\"OH NO!\",\"clickEvent\":{\"action\":\"run_command\",\"value\":\"minecraft:tp @p 100 49 0\"},\"bold\":true,\"color\":\"dark_red\"}",Text2:"[\"\",{\"text\":\"The \"},{\"text\":\"flip\",\"obfuscated\":true,\"color\":\"aqua\"},{\"text\":\" broke.\"}]",Text3:"{\"text\":\"Right-click\"}",Text4:"{\"text\":\"this sign!\"}"},display:{Name:"End Spawn"}}I get the following text on the resulting sign:
OH NO!
["",{"TEXT":"The
Right-click
this sign!
I suspect I'm being bit by this bug in 1.12 Pre6. I'll come up with different text.
@Andy (Romaq) Smith I cannot confirm what you are describing for 1.12-pre6. For me the second line is displayed correctly.
Edit: I suspect you are using it with a modded version of Minecraft since you are using minecraft:tp instead of tp or /tp. Modded versions are not supported here.
You are correct, I should have verified in Vanilla first. I'll pass the link to this bug report to Spigot's bug tracker as it may help pinpoint where to update Spigot code. Thank you, it would appear this should be resolved and closed for Vanilla.