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.
Related issues
is duplicated by
relates to
Attachments
Comments


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.

I had a similar issue, but I didn't even rename my tools. I had my enchanted bow, pickaxe, and axe in my echest and when I logged on they were changed to ########### and ####. I can still write on signs and stuff unlike these other comments, but it is very odd to say the least.

I havent tried writing on signs or in chat (I play on a personal realm with my boyfriend so we play together in person as we live together), but this started for me just from me combining books at an anvil and then later applying books to my tools at an anvil. It is also happening to him for the same things - basically any item that gets fed through an anvil gets all characters replaced with '#' signs

I have the same issue. I tried renaming my tools and all I got was a row of #. Then tried combining tools with books without renaming them, same result. All my previously renamed tools kept their names though.
I also tried writing on signs and it just keeps switching to blank.
I'm playing on Realms on Nintendo Switch.

Playing in my friend's realm, we JUST killed the ender dragon, I was making shulker boxes for everyone and trying to name them with our gamertags, Barny, Hunney, and Green - all of it is being censored as well as everything I type, no matter what.

it happened to my realms now. everyone els is aloud to type in my realm instead of me (the owner)

I am having this same issue on the realm I own. All items I tried naming turned to "#######" etc. Signs I place turn blank as soon as I place them, and books become blank after I write in them, even after signing them. Other people on this realm are having the same issue.

I'm having the same issue as well. Signs turn blank and command blocks also turn blank after I enter the text. It happens on almost all the devices I tried: PC, android, PS5 and PS4, and IPad.
Here are some clips I recorded:
https://youtu.be/Yi4R-nnLdYs
https://youtu.be/nwF6P4T5UCM

This affects map names when duplicating them on a cartography table as well.

I suddenly have the same issue. Whenever I name signs, the text disappears whatever info I enter.
A similar issue happens with naming items or maps. Those change to ############
Please help.
Update: It seems to only happen to me as the Realm Owner. Not with other players in the realm. So far I tested this on PC and Android with Minecraft version 1.19.11. Both show the same issues.

Same issue on my realms server in windows 10 edition. I received a notification that I had been temporarily muted right before this error occurred. I had not typed anything remotely offensive, but I did include hashtags (#) on my signs (as in "clue #3" - I was setting up a scavenger hunt for a friend). Please let me know how to resolve this issue! thank you.

I have the same issue in lastest win10 edition,while the bug don't work in Nintendo Switch edition.

For me on my Minecraft realm on Xbox Series S even putting enchantment books on weapons/tools changes it into hashtags (#) anything to do with naming anything.

I'm experiencing the same thing, but before this happened it said, "You've been temporarily muted in chat. Remember to follow the Minecraft Community Standards." for no apparent reason.

same issue with me, happened to my boyfriend a day before it happened to me and my little brother is having the same problem. It's fine if we can't use the chat because we all can talk on discord but I would really like to name some of my items

It's happened to me when I put an enchantment on my shield. I didn't even rename it.

The best "work around" I have found is to leave the naming line empty. This will name the item the default name (ie diamond pickaxe with no data in the line will still be called diamond pickaxe). This doesn't allow for special names though.

Same. It’s happened before, then was fixed, but the bug is back, it seems. On console for me.

Had this happen while trying to name a fishing rod, even tried to name it again and it is stuck with ########### as the name. This is happening along with not being able to put text on a sign, so it seems the two issues may be related.
Update: This is happening with items, sign text, and not being able to use chat. All 3 are happening at once and all 3 seem to be related to this same bug.

so this bug is happening on my realm where if I try to write on a sign as soon as I am done it completely erases everything. also when I put anything in an anvil or name tag it replaced the name with ##### even if I did not choose a name. for example if I put a pair of “netherite boots” in an anvil to add an enchantment and do not try to change the name from the original, it still changes the name to ########

I am a realm owner and 2 players on my realm are unable to name any items, or signs. They are able to type in chat. One is on switch the other on PC. This has been going on at least 2 weeks now. They are able to clear when naming items and get the default but they are unable to create custom names or create signs, they just get the #####s.

The issue seems to be resolved after I did a clean Windows install. I can write signs again and rename items.

It's finally fixed. Thanks!

I had this issue appear while renaming a Structure Block that I had saved a structure to.
In my case, the entire custom name was replaced with a line of 17 hashtags. Oddly, these hashtags weren't in italic.
A few days later, I decided to try the renaming again and this time it worked without any issues.
Sometimes waiting a few days and then retrying with a different anvil will fix this issue.

Still an issue in 1.20
Tried to type "Flasher" and got a bunch of # symbols. Editing the sign after placing it doesn't fix the issue and the newly added hanging signs are also affected.
[media]
Still happening in 1.20.12 although the chances of it happening are very hit or miss.
Sometimes you can go for hours typing and placing signs without an issue then all of a sudden you'll get a sign with the 22 #'s and a dash.
I've also noticed that whenever this glitch occurs with a sign, it deletes the line breaks just before the #'s appear.
One thing to note is that the NBT Data of the sign is still saved to the world file.
I found out by doing Ctrl + Pick Block on a glitched sign and then placing it. The #'s show instantly when placing glitched signs like this since there's no pre existing text to glitch out.
[media]
I can't even write something simple like "see 455,-10,-215" onto a sign. It turns into "########...".
I did not chat or say or write anything before in this realm, but that sign got censored.
When I pay money on a monthly basis for a server, I expect to be able to write coordinates onto signs.
If there are censorship rules, please make them transparent and clear. A position coordinate is not profanity or anything that deserves censoring.
All this combined with the limited simulation distance of 4 make realms really really expensive for what you get.

Confirmed for Realms 1.20.12
Slavic names written in Cyrillic almost 100% cause this issue. After writing in sign, if sign does not glitch out immediately, I have not seen any glitch at a later time so issue seems to occur during the moment that the sign loads after editing.

Still happening in 1.20.41 however it's less frequent and I've only seen it once while renaming a Structure Block with an Anvil.
24 hashes in their full glitchy glory
[media]
Still happens occasionally in 1.20.50

Still Occurs in Realms 1.20.60, It seems that It will go a long while without occurring then once it starts (I often am editing many signs in a batch for storage chests or markets) it continues to do it.
I really cant see any pattern as one sign will be okay but another sign with the same text or same text with one word added will cause the #### to appear

Still happens in 1.20.71
How hard is it to fix this? They should get the person who fixed REALMS-9191 onto this issue.

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
[^2023-08-07_15.05.00[01].jpeg]
[media][media][media][media][media][media][media][media][media][media][media]