In the latest Bedrock edition, Birch Forest M (the biome with unusually tall Birch Trees) will not generate. To make sure this is the case, I found Birch Forest M seeds for Minecraft Pocket Edition before Bedrock Edition was released and tried those seeds on Bedrock.
The seed I tried was 1560093373 and the Birch Forest M biome is suppose to be directly in front of spawn. Except, when I try the seed, I get just a normal Birch Forest and not the M variant. Other M variant biomes may not be generating as well since I do not recall seeing a Plain M or Swamp M biome either when I am seed hunting.
In the pictures attached, one picture shows the mountain with the Birch Forest M and the other picture is my screenshot of the normal Birch Forest I see in my game where the M variant is suppose to be.
EDIT: The other M variant biomes seem to generate normally including Swamp M biome. However, it seems Plain M biomes are turned into Roofed Forest M biomes. That's a shame cause Plain M biomes were cool to find but I know this was deliberate. The Birch Forest M biome not generating is definitely a bug and will need to be patched.
Edit 2: Another seed to try is -1114341188 and you will spawn with a birch Forest in front of you. This Birch Forest is suppose to be a Birch Forest M and it used to be a Birch Forest M in previous versions of Pocket Edition. I attached two more pictures (IMG_6803.jpg and IMG_6801.jpg) showing the old version and the current version.
Edit 3: Added 3 new pictures of a third example to prove the M variants did not change locations at all. The seed is -1879528770 and had a Savanna M/Birch Forest M combo to the left of spawn in the past. Now, the Birch Forest M is reduced to a regular Birch Forest but the Savanna M is still a Savanna M. In addition, Birch Forest M are a more mountainous variant of a regular Birch Forest. With that in mind, the huge mountains on the left in the old picture is generated only because it is in a Birch Forest M. Now, the mountains are still there but the trees are no longer tall. This means the game knows this exact spot is suppose to spawn a Birch Forest M as it does with the terrain but is spawning a regular Birch Forest as the biome instead.
Edit 4: Still an issue on 1.2.9. I included InsaneBirchForestM.png picture to show that the biome is definitely a Birch Forest M as the crazy terrain shows it is far too mountainous to be a normal Birch Forest but the trees are still bugged to be regular height. The seed for this Birch Forest M is 1365449400 and the coordinates is -30 77 250.
Edit: Still not fixed in 1.8. 1.9.0
Linked issues
is duplicated by 1
Attachments
Comments 12
@[MCPE Helper] Auldrick
Could you show us the seed and where you found a Birch Forest M? The fact you found one is very surprising as me and many of my other friends that hunt for good seeds have not seen a Birch Forest M after 1.2 update. The other odd thing is all other M variant biomes still generate in the same spot as previous updates with the exception of Roofed Forests replacing Plain M biome.
If Birch Forest M are still spawning like you said, they are currently far more rarer than Mushroom Biomes, Bryce Mesa, and Ice Spike biomes. In the past, Birch Forest M had about the same rarity as Flower Forests, Extreme Hills M, and Mega Taigas when we searched through seeds.
@[MCPE Helper] Auldrick I've witnessed the same issue as Alex. You may know that the biome generation is the same in Java as it is in bedrock - you find a mushroom biome on PC, then you can go to the same coordinates in that seed on Bedrock and it will be there. With this information, you can still tell where Birch Forest M's should be spawning, and like you said they haven't intentionally changed as the chunk generation wasn't changed between updates - therefore it's correct to assume a big is chasing their dissapearence.
@[MCPE Helper] Auldrick
Please check out my third edit. I understand your reasoning that Mojang could had changed the locations of M variant biomes but I have a counterexample to disprove that.
I withdraw my suggestion that Birch Forest M is still generating. When I read your description, it immediately made me think about the tall birches I had recently found, but I forgot about the version under which it generated. I found it in my personal survival world, which I have been working on for more than a year...well before this issue started happening. I found it when I took a wrong turn on a river and wound up in an area I'm not familiar with, but you've now reminded me that I made the same mistake on the same river a long time ago, so the chunk was very likely generated back then, well before 1.2. My apologies for the confusion.
@Tristan Miles: World generation can't be exactly the same as Java, because there are no amplified worlds in Bedrock. However, that's a quibble. My belief that it was different was based on the memory of trying a Java seed quite a while ago and finding it generated a similar, but not identical, world. But at the time I was a noob and didn't realize that biome generation was completely separate from terrain generation, I accept what you say about biome generation being identical, and thank you for pointing it out.
I can't truly confirm this for MoJira without spending hours generating a bunch of worlds and searching them for the missing Birch Forest M, but we have a "Community Consensus" confirmation status that we use in such situations when multiple users are all reporting essentially the same issue. I have attestations from the two of you, but it would be good to have a couple more. Could you have a couple of your seed-seeking friends comment to agree that Birch Forest M is no longer generating, for the record? (An unconfirmed issue isn't automatically ignored, but a confirmed issue gives the developers more confidence that it's a real bug.) Never mind. I realized I could just create another world with the same seed and check the coordinates in my screenshot. I can confirm this report the normal way.
Reopened for review.
One example:
Seed: -1879528770
Location: /tp 208 119 267
For the other examples mentioned in the ticket, it would be most helpful if you could provide a seed and coordinates of the places where the wrong biome/features are generating (if possible).
versions of MC, as betas and non betas have different seeds! And will appear differently if typed! Every version of Minecraft works differently 😞 maybe you are on Beta?
@@unknown
I am using the full release of v1.8.0 on Bedrock Edition and the seed GODmedpups ( 1365449400 in number format ) and I am going to the Birch Forest M at -30 77 250. In fact, the picture of this seed's Birch Forest m is already attached to this report under the name of InsaneBirchForestM.png. I also tried the other seeds in this report as well and they all work for me.
If none of these seeds are working, can you state what version of Minecraft you are using and where exactly are you putting the seed when creating a world?
I was recently in a forest with super tall birch trees in my world. (See Tall birches.png.) I had never seen them before, so it was remarkable. So if Birch Forest M is the only biome where they generate, there must be another explanation why you don't find them where you expected.
It's possible the seeds you checked no longer generate the world the same way. The older your previous use of them was, the more likely it is that world generation has changed since then.
Mojang does change the chunk generation algorithm occasionally. It doesn't affect chunks that have already been generated, because those are saved in the level database, but it can cause bizarre discontinuities where an old generated chunk adjoins a newly generated one. In this case, my tall birches were in the middle of a giant Birch Forest biome. Maybe Mojang decided Birch Forest M should only generate where Birch Forest would surround it. At any rate, it doe generate.