mojira.dev
REALMS-10537

Named items and signs get changed into #'s

Today out of the blue, any items I rename have all characters replaced with #'s. I can replicate this with any item.  This item has been renamed "Cast's Sword" "Sword" "Help" "Stop" random characters, no matter what the end result is always replaced with #'s for every character including spaces.

Linked issues

BDS-17352 Maps and Signs naming issue Resolved BDS-17410 Pickaxe becomes ####### Resolved BDS-18787 Sign Censored Resolved MCL-22067 anvil bug, nametags are all in hashtag Resolved MCPE-159585 Incorrectly censoring Resolved

Attachments

Comments 41

[^2023-08-07_15.05.00[01].jpeg]

[media][media][media][media][media][media][media][media][media][media][media]

They closed my ticket in favor of this one stating duplicate when this isn't strictly my only issue. Its ANY form of text entered. I can not enter it in chat normally, as nothing pops up for other users. If I input the command way with "/say <text here>" it also changes all text to #'s. 

 

i have the same problem but i said words such as hitler and after that i couldn't rename anything

Im not even renaming items when putting them through the anvil and it’s still getting censored.

I have the same issue… mine was resolved and linked to this, as well, but I can’t write on ANYTHING either. No signs, no name tags, no chat…. this started right after I made a handful of pride flags with no issue, now I can’t type anything at all.

UPDATE: Mine fixed itself! I waited a day or so without playing much, woke up this morning and could do everything again! Don’t know if it’ll fix every time, but there’s one possibility; just wait it out and see what happens.

31 more comments

Confirmed on Realms for 1.20.80

Confirmed on Realms for 1.21.0

Confirmed still happening in Realms on 1.21.2 

It's particularly bad when trying to form large letter signs with Unicode block characters, such as █. Works perfectly normal in a singleplayer world.

Singleplayer sign:

[media]

Same sign in a Realm: 

[media]

Confirmed in version 1.21.31 on Realms.  

I was able to write:

Luck o the Sea 3
Lure 2

When I went to put an "x" in front of Lure 2 it then showed as the hashes. 

This is consistent for the following:

  • Destroying and putting up a the same sign. 

  • Destroying and putting up a new sign. 

  • After saving and re-loading the realm.

It does not happen for just "xLure 2" or for "Luck o the" as the first line.  It also doesn't happen if I use "1Lure 2" instead of "xLure 2"

Step 1:

[media]

Step 2:

[media]

 

Step 3:

[media]

 

If I use "x1234 5" instead of "xLure 2" I get this instead:

[media]

Confirmed in 1.21.50 via duplication of @ShadeTC's method (Just trying for consistency in reported occurrences)

Don't know why this was marked as resolved, unless it has to do with the transfer to the new bug reporting site

migrated

(Unassigned)

Community Consensus

Bedrock

Retrieved