6
Structure Bug
rangda15bangda
So a friend of mine was playing on bugrock, and recently had a glitch or something where a location they had previously been had spawned new structures. I didn’t get to see it happen, so I originally thought it was because they had turned up their render distance to look for villages better, but they claim a one of the structures had spawned in their direct path of travel. (They were exploring via boat.) Does anyone know if this is possible and how? I play mostly Java, so I am unfamiliar with the array of bedrock bugs.
5
It's not bugrock 😡
Yes, this is exclusive to bugrock.
If you're traveling via any method (boat, walking, elytra), then the chunks will not actually be loaded. Once you unload those chunks, the world will forget they were ever loaded, and will be able to spawn new structures or world generation upon updating. However, the chunks will be saved if they are interacted with in any way, such as breaking or placing any blocks, opening a map in the area, dropping items, or interacting with entities.
About maps, there's actually any interesting bug where if you have a Level 0 map (128x128 blocks), then it will load in and save all chunks that would be saved if that map were upgraded to a level 4 map (2048x2048). That means that having a singular Level 0 map loads in a 2048x2048 block area, thus significantly increasing world size. (source here)
Bugrock edition is an interesting phenomena
If you're traveling via any method (boat, walking, elytra), then the chunks will not actually be loaded. Once you unload those chunks, the world will forget they were ever loaded, and will be able to spawn new structures or world generation upon updating. However, the chunks will be saved if they are interacted with in any way, such as breaking or placing any blocks, opening a map in the area, dropping items, or interacting with entities.
About maps, there's actually any interesting bug where if you have a Level 0 map (128x128 blocks), then it will load in and save all chunks that would be saved if that map were upgraded to a level 4 map (2048x2048). That means that having a singular Level 0 map loads in a 2048x2048 block area, thus significantly increasing world size. (source here)
Bugrock edition is an interesting phenomena
If I understand this correctly, then (in br)…
one should be able to find structures (like a Mansion) by traveling until one has the proper biome (a dark forest) in view, then repeatedly retreating and advancing (repeatedly loading and clearing the pseudo chunks) until the desired structure generates — but one would then need to interact with [all? | some? | at least one of? ] the chunks containing the structure to 'lock' it into the world.
one should be able to find structures (like a Mansion) by traveling until one has the proper biome (a dark forest) in view, then repeatedly retreating and advancing (repeatedly loading and clearing the pseudo chunks) until the desired structure generates — but one would then need to interact with [all? | some? | at least one of? ] the chunks containing the structure to 'lock' it into the world.
No. Structures still only generate based off of seed in BR, meaning that you cannot cheese the system by unloading and reloading the chunks. Them not being actually loaded and saved (and still somewhat contributing to file storage issues for some reason) only shows its effects when the world is updated to a newer version, which can cause strange anomalies to occur.
For example, frozen ocean generation was changed recently (1.21.1something) to match "parity" with JE (still don't agree that it's perfect parity..), but if you've already explored the frozen ocean biome, then the chunks that are saved are very sporadic. This causes updated chunks to overlap with older chunks (which for whatever reason are either frozen tundras or stony shores), giving it this corrupted look. This is a photo from my actual long-term survival world (DL here), where I had this happen to a frozen ocean biome that I was mining ice at.
.png)
Thankfully, I was able to recover the majority of it using AmuletMC to trim the chunks so that they were forced to load them into their default state that they would have been on that seed.
Structures can also be cut off from this glitch, such as in this example, a trial chamber being cut off.
.png)
In order to not have to deal with this glitch, interacting with something in every chunk is the only solution. That, or simply don't update. Although, unfortunately, BR forces you to update if you're playing online. You literally cannot play the game until it updates exactly when it releases. The only way around it is to disconnect from internet services while playing it.
My world size is ~1.1GB, which is quite large, especially given that I have only interacted with chunks around my main area, and explored quite a bit around that. However, in the areas that I've explored, I have not interacted with any chunks.
To clear up any confusion: it's not exactly that chunks aren't saved entirely, but rather, quite sporadically in the strange grid-like pattern shown above. All of these chunks are added to the world memory as if you explored them all.
A potential solution here could be to only save the chunk coordinates that you've loaded, so it doesn't change them upon updating (it still does change it. it was previously a frozen ocean, for instance, but changed some of the chunks to a frozen tundra/stony shore).
Hopefully this clears anything up.
For example, frozen ocean generation was changed recently (1.21.1something) to match "parity" with JE (still don't agree that it's perfect parity..), but if you've already explored the frozen ocean biome, then the chunks that are saved are very sporadic. This causes updated chunks to overlap with older chunks (which for whatever reason are either frozen tundras or stony shores), giving it this corrupted look. This is a photo from my actual long-term survival world (DL here), where I had this happen to a frozen ocean biome that I was mining ice at.
Thankfully, I was able to recover the majority of it using AmuletMC to trim the chunks so that they were forced to load them into their default state that they would have been on that seed.
Structures can also be cut off from this glitch, such as in this example, a trial chamber being cut off.
In order to not have to deal with this glitch, interacting with something in every chunk is the only solution. That, or simply don't update. Although, unfortunately, BR forces you to update if you're playing online. You literally cannot play the game until it updates exactly when it releases. The only way around it is to disconnect from internet services while playing it.
My world size is ~1.1GB, which is quite large, especially given that I have only interacted with chunks around my main area, and explored quite a bit around that. However, in the areas that I've explored, I have not interacted with any chunks.
To clear up any confusion: it's not exactly that chunks aren't saved entirely, but rather, quite sporadically in the strange grid-like pattern shown above. All of these chunks are added to the world memory as if you explored them all.
A potential solution here could be to only save the chunk coordinates that you've loaded, so it doesn't change them upon updating (it still does change it. it was previously a frozen ocean, for instance, but changed some of the chunks to a frozen tundra/stony shore).
Hopefully this clears anything up.
"Hopefully this clears anything up."
Yes, thank you
Yes, thank you
