PS4 World Conversion to bedrock reverts some chunks to initial state

First bug I've found is that all but 2 of my maps in frames have been cleared.  

Here's my experience with this bug: I have been building my city world since 2014 on the PS3, but for whatever reason, the first chunk south west of the center of the world (0, 0, 0 heading negative X and towards the evening sunset direction) are reverted back to stuff I had back in 2015. The same thing happens to a chunk next to the map border on the east side of the map (within the legacy's central map). Once again, 2019 world meets the 2015 chunks once again (I'm just glad the rest of it doesn't look like 2015- that year was terrible looking in hindsight.)

I keep several copies of my world in case of a bug like this, and I've tried using a 2018 copy, a recent 2019 copy, and the current copy of the legacy-based world as the world to convert.

I've also tried editing the newest copy on the legacy mode, and the blocks that I placed right in front of myself didn't convert at all- when the world was converted during this attempt, I was sitting in a chunk with this issue. Another thing I tried doing: sitting next to the point of failure but not in the chunk itself, but there's no difference- it's always the same 2 chunks.

Lastly, I've removed all copies of my world from the PS4 so the system isn't trying to pull data from anywhere but the world I want to convert since I did have a 2015 copy on my PS4 at the time of discovering this issue. No difference still.

I'm hoping a patch will come out before I get too far into developing the future of my world on Bedrock Edition. My world's been through a lot of bug-filled updates over the years, even those infamous memory leaks that 2015 was full of, and I look forward to this being fixed 🙂

For Amanda Whistler,

Maps in the item frames disappear because maps no longer show coordinates of your position in the world. That happened to my friend in his world, which wasn't a big deal compared to chunks reverting back to default when not supposed to. hope this helped.

For cks Jaguar,

It sounds like your having similar issues to me, but my i started my minecraft world on the ps4 instead of the ps3. In April of 2018 i lost power unexpectedly during my session of minecraft. My main save file was corrupted. Had no choice but to reload from a previous save. As doing so, chunks in a different area of my world were reverted back to default. I lost everything i built and created in that area. It took me months to repair the damage in which in the end was finally all fixed, so i continued on with expanding. My current 2019 world is colliding with my 2017 build with mountains and trees are returning in areas thats been cleared where houses were built. Not sure what is causing worlds to collide, but its definitely a bug from a gamer's perspective. I've always backed up my saves since my corrupted save incident last year.

The new 2.0.0 update hasn't resolved this issue, at leats for me.

For Len Taboada,

I looked over the patch notes. it seems it was only minor bug fixes and not big ones like the conversion issues we're all having.

For Jesse

I think it's kinda weird because my world is so old, I can date the chunk errors back to a time between January and June 2015, based on 2 copies surrounding that era, whereas a newer world will simply lose all data. I'm gonna see if 2.00 fixes this for me because my case has data no matter what, but everyone else gets their chunks reverted to as if nothing happened/nothing was ever built.

No fix... Oh well.

Snap I've got a 255 by 255 "chunk" that has been reset for want of a better term. Mine would be about that old to. Prob from my PS3 era ish. Really don't want to try to rebuild the stuff in there 🙁

For cks Jaguar, 

Despite worlds being old, data is data. It should remain the same for the matter of times your transfer it. When converting it, no data should be lost. its like a puzzle. Our worlds are like a giant puzzle. When converting, the puzzle is being fully constructed. Some how the whole puzzle has sections missing and incomplete. But in the end, 35 yr old data thats been stored on a 3.5 inch floppy disk could still be read today and it would remain the same as it was when it was first saved. The same thing should be said for the save data of our worlds.

For Ilsley,

I think my world may have a 255 x 255 chunk reset in the spawn point.

 I think mine has the same issue, but it wouldn't explain the 2nd chunk being reverted to 2015 as well.

Well i'm taking a guess theres lines of code being read during the conversion. I'm going to say our worlds are comprised of lines of codes. Code 0 would be the world with no player structures built. Code 1 and onward would be structures we the players built in 1 map chunk area under section 1. going to section 2, meaning in a different chunk area the line of codes repeats from no player structures to players structures. The line of codes are stored containing information from when there was no structures to the clearing phase of that area to players building structures in that area. storing from when you created your world to now. My guess is the lines of codes are being read for multiple chunk areas, the computer or whatever thats reads the information during the conversion phase misreads the line of codes, resulting in the chunk areas reverting back or overflowing back to code 0, thus therefore erasing what us players built in that area. I am not familiar with coding or computing, but Minecraft behaves sometimes like a 8bit, 16bit, 32bit, and 64bit games. Theres always between 8bit to 32bit of integer overflow, causing glitches and many things to occur wacky in minecraft. best example is the 32bit integer overflow causing what is known as the far lands in some versions of Minecraft.

All I can say is that could be a viable explanation, but my world still has player built structures no matter what. So maybe the game is reverting everyone back to Q1 Q2 2015 in those 2 chunks? Or what would've been there during that era?

I'm going assume thats what the culprit is. In the conversion the computer is reading the lines of code from 2019, but when getting your 2 chunks, if the problem is occurring near the spawning of your world. I take it the bed spawn. The coding for those chunks is either misread or overflows, thus therefore reading the codes and reverting the chunk back to 2015, rather than the 2019 codes, along with whatever work you did after 2015. As seen in my pictures, its reverting back from 2019 to 2017 with a mix of 2016. 2016 being the start of my world, 2017 being the transforming and clearing of that area with some old structures, the railroad tracks and overwriting the 2019 structures, cutting some in half and deleting the rest. All thats occurring near my bed spawn point, where you return after defeating the ender dragon.

I tried moving both my bed's spawn and the world spawn to a nearby chunk that clearly works- no difference. And it still doesn't explain the eastern chunk being reset to the same early 2015 era as well. Houses that appeared in mid-2015 were either erased entirely, or the development of them was reset- Must've been Late Winter/Early Spring 2015 when those messed up chunks were "modern". I'm also using my house's color scheme to date the chunks- My house was converted to a different scheme within the first 2-3 months of when I first moved the world to PS4 in January 2015. I honestly wish it could've reverted to 2018 or 2017 because 2015 was a disgusting time for my city's progress from a quality pov. I have a tendency to pardon 2014 stuff since it was the first year of the city, but not 2015. 2016 would've been my compromise at the very least if I could choose.

One thing I will point out is item frames in the broken chunks did in fact convert, but obviously with it resetting to 2015, nothing is there where the item frames' background blocks were. I also removed all item frames and maps from the modern legacy version, no difference with fixing the issue still...

I see. well i don't know where we go from here other than continue to play on the old minecraft till a solution is found. Its hard to say if both 4j and Mojang have to sit down together to figure out this issue. I think 4j should have released a final bug fix update patch before bedrock came out. that could have possibly prevented this bug, but then again we wouldn't have known if would have done anything or not. With the 2.0 update for Bedrock, took care of some bugs, but nothing big as this bug, if it is even considered a bug. All i know is our worlds are fully converting over, but a specific chunk area is resetting for no reason. least near the spawn for me in my world at least. Servers are a pain.

This happens to me too. where i had build a building now there are chests that i put there some years ago, but not the recently blocks

Well about all we can do is have patience and wait for a fix, while we continue building our worlds on the old minecraft. I found whatever we currently build in our worlds will carry over, but just not in the chunks of our worlds that are strangely being reset back to a previous time. Other words we're time traveling between the time lines of our worlds and the different years of that world.

I have one world that does this, others that don’t. Oddly, although my stables was gone, the horses are still there. So are other animals but not their corrals. A cat sitting in a tree was originally sitting on the platform of my skyrail station. My house was definitely an early version, yet about 100 or so blocks away all my work was still there. The spawn chunks reverted but nowhere else.

In a twist, there are items in some of my chests that would not have been in the game back in 2015. One chest has several stacks of tube coral, in the original world these were coal blocks. Possibly, due to reversion to a time before coal blocks, the converter produced a different block. I also have several stacks of sweet berries in another chest. So, if the world was reverted to a 2015 version, where did the berries one from?

For Wenlock burton,

I am not sure where the berries would come from. The conversion definitely has something going on. All the chests in my house in world get fully erased as it reverts my house back to 2017 rather than keeping it a 2019. The chunks in my world break at the spawn point, but despite changing and moving to a different chunk location, the original spawn area chunks still revert back to a later period of time. The worst case scenario is that if theres no fix to this. its either we stay playing on the older minecraft or knuckle down and try to fix and rebuild what we lost. As much as i would hate to do that, loosing years worth of work. it be the only way to play the new minecraft, just not enjoy in the way we would like to, till all the damage is repaired. I'm still keeping my fingers crossed for a fix. Just don't give up hope.

Some of you are lucky that you can even play in your worlds. I get to 75% on the conversion and my game crashes, every time.

I'm surprised this thread doesn't have the Confirmation Status set to something not Unconfirmed. Definitely has a lot of comments and chat and surely they'd say they've found the issue (not necessarily a fix).

I did alot of reading up on users from xbox who suffered the same exact issue, who reported the bug on here. From what i've read, it seems they had quite alot of issues with world converting. You would think Mojang would have worked out the bugs before releasing it to the ps4. The xbox and ps4 may be 2 different machines but the bedrock coding is the same, hence the cross play feature. Perhaps this issue is only small compared to how major it was on the xbox, but despite it being small. Yes i would agree as to why its still unconfirmed. My pictures speak a thousand words of to what the issue is. As far as i know, no one has posted youtube videos about this issue. Everything seems to run fine, a few complaints here and there, but nothing about world converting issues. Some users from xbox said they continued trying to convert over and over till it went through. Some Mojang employees said try relocating the spawn into the center of a chunk in a effort to fix whats causing the chunks near the spawn to revert back to normal. Others said load up your world, wait for a few for everything to load, then hit exit and save and wait for the server to update the save, then try converting again. Its possible being wireless could have its issues with saving our world data to the server. Using a Ethernet cable for a solid connection could possibly work, but someone would have to take the time at testing to see if its worth going through the hassle for. it would be the only way to know for sure. If it all fails, then we're definitely going to have to try to get Mojang's attention to give us an update that this issue is being looked into. We're all still going to have to wait as 1 week approaches since bedrock has been released, along with my report of this bug.

I tried doing the spawn relocation, no luck. Also, a PS4 Bedrock Edition world's save data is made of 1 file (or if you copy to a USB drive, you have the main data file and a .bin file to go with it), and it is saved locally. They may have been having an issue with Realms if data has to sync with a server. I've also tried and tried again with converting the world constantly, even ones from previous years (but after the time of when the chunks that are messed up were new). They've resolved 2 clones of this issue for being duplicates, and they are tracking. I'd like to see them reach out for our copies of the worlds with issues because at that point, I'd send it to them- PS4 Ed. and Bedrock Ed.- in a heartbeat.

i see. I tried reconverting my world last night after relocating the spawn. the same chunks revert back to 2016/2017. The developers are about to go on holiday for christmas. We're more than likely going to have to wait till after xmas, when we can see any progress being done. I'd be more than happy to send copies of my world to the developers. I've done it multiple times with 4jSteve when i was still having trouble with my world. After my corrupted save issue when i reloaded from a previous save. I had chunks reset from 2018 back to 2016, despite it was a save just a few months back in 2018. Despite all that, I was able to fix and was able to continue playing in my world, but too much fire charges ended up in one chunk, so when trying to enter that area causes the game to automatically crash on the old ps4 edition. I still have this issue today, but it doesn't effect the transfer. We're all still going to have to wait alittle longer. I know we waited long enough for Bedrock, but we're going to have to wait more, till this world conversion issue is resolved.

The newest patch for minecraft on ps4 2.01 still doesn't fix the world conversion bug. Despite a new system software update for the ps4, followed by the update for Minecraft, the same chunks are still reverting back to 2016/2017 in my world. This is the 8th time i've done converting my world.

If they go on break, they better fix it after it because it would be the 2nd time I've had to wait until after Xmas to get an update from them- They did this in 2014, where PS3 and Vita got the newer update and PS4 didn't, so everyone who just got a new PS4 couldn't migrate until early January 2015.

I'm gonna attempt another transfer after work.

we'll just have to wait and see. but i wish you luck on transferring again. I just hope this gets resolved. Its just so annoying at this point.

For cks Jaguar, I noticed your video on youtube of demonstrating this bug. I congratulate you on your effort and the work of your minecraft world. From what i could tell your chunks are reverting close to the center of your world. The 2nd chunk you showed is about the same distance as my chunks from the center point of my world. You did a detailed job at explaining everything about this bug. When i saw the part when you said i beat everyone to it. I giggled at that. I wasn't planing on wanting to beat everyone, but someone had to report it. Guess i really am swift as the rabbits of Watership Down. I gave you a thumbs up on your video. When all this is said and done and we get our worlds converted over to how they are supposed to be. I will invite you to a minecraft community that is run by a friend of mine that i'm apart of. Its always nice to add more fellow minecrafters to the community, specially one who is experiencing the same issue as i am. Again thanks for posting the video on youtube. Have a wonderful Christmas and happy holidays.

That’s what I’m seeing, the chunks around world spawn are reverting. Beyond that all work is present and correct. My rail lines are cut off before they reach the central area. Still don’t know why i get stuff changed in some chests. We’ll see in the new year.

I'm personally not experiencing this, "chunks reverting back to set date". I'm only experiencing what appears to be an incomplete conversion, or a complete refusal of conversion of the same areas which becomes invalid, then renders new terrain generation in it's place. Also, my chunks near my world spawn are unaffected. My whole center map is okay. The biggest area affected for me is located at the top left map at the bottom right quarter of it, and another mid upper right quarter map somewhere i can't remember specifically. I'm sure there are other areas in my world that i haven't built anything at that are affected by this bug, i just haven't looked elsewhere other than where i have built, since that's what matters most to me in my world.

For Chris Dixon, The pictures shown of the issue occurring with my minecraft world are only 2 chunks away to the west and south west of the 0X and 0Y coordinates of my world, thus therefore i'm considered to be in the center of my world. For me in my world, it is just this cluster of 8 chunks refusing to convert my 2019 progress and instead reverts it back to 2017, erasing everything I built from 2017 to 2019. The rest of my world, beyond the areas that i've built things transfer over just fine. For me its only the center of my world thats being affected.

For Wenlock burton, Going from PS4 edition Minecraft to Bedrock, with it being a whole new minecraft game and engine, along with new blocks and items. I'm assuming your items in chests are shifting from what the PS4 edition has them valued as. the bedrock edition reads that value and displays the incorrect item with the same value for a different item from the ps4 edition. That could be whats causing your lost items, thought i am only guessing at this point.

For Jesse

You're welcome, message my PSN account in the description of the video if you're gonna invite me to that group. I'm also gonna attach a link to the video I made for the sake of adding evidence/proof of [the bug|http://https://www.youtube.com/watch?v=yutpC-3YVeA]. Feel free to sub.

I think we should all get pictures of the chunks that are messing up because my chunks, seen in the video, aren't exactly in the same spots compared to what I'm seeing up above in the previous comments

For Chris Dixon
My world is so old - watch the video https://www.youtube.com/watch?v=yutpC-3YVeA, my "reversion to original terrain" is literally player-made content. My world was originally a PS3 flat world, and most people are probably using a world that's newer than mine and/or is PS4 only, thus causing it to revert to what 2015 would look like if it had existed in 2015. I'm almost wondering if the "2015" chunks are from when I first expanded my world to Large.... Or something bigger than "Classic" on PS4 Console Edition.... Idk a thought I had because like I said, it's an old world.

Trying to figure out what’s happening with those blocks. One chest has several stacks of coal blocks but, after conversion, that chest has the coal blocks replace with blue coral blocks. Another has a loom and another has a smoker. As far as I can see, those two were probably both furnaces. Aside of so much missing, there’s item frames in mid air that were on dispensers. Most still have items in them. Most of the item frames are displaced a few blocks from their original positions. In an odd outcome, there’s one furnace in my house, after conversion there are three furnaces (probably was that way long ago) and they have blue coral in the fuel box. Lastly, a chest has several stacks of sweet berries which I never had in the original world. All double chests have become single chests.

For cks Jaguar, By adding you over psn I can assist you by showing what the chunks look like on ps4, then show them reverting in my world on bedrock.

For cks Jaguar, looks like i found another video of a person who did a report about this bug. The reason i never found it is because its just listed as a minecraft ps4 bug, doesn't mention anything about world conversion bug since that what it truly is. There are hundreds of videos of people reporting minecraft ps4 bedrock bugs and now theres only 2 videos made about worlds not fully converting from ps4 to bedrock. So with that said, hopefully we can get some steam rolling to get this bug defeated.

My PSN ID is cks4205

For cks Jaguar, I'll add you over psn as soon as i can. been tied up with family and christmas. For all that has this issue, hopefully after xmas the development team can get to work at fixing this bug. We're just going to have to wait more, though we all have waited long enough. I want to wish everyone a merry christmas and have a happy new year. Keep the spirits up.

Wenlock Burton, I am having a very similar issue with world conversation. Old items stored in chest or furnaces changed general to new version items. Red stone became polished quartz stairs, and enchanted diamond sword became an enchanted jungle-wood trap door, coal in furnaces became blue coral etc. interestingly, the world itself in someways did update to 1.14 the water is different along with bio, rabbits/fish other realitively new passive & neutral mobs spawned, and in game mechanics changed. I haven’t tried leaving towards the edge of the world boarder then returning. Figure this might change mob generation, but for the items no clue. Strange thought that only some items were affected like the sword while other items like my bow remained the same with the same enchantments.

Looking on the official Minecraft wiki, the up coming update for Bedrock 1.14.2 will be fixing minor bugs, but does not contain any bug fixes in world conversion. Though it may change when this bug gets recognized, but if not. I wouldn't get too excited for when the update rolls out. We're still just going to have to wait even more, despite how exhausted most of us are when it comes to waiting. Hopefully this will be fixed before Minecraft Dungeons rolls out in spring of this new year.

So Im having the same issue. One section of my city in my world reverted back to 2015/16ish. Very frustrating as I would like to move to bedrock completely. Has anyone heard from Mojang regarding this?

For Chris Z,

No one hasn't herd anything from Mojang about this bug as its still opened. Most of us are just playing on the old Minecraft till this bug is fixed before moving over to bedrock entirely. Alot of us as been waiting for almost a month. This bug had occurred on Xbox as well when bedrock was first introduced there. More than likely we're just going to have to wait as the developers deep dive into the root of the problem. More importantly Bedrock 1.14 on PS4 is a beta as developers are testing to make sure sure the game can run smoothly on ps4 without any issues. Theres been some gimmicks here and there. Once 1.14 becomes more stable, it should correct the problem in world conversion, hopefully. Developers are currently working on update 1.14.2 for bedrock to fix more bugs. With the attention of this bug they may delay 1.14.2 to include this bug or could be waiting till 1.14.3. Only time will tell. About all we can do is just wait.

Sorry to hear that you are still experiencing issues with converting your worlds over. Have you tried creating a new world with the same seed in the latest 'editions' version on PS4, building some structures, and then converting that world to Bedrock? If this is a reproducible issue, could you please provide the seed where this is happening?

So i am to create a new world by typing the seed number code in and spawn in that world and build some structures, then try converting to bedrock. Correct?

Ok. I made a new world, using the same seed code on the ps4 edition of minecraft. I built a small mossy cobblestone house in the world. I placed it in the exact same X and Y coordinates position on my world that is having trouble converting over. As far as I can tell the world conversion went very swiftly and the cobblestone house i built is still intact. nothing has been effected. Everything is as it was. Only difference is the terrain generation formation is completely different than from what it was when i had first started major transforming. I started near a swamp biome.  In the new test world i'm in a grassy plains biome. I hope this has helped.

Thank you for testing that out - it will hopefully help to rule out at least some of the issues.

Sounds good. It is a bit of good news for us Minecrafter's who's been plagued by this issue. We hope to hear more updates soon.

When I convert my world to bedrock it does all the exact same stuff and for some reason my seed even changes to a different seed when I’m bedrock. I’m not sure if maybe that has to do with all the corruptions. My world pretty much is gone when I switch to bedrock!

For Colby heimlick,

Sorry to hear your having trouble. Its best to continue playing on the old version of minecraft, where everything works. Developers are currently investigating the issue. Hopefully we'll get an update sometime. About all we can do is wait patiently. I wish you and everyone here good luck on your worlds.

Guess I'll chime in here. Maybe if they get enough complaints and comments, they might actually do something about it. But, I won't hold my breath. My ps4 world, that I started in 2013, has been torn to pieces during it's conversion to Bedrock. I had a huge triple pod Iron Golem farm that was completely cut in half and replaced with new land, and the one pod that was left alone doesn't seem to spawn Iron Golems anymore for some reason. I had a huge mob grinder that is completely gone now. Left in it's place, a giant stack of minecarts from the minecart elevator I built to climb up to the grinder. I had a big zombie pigman grinder that is also completely wiped out, and again a giant stack of minecarts in it's place. All of my builds that were completely wiped out seemed to retain only some of the items I had stored in chests near these builds, and the items were just strewn across the ground, or in trees, or floating in the water. I had a gigantic underground vault that was one of my first big builds. So large, it had 756 double chests, half of which were filled with items. When I visited my vault for the first time in Bedrock, a bunch (but not all) of the items I had stored were floating in the water at sea level above where my vault was located, and where my vault was is now just caves again with some scattered items throughout the new caves.. I even had a cat that I name tagged and let wander around my vault that was killed as soon as soon as I got close enough for that chunk to render for the first time in this new Bedrock version of my world. As I approached, I got a notification on the screen that said my cat suffocated in a wall..... IT KILLED MY CAT!!! Some parts of my world were (seemingly) nearly untouched though. I have a small city that I've been working on for a long time. Most everything seemed to be there. I did notice that some random chests were gone along with all of their contents. In my city, at the top of a skyscraper I built, I have another large mob/zombie pigmen grinder that also doesn't seem to want to spawn mobs anymore. I have a witch farm that doesn't spawn witches anymore. I have a slime farm that doesn't spawn slimes anymore. And I have a guarding farm that doesn't spawn guardians anymore. I also have an enderman farm in the End that was nearly half regenerated, AND THE DRAGON IS BACK.. Although, I don't know yet if this was a result of the Bedrock update, or from one of the End updates they've made some time ago. I haven't been to my End in some time. I actually stopped playing Minecraft on my PS4 some time ago because I got so tired of every time I loaded my world, another one of my redstone machines, or mob grinders, or something no longer worked because of some change they implemented. It was literally EVERY SINGLE TIME there was something else broken that wasn't broken before. It was infuriating. But, when I heard that they were finally standardizing the game with the 1.14 update and going to keep them all inline from here on out, I thought I'd give it another chance, and see if I could get back into it. I guess instead they decided to double down, and instead of just breaking random builds with changed mechanics of the game, they just decided to completely destroy 65% of my world this time. Guess I won't be coming back to this game after all. At least not until they fix this issue, which they probably won't. I reported a bug in here in May of 2016 that to this day still has not been fixed, it was "postponed"... And you can't tell me that they didn't know about this conversion bug before they released this to PS4 consoles. I am a programmer and I have never seen a bug of this severity before. I would not have a job anymore if I released to production a bug even 1/10th as severe as this. It's not possible they did not know.

For John Sanders,

The Redstone behavior in Minecraft has been different from console edition since bedrock was created from day 1. Everyone has complained about that since the beginning. I have automatic drilling machines to remove mountains for me, I have a 4 digit 7 segment display counter. All of my machines no longer work. Its one of the sacrifices going to bedrock. It would be nice to have the old redstone console behavior back, but the more important thing right now is fixing the world conversion error bug, that's causing our worlds to revert back and break. The xbox one console users suffered the same issue as us playstation users are experiencing. Patience is a virtue, though many of us as been waiting for over a month already. Its hard to say what else to do from here, other than just continue playing the old minecraft. I've crafted hard, I had problems and issues effect my world, at one time I quit playing minecraft for month and then came back. I've been fighting minecraft every step of the way. For when bedrock came to ps4, I had hoped Minecraft and I could get along, but seems like we don't. So the battle continues. Developers are still diagnosing the problem. It's possible they may have to contact 4j studios to work out the problem, but its hard to say at this point. Bedrock edition on PS4 is still in beta form as we're on update 1.14.1. Hopefully 1.14.2 will come soon. Hopefully 1.14 will become more stable before update 1.15 comes. Waiting is all we can do. Developers know we're upset at this point, they know we're waiting. Hopefully we'll hear an update soon about the bug. If anyone here are youtubers, make videos about it, spread the word.

Forgot to say earlier, but my world wasn't converted from PS3. I wonder if the "older version" stems from an update to the world generation algorithm? My PS3 worlds appear to have converted ok. A creative PS4 world had a number of item frames pop off the walls and the outer maps on the map wall reverted to empty ones. Some stayed in the frames, some were in the floor. Also, in the survival PS4 world I can find most of my sky rails except the one going West. Everything West of spawn is gone.

For Wenlock burton,

It's hard to say what the issue thats causing certain chunks to break and revert back. The number seed our worlds generate isn't the issue as one of the developers asked me to test that out. Typing the world seed that my world is having trouble converting for a new world generated fine on ps4. building a few structures, then converting over to bedrock. the conversion was successful and my structures stayed intact. It's either our console worlds have broken chunks failing to convert or the program that converts the chunk data is misreading the information from them. It can't be corruption, otherwise our save data would be corrupted. It can't be a bad spot on the hard drive in the ps4, otherwise what data we save wouldn't be saved. Whatever the case may be, it sure doesn't explain why the chunks are erasing what structures we built and reverting back to a later period to default. I'm losing year 2020 progress in the affected chunks as those chunks revert back to the year 2017, erasing what i built and rebuilding structures i once started out with as seen in the pictures i submitted.

The conversion to bedrock edition should be a 1 to 1 conversion. Yet some worlds, mine being one of them resets chunks for no good reason. I don't know how the conversion works, but it should just be converting the data of all the chunks on console edition to bedrock edition. Somewhere in the process it is failing to read or convert forcing a chunk reset. I was anticipating the bedrock update, but I'll have to wait till they fix the conversion process. There was an old update way back in the early days that literally deleted players world, so I suppose it's not as bad as it could be.

For Jacob Whisenant,

I couldn't agree more. Converting from Console to Bedrock should be 1 to 1. Instead we're going from 1 to 0.  This issue plagued the xbox one users for awhile, till I assume it was fixed. Us playstation user's are facing the same issue. It's suspected we should be getting another update before the nether update is released, but i am not sure. I just know We're still on 1.14.1 beta for PS4.  If the world conversion isn't fixed before the nether update comes. I'd rather take my chances with a 3rd party minecraft world editor and convert it that way in hoping it would fully convert, bypassing the failing to read chunk data bug. It's just unfortunate that mostly everyone else's worlds converted over just fine, but a small group of us are having issues. It's a real shame. Hopefully we'll get a response soon from the developers.

With Minecraft Update 2.02/ 1.14.20 released on PS4 today, The world conversion bug is still present as the same chunks still continue to fail at converting from Console Edition to Bedrock. It only seems to be the over world chunks that are breaking. The Nether and the End are not being affected. I also noticed that add on packs you buy in the store are not avalible to select when configuring the settings for your world in addons and behavior packs before opening it in bedrock. I was wanting to add vehicles and trains to my world thats failing to convert over. The packs to put them in do not show up in the settings, even with cheats and experimental game play turned on.

Here’s a couple of shots of the remains of my PS4 world after conversion. There was a walled village with small shops, just the item frames and villagers remain. Inside the house, many chests didn’t convert at all and some item frames are also left in mid air.

Oh wow. I guess you can say the same thing is happening for me, but what your showing is only happening to one of my friends houses thats in my world, who's house is destroyed in the broken chunks reverting. Only the item frames, her armor stand, and horse are the only things that remains of my friends house. I'm hoping we'll have these issues resolved soon.

Would you be able to provide a copy of the world save for us to investigate please?

If the world is larger than 10MB you can upload the world to OneDrive or a similar file sharing site, and then share the link here.

For Jay Wells,

Which copies of my world are you requesting? The console edition, the bedrock edition or both? I must know, so i can prepare them for you.

Just send both lol the wait for the fix is going towards 2 months. How should I send them privately? I'm definitely providing mine tonight after work.

For cks Jaguar,

I'd like to send mine privately too. I know the bug has been going on for 2 months. I'm exhausted from waiting. I just want to enjoy bedrock without any problems and enjoy future updates that will come to Minecraft. I'm anticipating Minecraft Dungeons as we'll want its assets in bedrock to use in our worlds, since MC Dungeons is considered cannon.

For Jay Wells,

Not the OP but my world was also affected by the bug. Here is it if you want to give it a check, I have been building on it since around 5 years ago. It's the Editions version of course, not the Bedrock one. Hope this helps the team 🙂
https://drive.google.com/open?id=1nL5c6E4yEfLC68op7dI5soxPB-1q8bDI

For future world save submits, does anyone know a better privately way of sending copies of our worlds to Minecraft developers without worrying of other than just the developers downloading our worlds and checking them out? I just don't like the idea of open links here in the wide open, even if restricted to just users only. I'd rather send copies of my world over facebook for more private use, since i don't have a twitter account.

Here are the steps to retrieve a copy of the world save from PS4:

1. Make sure your BLANK USB stick has been formatted to FAT32

2. Go to Settings > Application Saved Data Management > Saved Data in System Storage > Copy to USB Storage Device > Select Minecraft > Select Saved World to copy > Copy

3. You can then upload and share that world copy. If the world is larger than 10MB you can upload the world to OneDrive or a similar file sharing site, and then share the link.

PS4 Update 2.03/1.14.30 was just released. The update still doesn't fix the world conversion bug as the same cluster of chunks are still refusing to convert. Also the game was extremely slow to load up other preexisting chunks beyond the area of where i last left off playing the console edition.

Conversion is still broken with the current version 2.03 minecraft ps4 update

For Jacob Whisenant, We're just going to have to wait more. There are other things developers were fixing before this bug popped up. Waiting is the only thing we can do. I know its been 4 updates, 2 months, and 3 days we've been waiting. They're working on the big Nether update as well as the final touches for Minecraft Dungeons as that releases this spring. For those of us who submitted our worlds, developers are currently looking into the chunks that refuse to convert during the conversion process. We'll have to wait for their response. I'll keep playing the console edition of my world, but i get the feeling it will be in vein if it still cannot convert properly to bedrock. But that's just me.

For [Minecraft] Mega_Spud (Jay Wells),

Has any progress been made on this conversion bug?

The Ps4 Minecraft 2.05 patch did not fix this bug. Is there going to be an update posted on this issue? I would love to see this issue resolved so I am able to transfer my world.

Mojang
You no longer have to give me a birthday present (I'm 19 as of today) because I just found the actual problem: 2 chunks that are in World Data 1 are overwriting what we want: 2 chunks in the same spot, but from World Data 2 instead! Change the converter to ignore the 2 chunks giving us issues when converting World Data 1 and it should fix it (and check World Data converting to be sure?). I deleted World Data 1, converted the world, and the chunks came back.... with data loss elsewhere, but who cares- my 2019/2020 stuff came back!
AND when I put World Data 1 back and deleted World Data 2, then loaded console edition- I saw my garbage 2015 stuff that I don't want in my 2020 bedrock world!
Wish me a happy birthday (March 4 only)!

For cks Jaguar, Happy Birthday by the way. From what i read, it seems you dug deep into what the issue is. Sounds like you may want to do a video about this. I am going to have to try this method you described to see if it helps bring my 2020 progress over instead of old 2017 progress. If it fixes the issue, then we'll know to delete older world data saves. Again thanks.

The conversion system is still broken.

Actually- It's not. Our worlds are saving 2 chunks' data to World Data 2 instead of World Data 1. If we were to delete World Data 2, update the 2 chunks in World Data 1 to match what we want- data from from World Data 2- the conversion would work.

Try this experiment after you back up everything:

Go into your app save data management, delete the World Data 2 for your world. Go to where your world is messed up in Bedrock edition. It should align with what you find as being messed up. Now redownload World Data 2 and remove World Data 1, then play the world on either Bedrock or console edition. You'll notice the chunks that are messed up in Bedrock are still fine. However, you'll also realize how a lot of other things will go missing if you expand outward from the center of the world. In the end it might be better to just move on without what's lost in WD1 until they tell the game to listen to WD2 instead of WD1 in just the 1-2 specific chunks we want.

Can't we just delete world data from like 1 to 5 and when playing the game and saving. the world data we're currently saving would replace 1-5 and convert it that way? Its what i plan on doing.

Deleting world data #1 didn't help fix the issue for my world. Everyone's world I assume is logged differently. The broken chunks for my world have to be some where between world save #2 and world save #5. Hopefully all of this will give developers an idea on where to look.

Experimenting with data
Do not copy anything I do until I find something reliable that works for me:
I'm messing around with data again, and I tried loading console with the primary WD (World Data) and WD1. I griefed the 2015 stuff that's in WD1, but only stuff within one chunk. I downloaded WD2 that was backed up already and I converted the world once again. It turns out- memory loss is still something factored in, but the expected stuff from 2015 I griefed was replaced with 2019 stuff (Woo!), but the other chunk I didn't grief with 2015 stuff was still there. I'll let you all know when I figure out some sort of mix of actions that will give me the results I want.

Just remember that Minecraft World Saves imported from PS3 were stored differently than how Minecraft World Saves are stored on the PS4. So until a solution is found for both, we will still be sitting at Square 1. Tinkering will all this save data, you would think this gives developers an idea on exactly what to look at. But we won't know till we hear back from one of the developers. They're still busy with other bugs and updates, including the big Nether update. So regardless we're still going to have to wait, unless a solution is found by cks. Its all we can do for now.

I would like to hear back from the bug fixers about this issue.

Like to point out that update 2.05/1.14.41 not only does it not fix the conversion bug, but it also seems to be glitching my character and texture packs. Every time i start minecraft, they fail to load and bought character packs have locked icons on them. Also the memory storage limit seems to display the incorrect amount of memory storage. i have 2, 500mb worlds which isn't alot of space. Then trying to turn on experimental game play, minecraft can't turn it on because i'm almost out of memory space. Needless to say this update is pretty upsetting. I'll be shelving Minecraft for the time being, going forward at this point.

I released my video on my fix for this bug & I have another video uploading as I type this for another error. It's unfortunate that I have to sacrifice my other chunks to fix MCPE-58480 the way I did, but it's what I was mentioning the other day- I deleted WD1. https://www.youtube.com/watch?v=bLPqGYeCxGM Mojang people: If you read the title, I'm sorry, but you have to clickbait to get paid lol I have no hatred towards you all, but I laugh whenever I think about how quickly I figured out the reason for the converter's glitch when I sat down and put my mind towards it. Major thanks to Mega_Spud for helping out so much that I thanked you in the video's description as well. Same to Jesse for starting this.

Well, I tried cks Jaguars fix. Not fixed for me. I got a later version from the time PS4 Bedrock rolled out. Partly. The immediate spawn chunk had stuff from the original but nothing I’d done after the release of Bedrock. Further away my homestead (Australian farmhouse) was only the northern half. I still had item frames in mid air were the other half should have been. A chunk to the west it simply reverted to 2015 again but at least all my skyrails and the station came over. Possibly with so much going on in my spawn chunks the data could continue into another file, possibly World Data 2.

For those that can no longer wait for a fix can try cks's work around. Note that it may not always work. Minecraft at this point has given me a tremendous headache. I could try juggling around the saves with my minecraft world, but if i don't like the results i see, then i'll just have to flat out wait till an actual fix is implemented. Now we just need a video to see if structure block builds saved on bedrock for ps4 can be transferred between worlds. A video or confirmation needs to be noted. I added more my theme park, despite my over world chinks being broken. I'd like to copy what i added to a new save once the chunks are fixed without having to grind rebuild everything over again. As I said, its a real shame and a headache for dedicated players. There's only so much a person can take before breaking under pressure.

In my world I do have the 2019-2020 buildings and so on but there are new Chunks for example there is a sudden a jungle biome where there was a plains Biome before could you help me?
 
 
REPLY
 
 
 
 
 
 
 
U

For Tuur smeets, thats part of natural generation, the way minecraft creates worlds. Don't know if theres much you can do about that.

IMPORTANT NOTICE!!! When new Minecraft features are added into beta, Minecraft youtubers will document and discuss the new addons and bug fixes. I had just seen this video here on youtube https://www.youtube.com/watch?v=xUpxPCRVg-I  You can either watch the full video or skip to 6:47. Apparently it is showed that our conversion bug has been defeated. I guarantee everyone will be trying it out in the next minecraft update rolls out and we will see if its been squashed once and for all. At this point I hope that it is. Many of us has lost alot of productivity to our worlds. Those of us that continued on despite having our chunks broken now come to a cross road of how to manage with the loss of new progress. I was hoping saved builds in the structure block would help, but it cannot be done due to the dumb memory limit bar. I'd like to copy my theme park addons over to my fixed world once i know the chunks are fixed.

With many of us on PS4 still trying out the new bedrock features. many of us don't know of what bedrock can and cannot do. I managed to try importing builds from my theme park into another world with no luck. turns out 3D import is required and is only exclusive to windows 10 only. If developers changed where the structure blocks saves its builds into its own file on consoles. when accessing structure block builds from any world would make importing a breeze, since structures blocks used from any world would access that very same file to save and load builds. Hopefully it would be a new feature to implement down the road, if it can be done without breaking the game. Happy crafting everyone and best of luck.

For Jesse, i have seen at the patch notes of 1.15.0.56 beta, that this issue is resolved. But, when could it be available for all of us at play station? Im at quarantine in Spain and I need to play my wooorld

For Jorge Vila Tarife, I don't know when the update will be made avalible. I'd like for it to be soon. I know most us are anxious to try the new update to see if it fixes the problem. I hope that it is truly fixed, but we also have to take in consideration that it could only be partially fixed, but without evidence to confirm that its 100 to 50% fixed. We have to rely on the information we have that it's 100% fixed. It will be nice to finally have this bug squashed. 3 months, 5 days, and 5 updates worth of waiting so far. Being battle hardened, I hope the scars will heal.

For Jesse, i saw the issue MCPE-58480 (this issue) at the patch notes as resolved. So i think is 100% sure isnt it?

With it listed in the patch notes, we can hope that its 100%. But you have to account the 1% of possible issues occurring elsewhere.

update 1.15 is being skipped as the fix for this bug has been added to 1.16 which is the nether update. so now we have to wait even longer now till summer, which is unfortunate for those, including myself that has waited long enough. at this point my minecraft will continue to gather dust. Now the question is what happens to all the things you built in the nether when the nether update is released? Does everything get overwritten or does everything stay the same as is? If my nether project gets overwritten or gets completely erased then I quit Minecraft at that point. I would have wasted 3 years of fighting this game. I'm tired of fighting it. With bedrock the fighting stops, but with this bug not defeated, the fighting continues.

For Jesse: What do you mean the bug has been added to 1.16? It's still in 1.15.0.56 beta changelog. Where did you get this info? 

the minecraft wiki here in the link is one of them. https://minecraft.gamepedia.com/Bedrock_Edition_1.16.0 the other is a youtuber here https://www.youtube.com/user/XxEcKoxSoldierxX/videos  that covers alot of minecraft features and updates in released beta builds and change logs. thats who i came to find out all the features and bug fixes in update 1.15 was added to 1.16. Mojang wants Bedrock and Java to be parity with each other and be on the same update together to reduce confusion. Which is nice, though bedrock needs to catch up to the features with java. With whats going on in the world, we have to have patience and respect the developers, till this matter in the world is resolved.

This bug really sucks. We've been waiting for a fix since the release date in last year. I understand they have thousands of bugs to fix, but a major issue like this one should be prioritized. It's such a shame a large group of developers taking so long to fix a major bug that is ruining people's gameplay. I don't like playing survival too much, I like creating stuff so I've been waiting for command blocks to use in my city world since I bought minecraft on my ps3 and now, many years after when they finally get released, I can't use them in my city because of this bug... They fix bugs and others appear, in the last update they "added a new bug" where you can't use colored texts anymore, it doesn't let you put the § simbol... 

Your not the only one who's been annoyed by this. the problem is that this was not a expected issue to occur. By the time bedrock hit the ps4, Mojang was already working on the next updates and content. most updates had been minor bug issues and stability for the ps4 since its release. I cried wolf the day i was struck with this bug. It took time for others to crawl out of the wood work to report the same issue, then it led to some youtube videos to draw even more attention. Whats sad was i had to watch youtube videos to find out that our bug is finally squashed and then oh well we're skipping 1.15 and instead will have the bug fixes to 1.16 instead. No communication or contact from developers on that. a notification would have been nice, but now we know that is hopefully  the bug is squashed 100%. In the end we have to wait on time.

So, I'm tired of waiting, so I just removed all the buildings in the affected area and I'm rebuilding everything again, I think it will take less time than waiting until June for the bug fix. 🙂 

its taking so long its still not working

Let's wait to the 1.16 release

The bug fixes for this issue is packaged into the 1.16 update which is expected to release I would hope sometime this month. Others are saying being the end of June and the beginning of July I hope it releases soon cause i've waited long enough too.

Now this bug is getting fixed in 4 days. In 6 months that issue is happening, I rebuilt the destroyed part of my world, built a giant skyscraper, opened a RP server on that city and now I'm building another one. That was very disrespectful for people who lost most of their world. I was lucky to have only 5-8 chunks destroyed. 

6 months is far too long. Mojang should just have released 1.15 when it was ready. Hopefully this bug is fixed once and for all. Loosing 8 chunks wasn't fun. I just hope we won't having any more issues like this when going forward on ps5. If i have to wait 6 months again for something to be fixed. I'm quitting minecraft for good. tired of waiting and tried playing.