Dawson Berry

The issue still persists, only this time, the nether portal at x = 0, z = 0 in the Nether spawns the player outside of the corresponding x = 0, z = 0 portal in the Overworld.

Excuse me for saying this, but while I certainly agree that what's being talked about here is a bug, I should point out that it doesn't make sense for villager children to have all the same clothes and gear as adults, and thus, this bug may offer some potential for giving rise to new features in the same way that the bug with generic villagers originally gave rise to the Nitwit profession...

So perhaps the best fix for this bug involves both upgrading the old villager skins in a similar fashion to the various biome-specific looks of the Nitwit profession while making it so that these skins only ever occur villager children, and, simultaneously preventing the "minecraft:none" profession from showing up on adults during normal gameplay, perhaps by making sure that the clothes of villager children give a hint as to their future profession; e.g. white-robed villager children may grow up to be either librarians or cartographers, purple-robed villager children become clerics, etc.)...

Sorry, but I'm not quite sure what site to post this comment on, seeing as it is both bug-related and feature-related...

I wonder why no one seems to have seen this report... The issue still happens as of the most recently released version...

Okay, my mistake... I guess I just haven't been hanging around here long enough to really know the ropes...

Thanks for updating the list of affected issues, Killerbeenl... However, you missed 1.2.5.0, and the reason I know that that version is affected is because of MCPE-27986, which is a duplicate of this issue and lists 1.2.5.0 as an affected version...

Mega_Spud, I still think that someone should add 1.2.5.0 and 1.2.3.6 as affected versions in the description of this bug... It's bothering me that this hasn't been done yet, and I don't think I'm in a position to do so...

I kind of figured that there was more to this bug... I guess this bug is like an onion and the hotfix update only removed one or two layers of it...

Judging from what I've heard here about Blaze's case, along with my own and that of several other people, I think this bug might be partially connected to world seed, and which layer of this glitch you see happen in your world (if any) has a lot to do with the world seed and the numbers that are being crunched by the game as a result...

I just finished checking two more areas of my world, and they're also intact... Because my world was fully explored prior to conversion, I'll know if something is amiss. So, I'll keep posting updates here to let you guys know what I find in my world...

By the way, Koolen, I noticed the stutter you mentioned...

Good news, I just finished checking the central area of my world and there are no overwritten areas there... However, that's just one out of twenty-five areas I need to check... Let's see what happens when they finally get this whole bug fixed and not just one piece of it...

After all, my Overworld and Nether were fully explored before the Better Together Update, and that's a lot of terrain that needs to be converted...

Pascal, my world is 351.0 MB, and it's still not fully converted. However, it did get as much as 286.7 MB converted (a first for me), and I'm in the process of trying to see what's converted and what isn't. At least the town I built at x = 0, z = 0 is all there (also a first for me)... However, on the previous attempt to convert this same world, the aforementioned town was completely absent, replaced by new chunks...

They updated the game yesterday without announcing it, and I only found out about the update here in the comments section on this site. I think the update was a partial fix for the world conversion process. However, they still have a ways to go yet before it's completely fixed...

Since MCPE-27986 is a duplicate of this, can someone please add 1.2.5.0 and 1.2.3.6 as affected versions in the description of this bug?

Those bad reviews are warranted all right... but I think the devs may need more time to study this issue before an adequate fix can be made, Callum... After all, with an issue this bad, you don't just want a quick fix, but a good, solid one. Until that fix comes, let's just try converting worlds that are smaller than 200 MB, and see if this glitch affects those... Also, we need to be proactive and look for duplicates on this site that haven't yet been identified as such, like I said. Those are the only steps I can think of for us to take right now...

Hmm... Maybe the prospect of having to deal with such a massive and likely complicated bug is simply daunting to the developers... I would think that the case... especially if one is trying to unify play on different devices that originally ran Minecraft with different code bases...

As far as I'm aware, this is the first time something like this has been done... and don't forget... they still have to worry about the release of Minecraft on Nintendo Switch... So, if they want to avoid a similar disaster to this one, they'll have to work even harder to try and get the Switch version functional... and hopefully, that means finally fixing this bug...

Wow, those reviews certainly are bad... I would think that after seeing reviews like these, the devs would have the sense to try and fix this mess... Perhaps when their sales of this Bedrock Edition slump, they'll rethink things... Here's to hoping that's the case...

Of course, I'm still hoping they actually care and are trying to fix this and that they are not actually as apathetic as you say...

I certainly agree that there should be another beta just to give the devs time and space to finally squash this troublesome bug... Hopefully we'll get another Xbox One beta soon...

Are you sure that only files over 200 MB are affected though? To answer this question, maybe one of us should try creating a world that's smaller than 200 MB, then try to convert it over to Bedrock...

Mike, until the devs finally say something about this whole thing, how about let's all browse this site and look for more duplicates... That way we can actually help the devs out with this... Trust me, I've seen more duplicates of this bug than just the ones listed here on this page... for instance, MCPE-27986...

Sorry about the earlier versions of this comment...

Nice catch Pascal! This issue is a duplicate MCPE-25354. You know, the more MCPE-25354 duplicates I find, the more I wonder just how many people really have to deal with this problem... Since 1.2.3 didn't resolve this issue, perhaps what we need is another Xbox One Beta... That way we can send more samples of this glitch to the devs...

Al, the new chunks generating in your world is a manifestation of MCPE-25354, but the crash you refer to is something else...

Okay... at the time I made my previous comment, they hadn't yet updated the official wiki... Sorry about that...

Eh... the 1.2.5 beta is only for Android, not Xbox, and they still haven't actually released the full version of 1.2.3 yet... I'm still hoping that they're taking their time to study our world conversion issues...