Euwill Eusebio

Thanks GoldenHelmet! I'll add it to the bug report.
And can someone remove the creeper jpg? Someone put it there randomly and it's not at all related to the ticket.

I believe I know the cause. Chests do not render off-screen or after a certain distance to save memory. This is why whenever players look away from a chest, the light it is blocking goes through it as the chest un-renders.

Affects 1.17.0.52

Affects 1.17.0.52 beta

Affects 1.17.0.52 beta

It just happened to me again today. I thought maybe that it would be tied to skins resetting whenever players update the game. But now I can confirm that this isn't the cause. Yesterday I was in the most recent update (1.16.220) on my Win 10, and the latest beta (1.16.230.54) on my phone. Everything was perfectly fine, and my 3 skins were there. And then today when I went back to play on my PC, all of my skins have been reset. Both in the beta and in the full release versions. I tried signing out and back in on both devices with no success. I haven't recently updated my PC and phone for about a month. I'm convinced at this point that this issue is happening on Mojang's side. And their servers just not saving your skin.

This is already a known issue at MCPE-121718. Please search for your bug before creating a report to make sure your issue hasn't already been reported.

Can confirm that this still affects beta 1.16.220.50

Can confirm that this issue does affect beta 1.16.220.50. Here are some screenshots of several parts of the Ocean Monument. I've stood on top of the Monument for 30 minutes to make sure I gave enough time for Guardians to spawn. At times there would be a handful of 4-6 guardians, but they would be mostly at the back of the Ocean Monument or spread out attacking Squids. But in this instance, I found only four Guardians around the Ocean Monument which is very unusual and too easy for players who may try to raid an Ocean Monument. The three Elder Guardians are in the Monument but otherwise, the structure is completely devoid of any mobs whatsoever.

Can confirm that this issue still affects the latest beta.

Steps to Reproduce:
1. Create a new world (Recommended to use Creative Mode w/ Cheats enabled)
2. Locate an Ocean Monument
3. Find an Elder Guardian
4. Enter the Pause menu < Game < Difficulty < Peaceful

Observed Results:
The Elder Guardian disappears
Expected Results:
The Elder Guardian remains.

This is working as intended.

You will have to restart the game by closing it after your Anti-Aliasing has been set to 2 or above. After restarting, even if you switch it back to 1, your game will not crash when looking at the achievement screen. Only until after you restart the game after you've changed Anti-Aliasing back to 1, will the crashing occur again.

I can verify this as well on Windows 10. And Mateo's method works. Apparently, if Anti-Aliasing is set to 1, your game will crash upon pressing the achievement button. After it crashes, this screen may occur.

Hey there! Sorry, but this isn't a bug. Currently, there is no Spectator mode in Minecraft (Bedrock codebase). It is currently only available in Minecraft: Java Edition.

Hopefully now with these videos comparing how long vexes should take to be summoned, you may know that this is definitely a bug. Don't rely on the Wiki, information from there isn't always accurate. Also, I will remove the world that previously was there for downloading since it no longer works.

Hey Eric! I noticed you said that Evokers summoning vexes have a 5-second cast time. It has been a while since I last updated this ticket so I went back into testing today to time it. My results In Minecraft: Java edition the Evoker took almost 2 seconds to summon its vexes. And in Minecraft (Bedrock codebase) it took 6.35 seconds to summon vexes; pretty much matching what was in my video.

No worries if your world got corrupted. Minecraft Bedrock has a special system built in that slowly fixes corrupted worlds every time it's been opened. Eventually, the game will revert back so many times that your world will be fixed. So, in theory, keep opening your world until it opens. I got this tip from Helen Angel.

That's great! Have you found a way to reproduce this issue? Otherwise, it will be hard for the developers to fix it as well.

Hello Adam! Is your villager a nitwit? It has a green robe on with no badges on its hip. If so then those types of villagers specifically will never get a job. Can you send a picture or screenshot of the affected villager?

I also experienced this issue but upon signing out and signing back in again it fixed its self and nothing was lost.