Auldrick

This MIGHT no longer be an issue. In 1.21.101 the worlds show up as “Friend’s world”, which suggests that the explanation I speculated about at the end of my last comment might have been correct and has, perhaps, been fixed. However, I also traded up to a new PC since that comment so Minecraft has now been reinstalled on a PC it had never been installed on before, and that may have circumvented the problem, in which case the problem probably still exists. Since I can’t reproduce it any more, it’s up to somebody else watching this bug report to weigh in.

This is still happening in 1.21.94. On my PC, the other player’s world appears in my Worlds list as a “LAN world” for a few seconds, then disappears. This only happens once per launch of Minecraft. If I exit and relaunch, it happens again. This is repeatable.

I recently joined PC Game Pass, but it still behaves the same way. The other PC on my LAN is not on Game Pass.

On my Android phone, the other world initially appears twice, both as a “LAN world” and a “Friend’s world”. Then after about 2-3 seconds the LAN world disappears but the Friend’s world persists. As on the PC, the LAN world doesn't reappear unless I relaunch Minecraft.

Speculation: As an experiment, we turned off “Visible to LAN players” for the world. It still showed up on my phone as a “Friend’s world”, so maybe what’s really happening is this: Minecraft checks for both LAN worlds and friends' worlds, but if a friend is playing on the same LAN, their world would be listed twice, which might be confusing, so the game suppresses the LAN world in this case. The bug would be that in this case, the Windows edition suppresses the LAN world but also fails to list the friend’s world. So the problem isn’t detecting LAN worlds, it’s listing Friend’s worlds. (Remember, I can still join the unlisted world by clicking Join in the Friends drawer, I just can’t see the name of the world that way.)

I’m having what I think may be the same problem, but:

• The PCs on my LAN connect via Ethernet, not Wi-Fi (I don’t think the physical layer matters for this problem).

• When I open a multiplayer world, the other PC sees it. When they open one, I can see it for about 1–2 seconds, but then it disappears.

• Even though I can’t see their world, I can join it via the Friends drawer.

Both worlds have “Visible to LAN players” enabled and we’re both signed into Xbox Live.

I tried reinstalling Minecraft but it didn’t make any difference.

It occurs to me that the problem might have something to do with Xbox privacy settings, but it seems unlikely. Nevertheless, I'll investigate when I get a chance and update if it seems relevant.

Fixed in Beta/Preview 1.21.90.26. Expect it to be fixed in the Summer Drop.

The following additional Minecraft-branded skin packs have been found that also show only "1 skin" in the Marketplace details heading:

• Battle & Beasts Skin Pack (45 skins)

• Strangers - Biome Settlers 3 (25 skins)

• Magic: The Gathering Skin Pack (15 skins)

• Town Folk Skin Pack (20 skins)

• Campfire Tales Skin Pack (16 skins)

I can confirm that this happens with classic skins. Not sure if it also happens with Character Creator characters.

This issue has been resolved as Won't Fix.

The Slate item was never intended to be available in the game when the Education Edition toggle is off. That it was present in creative inventory was a bug (see MCPE-187696), and it was fixed in 1.21.50.28 Preview/Beta.

