Hacker1MC

Frederick Dalcourt Chassé, I downloaded your world and was able to use it, so this should be good as long as it exhibits what the developers are looking for. For proof, it has a 3,000 block long dirt highway, and a gold farm on top of a crop farm, at ~1322 days played.

I agree that a newly created world will exhibit this problem. You might want to create a new world on a separate device to skip the process of exporting from console/realms. Join it from your console from both splitscreen and non-splitscreen to ensure both “player B” inventories are created, and maybe put something different in each inventory to make them identifiable. You could rename a paper in an anvil with “host”, “player A”, “player B solo”, “player B splitscreen” for the 4 inventories. This may require 3 accounts, to avoid using a guest account anywhere, while the download via realms option would only require 2.

Then, to be clear, the storage/deletion of the login info is not the issue. Your UUID (Unique User ID) is tied to your Microsoft account, so you can't get another one/different one. Despite this being kept on-device, Minecraft uses a different UUID, similar to when playing as guest on Xbox, when you use splitscreen. When you return to a different profile, your login info is still functional - it is only joining worlds while as the split screen player that yields the wrong UUID. (Also, I believe splitscreen is prevented entirely on featured servers.)

This is further evidence that this is not a realms issue. Nothing is being done to the world file when importing or downloading in this case; the problem lies entirely in the fact that, for the last 7 months, playing in splitscreen is effectively the same as using an entirely different account. You would not notice this on local worlds created since June, because you would be consistently using the splitscreen inventory for it. But you can confirm this by joining your world from a separate device under the account that normally plays splitscreen. You will find that the separate device will use the same player data as on splitscreen from May or earlier, or potentially when that account was logged in solo on the realm, but it will be a separate player data from the splitscreen you've been using for the last 7 months. Without a warning, fixing this bug would catch users off guard, as the splitscreen data in all of their recent worlds would be replaced by the “correct” data for their account - unused player data of an empty inventory at spawn. This is how the bug was fixed both times on Xbox- if you had a splitscreen inventory while the bug was active, it was made inaccessible upon fix. This is why I urge everyone to not leave any items at all in your inventory when logging off, nor get attached to new pets tied to your splitscreen account. If possible, leave everything in a chest when logging off as a splitscreen player every time.

In an ideal world, Mojang could provide low-level tools to view and edit players' inventories directly in the file, so that both inventories could be recovered after this fix would be made. Even better would be to also manually re-assign all pets of one ID to another ID. Additionally, if implemented on Xbox, this could help me recover about 10-20 guest inventories in my world from the past 6 years, when I used to play with my siblings logging in as guest(1) intentionally. This solution would be the only change that isn't devastating to unsuspecting players with worlds from the last seven months, but I imagine it would be incredibly hard to implement, and nearly impossible to implement well.

For the time being, just leave your items in a chest when you log off from split screen so those items will not be taken away forever.

@Steve Blackman have you experienced this bug since updating to 1.21.132? I am curious if this hotfix, which works for Xbox players, is functional on PlayStation or Switch as well.

This delay is the reason I stopped using Happy Ghasts soon after their release. Not only is there a delay, but the player and their camera position is moved on this delay. If you look to the left at a block to mine/interact, your ghast will afterward suddenly align itself left, moving your player, overshooting the block you already chose to look at. This creates a constant conflict of failing to estimate how far the ghast will turn every time you try to use the happy ghast for building.

I don't think this issue is confined to realms, btw. On Xbox it is not confined to realms. You can join from a mobile device to any Bedrock world to confirm the account data is not the same as what you will find with splitscreen. When joining from split screen, you are simply bound to get the wrong player data.

Original reporter here. Xbox Series X, in a regular world.This bug is back. The secondary player joins under their correct username, but not with the correct player ID or data. They appear at world spawn, empty inventory, and notably they are a new player ID, as opposed to a repeat of the ID created in June 2025. This is a large issue, and extremely disheartening as the holidays have just begun.

Note to everyone newly discovering this bug, you can recover items by joining from a separate device and placing them in a chest. However, if you do continue to play on split screen while this bug is active, leave your items and armor in a chest every time you log out!! Otherwise your items will be erased when this bug is fixed for you! Also, don't use Ender chests, because they are tied to player id.

This bug affects the character creator item, in Outerwear, “Muddy Mud”. This item is not available on the Marketplace, and was obtained via a Minecraft Earth challenge.

“We are using this bug to track reports of losing progress when playing on a Realm in split-screen, which is affecting some players”

This is only an accurate description of the current persisting version of the issue if you consider the full report itself. In this context, “losing progress” is shorthand for receiving the wrong account when joining a world or realm via splitscreen. My heart goes out to all of you on PlayStation on Realms who have now waited nearly 6 full months for this to be resolved.

On the more recent progress console, make a copy of the world. This world should probably be able to sync. If it still won't, you need to delete the original world file. Then open up the copy of the world and close it, hopefully it syncs. NEVER delete it without ensuring the copied world works correctly first.

also, download Minecraft Preview for free. In the settings → world storage → import worlds from release version, you can find which worlds (and what dates on the file) are really being stored on cloud.

As of 1.21.90+, whenever a beacon beam changes color, it recalculates the color and changes it again after around one second. On single player, this presents itself as a very light color then the darker, more saturated, normal version.

On realms, this presents itself as two distinct colors showing from different timings, which means rendering the beacon color more often is absolutely possible.

I hope the team is still aware of this issue and how it presents a major limitation keeping beacons from their full potential.

Still affects 1.21.94, Xbox Series X and iOS.

MCPE-222048.

This bug has returned, exists in 1.21.93

This also affects wax level of chests, causing them to revert to unwaxed variants when they are not both waxed. This happens regardless of whether the waxed chest is the more or less oxidized of the two chests.

This seems to be intentional game design (from my single perspective). If you want them to return non-sorted items, place a chest that has a hopper below it. As long as a chest is empty, the golems will place the items in that chest. The only problem is that they will do this even if a nearby chest has a match (they place items in the first chest they can). Solution: place the “returned items chest” with hopper as far from the copper chest as possible.

Thank you for this report and workaround, it allowed me to share my feedback on the copper golem. I unfortunately still cannot comment though, as my test box always says “0/1500 characters”

Turn on the experimental toggle on world creation. They are there