As of 26.2 snapshot 7, falling block entities which represent signs are now correctly visible in their entity state. However, if that sign has associated text data, that will still be invisible until the sign makes contact with the ground and becomes a block.
Example test command:
/summon minecraft:falling_block ~ ~5 ~5 {BlockState:{Name:"minecraft:oak_sign"},Time:1,TileEntityData:{front_text:{messages:['I\'m','a','falling','sign!']}}}
Expected results: text would be visible when the sign is in a falling state
Actual results: the text is invisible in this state; when it touches the ground you can verify the entity did indeed have text data, but it wasn't visible then
Attachments
Comments 3
Thank you for your report!
After consideration, the issue is being closed as Invalid.
You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit The official Minecraft feedback site or visit the Minecraft Feedback Discord server.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
How, exactly, does this count as a feature request? The sign itself being invisible in a falling state, as far as I know, was always considered an issue. The text being invisible is the only remaining element that doesn’t work ever since the main body of the sign was converted to the proper model system. As far as I can see, text not being visible yet being defined in the entity’s data defies the expected outcome.
Thank you for helping us improve Minecraft! We saved your files: