Alternative Summary/Title: "sign GUI does not match final product"
On our Realm, I've tried naming a Sign, however Line Breaks don't get registered. I've Tried that on a different World (not realm) and had no issues... why is that?
[media]This could be somewhat related to MC-99863, but I'm not sure.
(End of required Info)
Notes:
-(/) More testing should be done- Bug Confirmed, no more Testing needed, yet still appreciated
_(?) Maybe a Temporary Workaround with special characters (?)_
_(?) The cause of the issue (Client side ~(less likely, due to Attachement 1)~ or {+}Server side{+}?)_
Attachment 1:
[media]Related issues
Attachments
Comments


This is super fustrating. Please note this happens with books too.

Can confirm for 1.17.11.

Can confirm this only works on realms. Have not yet found a workaround but I know special characters like the section sign are also affected by said bug.

Padding out blank lines with spaces doesn't work as a workaround. This is really messing with the formatting on a few signs I'm trying to place next to each other. Also confirming for 1.17.11 (happening on realm, both XBox and Win10).

Can confirm for 1.17.30.

Really frustrating.... The only workaround i found is trying to write longer words: "forest \n nether portal" -> "forest \n nether_portal"... but there are cases where this can't be used, and its uglier.
I was really counting on a fix with update 1.18
Please, also anyone write here other workarounds, like commands equivalent to "\n" if such a thing exists, or a formatting command to have invisible text... anything.

Still broken in 1.17.30 Realms, win10 client. I've recorded a video, please check bellow:
100MB MKV video: https://drive.google.com/file/d/1LEUm51i-ZROgg4cANa35b9hHbLkHhbIC/view?usp=sharing
Attached an image with video caps, highlighting one of the pages where the line breaks didn't saved properly: https://bugs.mojang.com/secure/attachment/444082/MC%20Realms%201.17.30%20-%20%20Book%20and%20Quill%20Line%20Break%20Error%20-%202021-09-30.png

Clayton de Oliveira Jr: It is not necessary to confirm versions that other comments have already confirmed. The Realms project does not necessarily show every Bedrock release version.
Also, please do not comment about other bugs on a ticket unless you are adding new information about how they are related. The other problem you commented about is already tracked at REALMS-3491.

@GoldenHelmet thanks, I've tried to find that other issue to no avail (Didn't know MC had an internal censorship algorithm 😃)

Can confirm for 1.17.32

HUH?! I have just joined our realm on version 1.17.32 and the issue is GONE?! Could you others check if the issue is also gone at your end?

The issue is not gone. Please update this bug to include 1.17.32.
Reply from @unknown: please read my previous comment.

Can you provide an example of text that triggers this bug in 1.17.32? I do not get it with the example text shown in the description.

Can confirm it's still broken in 1.17.32. Just tested it on my book & quill, wich you can see here:
[media]and in the video: https://drive.google.com/file/d/1LEUm51i-ZROgg4cANa35b9hHbLkHhbIC/view?usp=sharing
As I said before, it's a long book (35 pg), originated from a UTF8 txt file, via copy and paste directly in the book UI.
Something I didn't noticed before: sometimes you succesfully corrects the line breaks in a page, but them the breaks in another page disappear.
EDIT: attached a file with the text I used in my book and quill. Please refer to the video.

This issue comes and goes, it sometimes happens, and sometimes doesn't. Also with books and it's even more frustrating with them. (And it likely doesn't depend on what text you input)

I also have the impression it doesn't depend on the text input, because it happens randomly. Looks like some faulty memory management, or maybe related to the also faulty anti-swear filter (wich removes/replaces random words and characters – maybe there are line breaks in profanity_filter.wlist?).

This is slightly different, but still broken, in 1.17.40.
Signs containing only words now retain manually-entered line breaks as expected.
However, signs containing color formatting codes and/or non-word characters continue to behave as if the user didn't enter any carriage returns at all.
To reproduce:
Create a sign with the text:
§f-->
§bTunnel 1 East
§fTown 1
§fTown 2
Expected result:
The sign has four lines. The first, third, and fourth lines are white; the second is cyan. This was the behavior prior to 1.17.
Actual result:
The sign appears with the color formatting but without the user-entered line breaks. (In 1.17.30, the sign would appear without the line breaks and without the color formatting, as if the § character was simply omitted.)

I did further testing last night and found that this isn't consistently reproducible. Sometimes it happens, sometimes it doesn't, and I haven't yet narrowed down any additional factors.
In either case, the sign text will disappear entirely when the chunk reloads (see REALMS-9191).
The net result is that signs are useless on Realms in 1.17. If you can get them to display text at all, never mind display them with the desired formatting, they will go blank the next time you leave the area or log out.

The signs prior to 17.3.x used to work just fine, so it has to do with this newer Realms' version. (Except for line breaks, that issue isn't new)

@@unknown , in fact it is reproductible, but happens on random line breaks over the text. It is easier to verify on books & quills with many pages, because they would have more text.
By the way, now (1.17.40) we have another bug on top of that, making text in signs and books disappearing or not saving... refer to MCPE-146229, REALMS-9191, REALMS-9223 and REALMS-9231.

Happens to me as well, and the text is randomly disappearing as well REALMS-9553

People have mentioned that it happens randomly, but I don't believe that to be the case. What makes it seem random in my experience is that when it works, the chat/sign bug REALMS-9191 is happening... which seems to suggest that this issue only appears server-side.
I'd say it does seem to be related to the overly aggressive profanity filter which I assume they added more patterns to in a recent update, but the profanity filter changes words to asterisks even when the chaat bug occurs.. so either it filters on both sides, or it's not the chat filter

I added myown experience with signs, it has yet to happen to me with a book. It occured on a realm while I'm on my phone.

Since all the linebreak-related issues seem to be getting funneled to this tracker, I will add what I have observed about book and quills on a Realm.
When attempting to make a bulleted list in a book and quill, I encountered an issue whereupon any text on an EVEN numbered page would lose its linebreaks. Any lists formatted the same on an ODD numbered page would retain that formatting. While editing the book, linebreaks would remain, but the moment I close the book (not sign and close, just exit out of the book and quill interface), and reopen it, text on even numbered pages would have all their text pulled back into a single wrapped line, causing characters that I set to denote the beginning of a new line for readability to wind up in various spots on the page.
And in another book, it was the reverse: ODD pages lost linebreaks while EVEN pages kept theirs. But so far, it was never both at the same time, in any one book and quill. It was either Even broke while Odd worked, or Even worked while Odd broke. So at least there is some sort of pattern there, even if it seems to vary between two versions of the pattern.

Observation for book & quill
Using a censored word seems to trigger this issue.
Two things seem to occur:
-The affected page will no longer be able to use line breaks.
-Writing on another page will cause the affected page to go blank.
Deleting the affected page will allow the book to maintain its structure.

Same, Bedrock on the Xbox. Seemed like it only did it sporadically for me before one of the more recent updates but now it happens on every sign.
[media][media][media]Thank you for your report!
We're tracking this issue in REALMS-5898, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki – 📖 FAQs