Erik Harding

I'm not near my Xbox to grab a screenshot, but I did see this issue again with the 1.20 update. It seems to only occur during an update, and it seemed to be the developed/modified areas of our overworld showing up at the same coordinates as if they were in the End. I'm assuming if we flew to those locations in the End the map would show the proper End locations again.

It is harder to notice, but I believe it is also happening in the Nether. I noticed some portions of a bridge I was building were inexplicably brighter. The bridge was over a lava sea, but only small areas were affected.

I have this issue on my Realm as well. 

The highest light level is on chunk borders (coords divisible by 16) and it happens both above and below ground. It happens below Y-0. I haven't been able to confirm if the same light level is constant in a X,Z coordinate. 

I play with a  Xbox Wireless Controller – Grey/Green - Microsoft connected via bluetooth to a Surface Book 2. The issue is very erratic for me - sometimes I can play for hours without problem, sometimes it will happen multiple times within 15 minutes. 

I really wish I had solid reproduction steps for you, but I have not seen any pattern yet.

Edit to give an update on the randomness of it all - after playing for a couple of weeks without issue I've just had 3 controller freezes in an hour. As has been noted before, the computer still recognizes the controller but Minecraft no longer does. Closing and reopening Minecraft fixes the issue.

I know that I traveled from the the south part of the patch to the north, it was very laggy amdI traveled south again. I was holding the overworld map in my offhand, both maps were in item frames in the south location. I never traveled to the End side, but FoskcoA4 did (with the End map) and it was very laggy when he mapped over the affected area. I have yet to be able to reproduce it. 

Just to clarify, FoskcoA4 is the owner of the world in the original report.

Adding, the "overworld" part of the map can be overwritten by visiting that portion of the End but the game became very laggy.

It also persisted when the world was uploaded to a Realm.

I just had it happen in 1.19.22

I was playing on a private server, and as before once the controller input stopped being accepted I had to close the game and relaunch it before the controller was recognized. 

I had a suit of unbreaking 3 netherite armor go from full durability to destroyed during 1 wither fight. 

This still happens frequently in 1.19!

I can play for hours without it happening, and then it just happened twice within 5 minutes.

The controller is still recognized outside of Minecraft, and after closing and relaunching Minecraft it is recognized without any further steps (resetting the controller, ect)

I can also confirm this is happening, but I don't need to do anything (checking other screens) for it to occur. It seems to have become more frequent recently, I can have it happen a couple of times an hour. 

Like James said, the only fix is to quit the game and relaunch it.

I'm sorry I missed commenting on the previous reply. This is still an issue in 1.18.2

I had over 20 tropical fish disappear in a short period of time on a bedrock Realm. They do not cross chunk borders, but they do move vertically between y63 and y68. 

Wet sponges in the desert/savanna will dry out , it just takes a little bit.

Also worth noting this "instant drying in running water" effect will eventually burn out, similar to a redstone torch. 

It looks like this bug is user error - I found a harvester I had missed that did still have shears.

I had the same issue on Windows 10.

This is fixed as on seed -475302933 as of update 1.17.0.56 today

I would go further to say it is inconsistent. I have had some signs that have nice clear colors (like when using the § codes) and some that are barely visible - on the same type of sign, facing the same direction, in the same room with the same lighting.

I found similar, smaller pieces

Thank you, I thought I had turned EX on but I had missed it.

Issue resolved, the bug was me 😛