So I was building some cool looking redstone contraption, when suddenly someone texted me and I accidentally clicked on the notification. I went back to Minecraft, but the textures for all blocks were mixed up. I wasn't playing with any resource packs or mods, just Vanilla 1.18 Minecraft.
Β
Here a video: https://drive.google.com/file/d/1e24nJYVdW6U_fjwEogB_qGZ4AzDNjFqj/view?usp=drivesdk
Linked issues
is duplicated by 60
Attachments
Comments 10
Can i fix your video please you can just put the video like these photos and the like not working and i canβt see your video
affected me in 1.20.12 too, hereβs my video version. ios 16.5.1, iphone 13. i had also switched out to answer a text message and switched back in, and i had this exact same problem.
Actually if you're using an old shader, the same thing happens, maybe this happen because the rendering engine is outdated causing this error.
You can implement this bug by running the game in background and play in on screen
The fact that in 1.20.70 this still happens, and it includes Blocks that donβt exist anymore like The Nether Reactor
But still.
My textures werenβt as broken as the other ones
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Does the issue occur all the time or only occasionally?
Does the issue occur in a world without any texture or resource packs?
Does the issue occurs on the newest version?
This ticket will automatically reopen when you reply.
This still occurs in the latest version. According to MCPE-223406 , the issue occurs rarely. According to BDS-22761 , no resource packs are being used.
Hi) Is this still an issue in version 26.32 and later?
This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
π Bug Tracker Guidelines β π¬ Community Support β π§ Mojang Support (Technical Issues) β π§ Microsoft Support (Account Issues)
π Project Summary β βοΈ Feedback and Suggestions β π Game Wiki
This glitch still hasnt been fixed for like a decade. Still affects 1.19.63.