J. Metcalfe

No.  I cannot add a video since I didn't take a capture while it was happening (something I just don't tend to do while playing any game) and I haven't played Minecraft much at all since then (having moved onto other games for now).  I did try to be very detailed in making this report so that others might be able to verify the issue.  However, if I get back to playing Minecraft, if it happens again, and if I remember to take a capture, I'll add it to this report.  Thank you for your response.

Mining fatigue on the Xbox (using a controller and the right trigger) also is affecting blocks that should be mined instantly.  Since holding in the right trigger is the only way one can mine anything on the Xbox, the references to it only happening when holding down left-click are meaningless.  It happens 100% of the time on the Xbox.  Tapping the right trigger makes no difference since the block does not break instantly.

From the picture, I would say that villager is linking to a different bed that is not in the picture and that he cannot reach.  While some people say they will eventually sort it out to release their link from beds they can't reach and claim beds near them, my villagers never seem to get around to it and just stay up all night reclaiming the same bed that they can't reach (green stars followed a few seconds later by the yellow clouds).  That is, I found he will not link to another bed (even though he is standing right beside one) until the bed he is already linked to is found and removed.  The problem may also be complicated if other villagers (outside the picture) have claimed the beds in the picture for themselves even though they cannot reach them.  When you get a "match" (i.e. a villager linking to the bed right beside him), you should see the green starts emitting from both the villager and the bed at the same time. 

I doubt it is lag since, in example 4, my nether tunnel is completely enclosed, carpeted and 100% free of any sort of mob.  The walls have no indentations and are, so far, only adorned with torches.  There is one door about halfway down that corridor,b ut it is mounted flush with the inside of the tunnel.  There is no way, in that space, I should have taken any damage regardless of lag - unless the lag itself causes the player to be able to generate damage by running.

However, yesterday I played almost all day and never took any random damage or damage that I could not readily explain.  So, perhaps it is related somehow to my internet connection.  The only other possible difference is that yesterday I was not playing on peaceful mode.

May be related to MCPE-172862 (reported issue with editing text on command blocks, in chat, and naming in anvils).  I suspect it extends to all areas where one uses the onscreen keyboard with a controller.

When I last commented on this, I failed to note that I had tried just quitting and reloading... and it didn't work.  I was also experiencing the bug every time I loaded a world after freshly launching the game.

Something has changed today though in that I've launched the game (after fully quitting it) and loaded worlds 4 times today with no problems.  Hopefully the issue won't recur, but I'm still making my backup copies just in case, because it never hurts to have a backup anyways.

@James - No doubt the reason the workaround is not working for you is because you're trying to fix a file save in which the bug has already occurred.  The workaround is geared towards preventing the bug from ruining a save file that has not yet been opened by making a copy of it before it is opened... then, if the bug does occur, you would still have a "good" copy of that file save so that you could try again with another copy of that copy.  You can then still play the game once you get a good loading of your save.  When you exit the save, you can still allow it to save your progress... but then make another backup copy of it... so that if the bug occurs the next time you start your game, you have your good backup to make a copy from and try to load the save again.

The bug seems to only occur when you first launch the game and, for me at least, it occurs on the first file save I open whenever I first launch the game 100% of the time.  On the second and subsequent file saves I open as long as I haven't quit the game itself, the bug does not occur.

I do agree... I hope they can fix this bug as soon as possible.  Isolating it to the first saved open after launching the game, I hope, helps them track it down quicker.

