Summary
Text written on signs can ignore spacing/newline formatting under certain conditions. This might relate to MCPE-20759, but I am quite unsure on this, and I have encountered this only on Realms so far (thus reporting under REALMS).
Reproduction steps
There is no clear situation under which the problem will occur, however when it does occur, all of the following has been observed of the affected signs:
Newline(s)/space(s) is/are added before the affected text.
There is no space between the text; for example,Waterloo
will cause the bug to appear, butWater loo
will not. Formatting symbols also count as text in this case.The text does not overflow onto the next line; for example, if the text starts out on line 2 but more typing causes the text to go to line 3, the bug will not appear.
Video demonstrating the bug: https://youtu.be/pAyDxKMng0c
The bug has been checked to occur without any addons both server-side (Realms) and client-side. The bug may come and go without any clear explanation.
For the provided image the correctly formatted signs (centre-left and centre-right) were obtained by typing §r
at the start of the sign.
Linked issues
is duplicated by 35
relates to 5
Attachments
Comments 15
Been having the same issue but with books.
The game keeps ignoring the spaces i put in there and just groups words together.
It appears to me that signs are retaining their formatting in 1.17.32... until you move to another chunk and the text disappears entirely when you return. Since that's not exactly the issue reported here, I opened MCPE-143812 to track it. I found a similar (but not identical) report from a BDS user, hence using the MCPE project instead of REALMS.
It's reproducing for me now as the owner of a realm. Here is a video of what Zach Guth is talking about:
[media]
The reason it goes back-and-forth is that each time you type something the client updates its display, and it parses the line breaks correctly. Then a moment later the server parses the text incorrectly and sends the corrupted string data back to the the client. This is the same process with the other realms text bugs (MCPE-3491 and related), which have been misunderstood as censoring. My guess is that the realms server either uses a different unicode format than the client when it read/sends string data, or it is running string data parsing functions designed for a different unicode format that what the client uses.
I wish I could tell you. Mojang does not publish plans, prioritization notes, or timetables for fixing bugs.
I'm seeing this on a 1.18.12 Realms server consistently. It seems to be ignoring new lines completely.
Resolving this as CR as we can no longer reproduce this bug.
If this is still an issue please remake the bug report and include detailed reproduction steps, as well as a video showcasing the bug.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
I can confirm this in 1.17.
[media]