Random 1 block biome generating?
So I just found this random tall grass that has a green color, while I was in a savana biome. All other tall grasses were in the savana biome color. I went to F3 to see what the biome is, and it said that the biome that the tall grass was on is Roofed Forest. The coordinates can be found in the debug screen on the screenshots, and the seed is -4951220008273932285.
Linked Issues
Created Issue:
Random 1 block biome generating?
So I just found this random tall grass that has a green color, while I was in a savana biome. All other tall grasses were in the savana biome color. I went to F3 to see what the biome is, and it said that the biome that the tall grass was on is Roofed Forest. The coordinates can be found in the debug screen on the screenshots, and the seed is -4951220008273932285.
relates to
is duplicated by
is duplicated by
Thank you for your report!
We're tracking this issue as MC-69731, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Won't Fix, which means this is considered a bug but won't be fixed. The description of that ticket or the comments might explain the rationale. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues in Discord or Reddit


I have some small stripes of plains or forest in my deserts or along the borders of rivers. No plains or forest biomes nearby.
Won't Fix, the world generator will not be changed anymore for a long time.
But it isn't the world generator, this bug doesn't change the generation, its the generation of the real biome, just the color of the plants and the biome techincally, not including its generation
Please reopen, see previous comments for reason.
Seems to be fixed in 1.13-pre6.
No need to update this issue, it was marked as "Won't fix".
But probably it's fixed.
Can confirm for 1.21.3