Michael P Touloumtzis

Looking at these reports (including mine), they suggest that Minecraft makes an assumption ("storage is full") from a LevelDB error code which can also arise from other causes. Most operating systems & platforms don't separately report the "storage full" case–they'll surface it as an I/O error. LevelDB doesn't know about storage media and returns a generic I/O error (leveldb::Status of kIoError) for storage-media full but also for any other kind of I/O error. Minecraft might even be interpreting non-I/O errors such as leveldb::Status kCorruption as "out of storage space".

I just encountered this on Windows 11, Minecraft 1.21.22. The world is 348 MB. I have plenty of free space on my C: drive (458 GB free). When I try to enter the world, it says "You are out of data storage space and Minecraft is unable to save your progress! Minecraft will return you to the main menu to clear up storage space." and returns me to the menu.

Additional info: the world is a Realm of which I wasn't the owner. The Realm owner exported the world and gave me the file; I imported it to play locally.

Attached world ("MCPE-29548") with a copper bulb repro case. Observer watches redstone dust (toggled by lever) and powers bulb. The mechanism does not cross a chunk border.

Expected behavior: redstone dust and observer bulb stay in sync (both active or neither active) including across world save/load.

Observed behavior: powering dust then relogging results in out-of-sync state (dust powered, bulb off).

The addition of copper bulbs has really exacerbated this issue. I've made a few designs now with observers toggling copper bulbs, and they work fine when the world stays loaded but (sometimes, unpredictably, in some chunks but not others) lose their minds on save/restore since the bulb state gets toggled when nothing happened. At first I thought it was an issue with save/restore of copper bulbs themselves, but I eventually traced it to this long-standing observer bug.

Confirmed in a 1.20.31 Realm. The easternmost End gateway portal on the main island teleports me to a few blocks away from the central portal to the overworld. This gateway portal used to work (it took us to the outer End) when we initially defeated the dragon a few years ago. Two additional gateway portals on the north side of the main island still work, but their destinations in the outer End are further west than they originally were.

A bit of science: wool carpets make no difference--the frogs still won't eat magma cubes. Each time the world is loaded, the frogs on honey blocks have a brief period (a couple seconds?) of normal behavior in which they'll be able to eat magma cubes; they then stop.

Confirmed in 1.19.62. This is a parity issue as honey block floors are used in some Java froglight farm designs.

Also noting that although the issue title says "as mapped" (i.e. default controller settings), it's not possible to map the Pro Controller triggers (ZL/ZR) in Controller Settings since Button_L2/Button_R2 (Android KEYCODE_BUTTON_L2/KEYCODE_BUTTON_R2) don't appear to be recognized or bindable in Minecraft.

I suspect the issue with ZL and ZR (which I'm also experiencing in 1.18.2 on Android) is caused by the fact that the triggers on the Switch Pro Controller are digital, whereas the XBox controller and most similar controllers have analog triggers.