I converted a world created on 1.17.11 (seed: -6643344; all experimental options on at generation except "additional modding capabilities" and "Holiday creator features"; survival mode, normal difficulty) to 1.17.30.25. last week.
Today, after exploring some distance from my base, I entered a village of the taiga biome type. About 4 houses were cut in half and part-submerged in a lake.
Other abnormalities such as a free-standing submerged ladder and a campfire burning underwater were also present in/near the transected buildings.
Screenshots attached.
Similar to reports MCPE‐45096 and MCPE-45870, but these are extremely old and not in reference to 1.17.
[media][media][media]
Linked issues
is duplicated by 14
MCPE-141711
the village house fell down into a hole
Resolved
MCPE-141923
When I opened my world in 1.17.30 world generation was glitchy
Resolved
MCPE-142679
Structures and natural decorations get smeared all over mountains in converted 1.17 worlds
Resolved
MCPE-148725
Bugged large mushrooms
Resolved
MCPE-149223
Old and new world generations connection error
Resolved
Attachments
Comments 5
The entire world was generated on 1.17.11.
I suppose it is possible that that chunk was loaded before - I always set my simulation distance very high, so moving around out of sight at a distance might have loaded the village or parts thereof.
Worlds started looking radically different after the new terrain generation features were introduced in 1.17.30.24, so I'd expect the same as you on a new world on that seed - no village.
The reason for the report was defective world conversion. It's possible that only certain chunks of this village had previously been loaded, and those were all that were retained.
@Matthew Ferguson: When I generated a new world on 1.17.30.25 using that seed, I got the same results as you - no village there. This probably excludes a platform issue causing this.
i used a unnofficial bedrock launcher with the version the dude said. and the village was there. science the world gen is very different then I see that it might be broken
I've loaded up this seed on 1.17.30.25 on windows 10 and the village doesn't exist.
Was the world created in an earlier version of the beta? It's possible the chunks were generated in an earlier version.
I guess it's also possible it might be platform specific for some reason.
Does generating a new world with the same seed reproduce the problem?