"Fixing" this issue would involve either making the item (including its texture) available again, which is contrary to design, or deleting any instances of blocks and/or inventory items of that type, which is something Mojang never does (there's a policy against ever intentionally deleting something a player built). In contrast, making the item unavailable only causes its blocks to become inert and harmless, so it's safe to leave them or leave it to the player to get rid of them.

This issue has been resolved as Won't Fix.

The Slate item was never intended to be available in the game when the Education Edition toggle is off. That it was present in creative inventory was a bug (see MCPE-187696), and it was fixed in 1.21.50.28 Preview/Beta. Since the item is not part of the game (with the toggle off), its texture is absent from the game (with the toggle off), which is why it's shown as the "missing" texture.

"Fixing" this issue would involve either making the item (including its texture) available again, which is contrary to design, or deleting any instances of blocks and/or inventory items of that type, which is something Mojang never does (there's a policy against ever intentionally deleting something a player built). In contrast, making the item unavailable only causes its blocks to become inert and harmless, so it's safe to leave them or leave it to the player to get rid of them.

I have found that there is another bug report specifically about hitting storage limits on Switch when downloading from Marketplace or Realms. Recent commenters should check out MCPE-36670. It looks like that problem may be fixed in the next release (though it's possible the fix may only be to explain more clearly what happened).

@unknown: The bug tracker is for reporting bugs. We are not set up to provide support assistance and don't have expertise with your platform. You would likely find more help at outside community resources such as the Community Support Discord or at a Switch-specific Minecraft user group. I haven't checked, but Reddit might have one.

Although I don't really know, it does sound like you might have a free space problem. However, downloading add-ons from a Realm is a different process than downloading Marketplace content, so I doubt that your problem is a match for this bug report.

@unknown: The bug described in this report only affects the Minecraft-branded packs listed in the description. The Soundscape+ Add-On would not have the same kind of problem.

As a first guess, your problem looks to me like you might be low on storage. I can't tell what platform you're playing on so I might be totally wrong about that. But it wouldn't hurt to check Settings > Storage for any stuff you're not using right now and recovering some storage space that way. If that doesn't help, you might want to try asking for help at the Community Support Discord, and if that doesn't work, create a new bug report using the advice in our Mojang Bug Tracker Guidelines and FAQ. .

These items are exclusive to the Education Edition of the game used in schools. The "Education Edition" toggle in the Bedrock Edition settings does not include them by design. A behavior pack cannot change this.

Suggesting changes to the game's mechanics isn't forbidden. However, it's seldom helpful because we aren't Minecraft devs and don't know the details about how the engine works, or because we aren't CompSci experts and don't know how to think at the necessary level of detail. Brains are really good at solving problems like pathfinding, brainless computers not so much, and translating what the brain does into steps a computer can follow is hard, real hard. Especially if you have to simultaneously make it work well in a practically infinite variety of terrain and structure configurations, and do all this without degrading performance on the least powerful platform you mean to support.

Consider the suggestion made a short time ago to look for a door. It's too high-level and incomplete. It assumes (1) that the first door detected is reachable from where the villager is, and (2) that the target is reachable from that door. But it won't work if the door is behind a wall: The villager will just get stuck on that wall instead. Obviously, that means you should ignore doors that the villager can't reach directly, but that's the same problem as finding a path to a bed you can't reach directly. Although this suggestion makes perfectly good sense to and can easily be used by a brain, a computer has to have much more detailed instructions.

Finding a path from point A to point B is a classic problem in computer science. In theory, it's very simple to solve: You just have to test every possible path and pick the shortest one. But the brute force method explodes exponentially with each additional step required, so that approach isn't practical. So you have to find an alternate method, and it turns out those are always imperfect in one way or another, which is why the villager gets stuck now. What's needed is a different algorithm that works better in this situation and doesn't work worse in other common situations. But an algorithm like that is hard to find and verify, because Minecraft terrain/world generation is so extremely variable.

In summary, this is not so much a bug as it is a shortcoming of the pathfinding algorithm, and the reason it's taking so long to fix is that every conceivable alternative algorithm is going to have shortcomings of its own, most of them with much worse consequences on performance and/or naturalness of behavior. (Which is important: Villagers may seem not quite as smart as people, but at least they don't usually walk off a cliff or drown in a river.)

And then there are the dirt paths. It's easy to draw the wrong conclusion here because the game mechanics are obscure. Villagers don't avoid dirt paths per se; in fact, it's one of a number of blocks they prefer to walk on, all other things being equal. (This means that when a villager is already on a dirt path, they'll tend to follow it in preference to deviating onto grass etc., and sometimes you can make paths to nudge them toward places they need to go to.) I think the reason they avoid paths in cases like this is that dirt paths are shorter than full size blocks, so a villager calculating the best path sees dirt paths as a step downward from grass, dirt, stone, etc. And upward and downward steps (unless there's a stair) are discouraged by the algorithm, so villagers don't do silly things like trying to climb over blocks or dropping into one block holes that happen to be in their way when they could easily walk around them. The algorithm would probably work better if it only discouraged vertical steps of >1/8 block, but I dunno, maybe checking for that on every single pathfinding step would slow things down too much.

In summary, I think Mojang appreciates that we're trying to help, but without knowing the fine details of all the game mechanics, what we suggest is usually too high-level to implement directly, and besides that they've probably already thought of them and either found they won't work, are impractical because of hardware limitations, cause a different problem, or they're already working to implement them. Or, they've already got a fix but it's part of and dependent on an engineering change, some of which isn't ready for prime time yet. That's something that has happened many times. 

Edit: Please don't regard this as an invitation to discuss how to make suggestions better or how you think Mojang needs to change the bug fixing workflow. I posted this to help our Mojira customers understand why fixing bugs sometimes takes a very long time, despite the problem seeming to most people like it's not that difficult. But the bug tracker is not a chat board or other discussion forum; please use the Minecraft Discord for such things.

Please reserve comments for providing additional information that might help the devs find and solve the problem. The bug tracker staff normally has no information about when a bug will be fixed or why it's taking so long. We're just volunteers from the community.

Possible workaround:
Something you can do that might help your villagers find the door is to put up a fence or other barrier that prevents them from getting close to the wall near their bed (or workstation). The problem seems to be that they always look for the shortest path that brings them close to where they want to go but don't recognize the wall as a permanent obstruction. If you keep them farther back from the wall, or move their bed or workstation closer to the door, they'll be less likely to get stuck with the wall between them and it.

By the way, I have removed one of your comments. Please don't publish people's personal information on the bug tracker. It's prohibited.

That is correct, the only thing of yours that we could access was what you gave us a link to. But you said "move me back to the point of around September", which I took to mean you wanted someone to revert your live world inside the game, not the .mcworld file you linked. What I was saying is that nobody has access to that but you, because I thought you were offering to let us or Mojang edit your world.

• Neither we nor Mojang/Microsoft have access to your worlds in-game, either between gaming sessions or while you're actively playing.

• You gave us access to a backup of your world, but world files don't contain any chronology of what was done to them, so nobody can revert what happened to "move you back". Neither is there such a chronology anywhere else.

• In case you're wondering where I got the information about your cumulative time played, that and the other details are recorded in the world files along with your world settings. Mojang probably records it as information that might be useful for debugging. I used it to verify that the Backup save was actually older than the Primary save, because I wasn't completely certain which was which.

Lol, I must say you have a very relaxed attitude about letting strangers tinker with your personal files! You really should be more cautious—there are people on the internet who could do a lot of damage to you.

Which reminds me, it would be a good idea if you remove those sharing links:

1. Open File Explorer to the folder you copied your world backups to.

2. Right-click the first file and select OneDrive > Manage Access from the context menu.

3. At the top of the Manage Access dialog, click Links.

4. Next to the link, click the trash can icon (tooltip is "Remove link").

5. Repeat for the other link.

For clarity, the bug tracker staff are neither Mojang nor Microsoft employees, we're only players from the Minecraft community who volunteer. And neither Mojang nor Microsoft is keeping track of when you play Minecraft. There are probably logs of when you connect to Xbox Live, but for legal reasons they wouldn't identify you personally or record what you did while connected. Keeping information like that (at least without your explicit consent) is illegal in a large part of the world.

Since the spawn coordinates recorded in the save files are only about 10 blocks away from what you reported, it's not surprising that I saw the same things you saw: For the Backup world save I saw the pumpkins like in your "01 spawn point" image, and for the Primary world save I saw the mountain in your "primary save file mountain base" image.

Force quitting the game has a relatively higher likelihood of causing data loss or world corruption than just closing the window without saving. In future, if you have to force quit it would be a good idea to check for damage the next time you load it. By checking, I mean visit locations where you built something or significantly altered the terrain or structures. If they look ok, there likely was no loss, but if they don't, it's better to reload the world from an exported backup you took before the damage occurred and repeat the work you did in the aborted session. Then you can be fairly certain there's no damage that could be compounded by repeated failures to save the world.

I will now resolve this report as Invalid, because there's not enough evidence that a bug in Minecraft caused your problem. It's possible that a bug was involved, but if so it was in a past release and we can't identify any way to reproduce it, so the devs couldn't even begin to fix it. Good luck with your future Minecrafting!

Thank you for the world copies. Note that if you published "Can edit" links, the files could be modified by a third, possibly malicious party. If these are the actual save files and not copies in a different folder, you might want to consider them suspect now. If you ever have a reason to share files again, I recommend you use the safer "Can view" links instead.

I have downloaded and analyzed your world saves, obtaining the following information:

• Created in release 1.14.1 (Possibly a later release, but not much later)

• World spawn coordinates: X=1416, Z=4 (slightly different from what you said)

• Time spent playing the world: approx. 14D 16H 43M (Primary), 10D 14H 26M (Backup)
  Note that the world spawn Y coordinate isn't fixed. When you respawn, the game tries to place you on the highest solid block at the respawn coordinates.

• World save file sizes: 51.2 MB (Primary), 21.5 MB (Backup)

What happened?

Looking at terrain maps of your world, I see that it was corrupted at some point between the Backup save and the Primary save, and the damage was too severe to be fixable. Specifically, there is a 26-chunk-wide gap from X=1024 to 1439 where terrain was generated but the data has been lost. Sadly, your world spawn point falls within that range so all the building you did in that area is gone.

From your description you seem to have thought that when you teleported, the game placed you somewhere else but showed you the coordinates you'd entered. That wasn't what happened. The game placed you at the specified coordinates, but as there was no data to define the chunk there it regenerated the terrain around you, and the newly generated chunks are very different in 1.21 than they were in 1.14. The coordinates you used are now inside a mountain. The drastic difference is because the world generation redesign in 1.17 and 1.18 resulted in biomes being located in completely different places.

There's also some evidence that more corruption occurred quite a while ago, probably before release 1.18. I noticed 2 chunks centered at 1032,40 and 984,136, both of them in the middle of an ocean, but their surface is at Y=32 and Y=28, respectively and there is no water above it (they're holes in the ocean). This probably implies that the chunks were regenerated in some release before 1.18, which means the game had already tried to repair damage years ago.

How did the world corruption occur?

This kind of problem can be caused in a number of ways:

• By abruptly terminating the game, such as by a power failure, forced termination via Task Manager, or a crash caused by a very severe bug.

• By misusing a world editing tool (or using a defective one), for example to prune chunks. The game tries very hard to repair or at least limit the damage, but it isn't guaranteed to work.

• By using a defective storage device (hard drive, SSD, etc.)

• By closing the game without using the Save & Quit button. The game normally saves the world for you automatically, but this isn't guaranteed to work.

What can you do to fix it?

Unfortunately, anything you built in the damaged chunks between the Backup and Primary world saves is lost from the world now. If you regularly export backup copies of the world as you play it, you can work your way back through the available backups looking for the latest one where your  most important builds are intact, revert to that backup, and rebuild what was lost from later building. 

Since the hole-in-the-ocean chunks suggest you might have had repeated corruption, consider whether your habits for saving worlds need adjustment. You definitely should be using Save & Quit, and if you put enough time into a world that you would regret losing it you should be exporting it regularly, either before or after a play session.

Resolution of this report

World corruption can also be caused by a bug, but a bug that only affects one person and one world is ridiculously unlikely, so I doubt that a bug is involved in this case. Normally I would close this report. However, I want to give you a chance to respond in case you think my analysis is wrong. Please let us know if you're satisfied with it, or if not what else you think we should consider.

As a first step, we need to get copies of your saved world. The safe way to let us look at your files is to attach them to this report. However, there's a limit of 10 MB on attachments, and worlds that have been played more than trivially are typically larger than that, so we have a second way for you to share them from Windows using OneDrive. I'll assume you're using OneDrive. If you aren't, or don't know, just comment to say so and ignore the rest of this message for now.

If you're using OneDrive but your save files aren't in your OneDrive folders, I'll ask you to make a folder under OneDrive just for this purpose and copy your save files to it.

(Note: I'm on Windows 11. If you aren't, there may be some UI differences from what follows but the feature you'll be using is available from OneDrive. You may have to hunt for it a little though.)

With your save files in OneDrive, please right click on one of them and choose OneDrive, then select Share from the submenu. This will open a dialog. At the bottom is a section titled Copy link and it says "Anyone with the link can edit". Click on that and you'll see a More settings section where you can change "Can Edit" to "Can view". Then click Apply and you'll be shown a link that will let anybody view or make a copy of the file. Click on Copy and paste that link into a comment here (or you can add it to the description if you prefer).

My understanding is that you're saying you have two save files and the area around spawn is very different between them. If that is correct, please repeat the above instructions above for the second save file.

Let me also point out something else you should be aware of. The world seed you gave us above is "866 513 395". Did you insert those spaces to make it easier to read, or did you literally type that in for the seed when you created the world? You need to know that you can literally type anything in for a seed and the game will convert it to a number...but not the same number. When you type in a seed, if you only type digits (with an optional "-" sign), the game will use that number, but if you include any other character the game treats it as words and does some manipulation on it to turn it into a completely different and unrelated number that it uses as the seed. In any event, the real seed it used is shown in the world settings and that's the one you should give us, without changing it in any way, because when you change it we're not certain what your actual seed is.