MCPE-162083Titleraw text shadows do not appear correctly
Creating a title with the new line character & formatted colors causes the text shadows to appear incorrectly for subsequent lines.
To reproduce this bug, create a file en_US.lang in your resource pack & create the translation key:
title.test.sampletext=§4This is line 1.%1This is line 2!
Add the resource pack to a world & run this command:
/titleraw @a title {"rawtext":[{"translate":"title.test.sampletext","with":["\n"]}]}
Instead of the text shadow being consistent between these two lines, they appear differently. This affects map creators. There is probably an easier way to reproduce this issue, but this is how I encountered the bug.
For context, the translation string before the new line character has a shadow color of #2A0000, appropriate for the chosen §4 color code. After the new line, the game chooses #404040, which is the default shadow for uncolored text.
The reason this bug is significant is because title text does not wrap around. Its size is set & translation strings that work with English may be too long in other languages. A new line is necessary to fit more words. The 8 short words in the example string don't fit on a 1080p monitor with GUI scale 0 without a break. Marketplace content should work the same for all devices with default settings without text being hard to read.
I found a workaround: Explicitly redefining the color of subsequent new lines, such as in the example below, allows the game to correctly color the text's shadows.
title.test.sampletext=§4This line is red.%1§4This one is too!
Attachments1
Created Issue:
Titleraw text shadows do not appear correctly
Creating a title with the new line character & formatted colors causes the text shadows to appear incorrectly for subsequent lines.
To reproduce this bug, create a file en_US.lang in your resource pack & create the translation key:
title.test.sampletext=§4This is line 1.%1This is line 2!Add the resource pack to a world & run this command:
{"translate":"title.test.sampletext","with":["\n"]}
/titleraw @a title {"rawtext":[]}
Instead of the text shadow being consistent between these two lines, they appear differently. This affects map creators. There is probably an easier way to reproduce this issue, but this is how I encountered the bug.
For context, the translation string before the new line character has a shadow color of #2A0000, appropriate for the chosen §4 color code. After the new line, the game chooses #404040, which is the default shadow for uncolored text.The reason this bug is significant is because title text does not wrap around. Its size is set & translation strings that work with English may be too long in other languages. A new line is necessary to fit more words. The 8 short words in the example string don't fit on a 1080p monitor with GUI scale 0 without a break. Marketplace content should work the same for all devices with default settings without text being hard to read.
Attachments1
Creating a title with the new line character & formatted colors causes the text shadows to appear incorrectly for subsequent lines.
To reproduce this bug, create a file en_US.lang in your resource pack & create the translation key:
title.test.sampletext=§4This is line 1.%1This is line 2!Add the resource pack to a world & run this command:
{"translate":"title.test.sampletext","with":["\n"]}
/titleraw @a title {"rawtext":[]}
Instead of the text shadow being consistent between these two lines, they appear differently. This affects map creators. There is probably an easier way to reproduce this issue, but this is how I encountered the bug.
For context, the translation string before the new line character has a shadow color of#2A0000, appropriate for the chosen §4 color code. After the new line, the game chooses #404040, which is the default shadow for uncolored text.The reason this bug is significant is because title text does not wrap around. Its size is set & translation strings that work with English may be too long in other languages. A new line is necessary to fit more words. The 8 short words in the example string don't fit on a 1080p monitor with GUI scale 0 without a break. Marketplace content should work the same for all devices with default settings without text being hard to read.
Creating a title with the new line character & formatted colors causes the text shadows to appear incorrectly for subsequent lines.
To reproduce this bug, create a file en_US.lang in your resource pack & create the translation key:
title.test.sampletext=§4This is line 1.%1This is line 2!Add the resource pack to a world & run this command:
{"translate":"title.test.sampletext","with":["\n"]}
*/titleraw @a title {"rawtext":[]}*
Instead of the text shadow being consistent between these two lines, they appear differently. This affects map creators. There is probably an easier way to reproduce this issue, but this is how I encountered the bug.
For context, the translation string before the new line character has a shadow color of #2A0000, appropriate for the chosen §4 color code. After the new line, the game chooses #404040, which is the default shadow for uncolored text.The reason this bug is significant is because title text does not wrap around. Its size is set & translation strings that work with English may be too long in other languages. A new line is necessary to fit more words. The 8 short words in the example string don't fit on a 1080p monitor with GUI scale 0 without a break. Marketplace content should work the same for all devices with default settings without text being hard to read.
I found a workaround: Explicitly redefining the color of subsequent new lines, such as in the example below, allows the game to correctly color the text's shadows.
title.game.moreneeded=§4This line is red.%1§4This one is too!
Creating a title with the new line character & formatted colors causes the text shadows to appear incorrectly for subsequent lines.
To reproduce this bug, create a file en_US.lang in your resource pack & create the translation key:
title.test.sampletext=§4This is line 1.%1This is line 2!Add the resource pack to a world & run this command:
{"translate":"title.test.sampletext","with":["\n"]}
*/titleraw @a title {"rawtext":[]}
*Instead of the text shadow being consistent between these two lines, they appear differently. This affects map creators. There is probably an easier way to reproduce this issue, but this is how I encountered the bug.
For context, the translation string before the new line character has a shadow color of #2A0000, appropriate for the chosen §4 color code. After the new line, the game chooses #404040, which is the default shadow for uncolored text.The reason this bug is significant is because title text does not wrap around. Its size is set & translation strings that work with English may be too long in other languages. A new line is necessary to fit more words. The 8 short words in the example string don't fit on a 1080p monitor with GUI scale 0 without a break. Marketplace content should work the same for all devices with default settings without text being hard to read.
I found a workaround: Explicitly redefining the color of subsequent new lines, such as in the example below, allows the game to correctly color the text's shadows.
title.game.moreneeded=§4This line is red.%1§4This one is too!Creating a title with the new line character & formatted colors causes the text shadows to appear incorrectly for subsequent lines.
To reproduce this bug, create a file en_US.lang in your resource pack & create the translation key:
title.test.sampletext=§4This is line 1.%1This is line 2!Add the resource pack to a world & run this command:
{"translate":"title.test.sampletext","with":["\n"]}
_/titleraw @a title {"rawtext":[]}_
Instead of the text shadow being consistent between these two lines, they appear differently. This affects map creators. There is probably an easier way to reproduce this issue, but this is how I encountered the bug.
For context, the translation string before the new line character has a shadow color of #2A0000, appropriate for the chosen §4 color code. After the new line, the game chooses #404040, which is the default shadow for uncolored text.The reason this bug is significant is because title text does not wrap around. Its size is set & translation strings that work with English may be too long in other languages. A new line is necessary to fit more words. The 8 short words in the example string don't fit on a 1080p monitor with GUI scale 0 without a break. Marketplace content should work the same for all devices with default settings without text being hard to read.
I found a workaround: Explicitly redefining the color of subsequent new lines, such as in the example below, allows the game to correctly color the text's shadows.
title.game.moreneeded=§4This line is red.%1§4This one is too!
Creating a title with the new line character & formatted colors causes the text shadows to appear incorrectly for subsequent lines.
To reproduce this bug, create a file en_US.lang in your resource pack & create the translation key:
title.test.sampletext=§4This is line 1.%1This is line 2!Add the resource pack to a world & run this command:
{"translate":"title.test.sampletext","with":["\n"]}
_/titleraw @a title {"rawtext":[]}_
Instead of the text shadow being consistent between these two lines, they appear differently. This affects map creators. There is probably an easier way to reproduce this issue, but this is how I encountered the bug.
For context, the translation string before the new line character has a shadow color of #2A0000, appropriate for the chosen §4 color code. After the new line, the game chooses #404040, which is the default shadow for uncolored text.The reason this bug is significant is because title text does not wrap around. Its size is set & translation strings that work with English may be too long in other languages. A new line is necessary to fit more words. The 8 short words in the example string don't fit on a 1080p monitor with GUI scale 0 without a break. Marketplace content should work the same for all devices with default settings without text being hard to read.
I found a workaround: Explicitly redefining the color of subsequent new lines, such as in the example below, allows the game to correctly color the text's shadows.
title.game.moreneeded=§4This line is red.%1§4This one is too!Creating a title with the new line character & formatted colors causes the text shadows to appear incorrectly for subsequent lines.
To reproduce this bug, create a file en_US.lang in your resource pack & create the translation key:
title.test.sampletext=§4This is line 1.%1This is line 2!Add the resource pack to a world & run this command:
/titleraw @a title {"rawtext":[{"translate":"title.test.sampletext","with":["\n"]}]}Instead of the text shadow being consistent between these two lines, they appear differently. This affects map creators. There is probably an easier way to reproduce this issue, but this is how I encountered the bug.
For context, the translation string before the new line character has a shadow color of #2A0000, appropriate for the chosen §4 color code. After the new line, the game chooses #404040, which is the default shadow for uncolored text.The reason this bug is significant is because title text does not wrap around. Its size is set & translation strings that work with English may be too long in other languages. A new line is necessary to fit more words. The 8 short words in the example string don't fit on a 1080p monitor with GUI scale 0 without a break. Marketplace content should work the same for all devices with default settings without text being hard to read.
I found a workaround: Explicitly redefining the color of subsequent new lines, such as in the example below, allows the game to correctly color the text's shadows.
title.game.moreneeded=§4This line is red.%1§4This one is too!
Creating a title with the new line character & formatted colors causes the text shadows to appear incorrectly for subsequent lines.
To reproduce this bug, create a file en_US.lang in your resource pack & create the translation key:
title.test.sampletext=§4This is line 1.%1This is line 2!Add the resource pack to a world & run this command:
/titleraw @a title {"rawtext":[{"translate":"title.test.sampletext","with":["\n"]}]}Instead of the text shadow being consistent between these two lines, they appear differently. This affects map creators. There is probably an easier way to reproduce this issue, but this is how I encountered the bug.
For context, the translation string before the new line character has a shadow color of #2A0000, appropriate for the chosen §4 color code. After the new line, the game chooses #404040, which is the default shadow for uncolored text.The reason this bug is significant is because title text does not wrap around. Its size is set & translation strings that work with English may be too long in other languages. A new line is necessary to fit more words. The 8 short words in the example string don't fit on a 1080p monitor with GUI scale 0 without a break. Marketplace content should work the same for all devices with default settings without text being hard to read.
I found a workaround: Explicitly redefining the color of subsequent new lines, such as in the example below, allows the game to correctly color the text's shadows.
title.game.moreneeded=§4This line is red.%1§4This one is too!Creating a title with the new line character & formatted colors causes the text shadows to appear incorrectly for subsequent lines.
To reproduce this bug, create a file en_US.lang in your resource pack & create the translation key:
title.test.sampletext=§4This is line 1.%1This is line 2!Add the resource pack to a world & run this command:
/titleraw @a title {"rawtext":[{"translate":"title.test.sampletext","with":["\n"]}]}Instead of the text shadow being consistent between these two lines, they appear differently. This affects map creators. There is probably an easier way to reproduce this issue, but this is how I encountered the bug.
For context, the translation string before the new line character has a shadow color of #2A0000, appropriate for the chosen §4 color code. After the new line, the game chooses #404040, which is the default shadow for uncolored text.The reason this bug is significant is because title text does not wrap around. Its size is set & translation strings that work with English may be too long in other languages. A new line is necessary to fit more words. The 8 short words in the example string don't fit on a 1080p monitor with GUI scale 0 without a break. Marketplace content should work the same for all devices with default settings without text being hard to read.
I found a workaround: Explicitly redefining the color of subsequent new lines, such as in the example below, allows the game to correctly color the text's shadows.
title.test.sampletext=§4This line is red.%1§4This one is too!
![[MCQA] Bartłomiej Słodkowski](../../../data/avatars/users/18941.svg){kind=small}
![[MCQA] Kinga Izdebska](../../../data/avatars/users/18949.svg){kind=small}
Affects 1.19.22
Workaround is to use new line characters via translation keys, but another bug prevents itself: MCPE-162083
Workaround for the workaround provided in report.
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Could you please attach an example resource pack that showcases the issue?
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📓 Project Summary – 📧 Suggestions – 📖 Minecraft Wiki
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki