cks Jaguar
Assigned
Reported
Comments
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.
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.
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)!
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 Mega_Spud
He did on MCPE-58480 recently (as of the time of writing). The issue still exists on 1.14.2 (PS4 2.02).
Thanks
-Kyle
My PSN ID is cks4205
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.
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
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.
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'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).
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 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.
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 think mine has the same issue, but it wouldn't explain the 2nd chunk being reverted to 2015 as well.
No fix... Oh well.
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.
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 🙂
Seems another user here has the same issue. I've pasted my story above into its comment section. https://bugs.mojang.com/projects/MCPE/issues/MCPE-58480?filter=allopenissues
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.