I ran another test on another different world save... I quit the game entirely from the Xbox Home Page (without shutting down the Xbox itself), waited a minute, and then launched the game anew.  I chose a world save to load and spawned in at the original world spawn with my inventory and levels completely wiped.  (So, this bug is 100% occurring when the game is first launched).  I used the "Save & Quit" option, then deleted that save from the main screen using the "edit" screen.  I then scrolled down to my backup "copy of" save I had made on a previous session and used the "edit" screen to make a "copy of copy of" save.  I then loaded that save and it loaded correctly (So, this is currently a reliable workaround... as long as one has backup copies made from before the bug occurs.

To other players:  IF you have not made a copy of your world from a previous play session, I suggest you go directly to the "edit" screen before trying to open any save and make a copy at that time to avoid having the save file ruined by this bug by opening it whenever the game is first launched.  That way, if it does occur, you'll have a good backup save to copy from and try again.

This is a serious bug and, hopefully, there will be a fix soon.

It should also add, all 3 save files that were affected over the last two days were single-player saves.

This has happened to me for the first time yesterday... and then again today... on two different saved worlds.  In both cases, my inventories were completely wiped, my levels were wiped, and I spawned back at the original world spawn despite having my bed at a different place and having used those beds for months and months as I built up a home base away from spawn.

Fortunately, I have long made a habit of creating a separate backup copy of my world saves each time I end a play session (from the edit screen).  This meant I had a copy from my previous play session before the bug occurred, so I was able to create another copy from the unloaded backup, then load that... and it loaded correctly.  So far, this issue is only occurring when I first start the game, not when I load a new save from within the already started game.  My platform is Xbox X, v1.19.63.

My issue was "resolved" and linked here - however, my issue is that I cannot delete the individual worlds that have failed to sync properly from my Xbox itself since there is no way to access the "edit save" screen from the message box that appears whenever this happens.  If I try deleting the save data from my console, the corrupted save is automatically downloaded from the cloud the very next time I reopen the game... EVEN after I have uninstalled the entire game.

My request was for a "delete save" option to be added to the message box so that these corrupted saves can at least be deleted from the console AND the cloud updated to remove them from there as well WITHOUT have to delete every Minecraft save from Everywhere (which is an option, but too drastic an option since I obviously do not want to lose any other worlds that are not corrupted).  The current situation just adds insult to injury - having lost one world to corruption and then having to lose every other world to this lack of the "delete this individual corrupted save" option.

PS:  Yes, I am very angry about this this at the moment.  Corruption happens... I can accept that... but THIS lack of an appropriate delete option is simply ridiculous... that it has, apparently, gone on for years now, makes it even more ridiculous.

I am playing on an Xbox One and have recently upgraded a world originally generated in 1.17.  I was originally delighted to find the area below Y0 just below my main base (which is in a plains biome) spawned with several smaller caves that have all the traits of being a lush cave with several clay water pools, glowberries, drip leafs, moss blocks, and moss carpet blocks.  However, no tropical fish or axolotls have spawned either in the natural pools or other pools that I have made in these caves.  I have had a glow squid spawn on a copy of the world that I put into creative, but none have spawned in the survival copy as yet after several day/night cycles working within an appropriate spawn distance.  This certainly sounds like this reported issue could be the problem in my world as well.  (NOTE:  I have managed to both spawn and breed several axolotls in my 1.18-created world in similarly constructed water pools that I have made within a lush cave there; so this issue does appear to be related to the upgrading of a 1.17 world to 1.18.)

ETA:  I have played several more Minecraft days near the above-mentioned water pools in Survival mode.  Several glow squid have now spawned now that I have much of the area sufficiently lit to suppress spawns of creepers, skeletons, etc.  Still no tropical fish or axolotls despite the terrain below Y0 clearly showing that the biome should be a rather large lush cave one (lots of clay, moss, glowberries, drip leaf, and spore blossoms having been generated in several small to medium-size caves when the world was updated from 1.17 to 1.18).  The only thing different from a 1.18 luch cave is is that there is not a huge cave in the area - possibly because the terrain above Y0 was already formed in 1.17.

ETA2:  I have also just now recreated my seed in 1.18 (in creative mode) and confirmed that the area is also a lush cave biome that extends both above and below Y0.  I see no reason why tropical fish and axolotls are not spawning in my upgraded 1.17 world.

ETA3:  This particular file save has since become corrupted and is unplayable (i.e. will not load and will not even allow me to delete it from the console).,