Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-224006

Vegetation generates twice in villages, resulting in invalid blocks

XMLWordPrintable

    • Unconfirmed
    • (Unassigned)

      This issue has a different cause, please close it for now.

       

      After some experimenting, I've found that plants can generate both before and after villages.

      I made a datapack that shows this easily. Create a world with the datapack, and use the /locate village command.

       

      You can see plants generating normally in the grass areas, which means they do generate after structures. You can also find plants on top of smooth sandstone.

      Notice that plants never generate on the smooth sandstone in the rest of the world, so they can't naturally generate there after the structure. It means some plants generated first on grass and got their ground or part of them replaced by structures. This is basically what causes MC-140242.

      In the lower grass area you can find plants that both generate before (and are thus cut) and after the structure (generating normally).

       

      In the other image you can see this example with a support island. Villages have their own support islands so that they don't float, and it might be related to this problem.

      I suspect that vegetation is generated for the island first, and then normally for the entire world.

       

      It can be fixed by simply having all vegetation generate after structures. More information that can be found in MC-223305.

        1. 2021-04-23_18.14.18.png
          1.36 MB
          user-68c81
        2. 2021-04-23_18.28.07.png
          1.20 MB
          user-68c81
        3. 2021-04-23_18.48.07.png
          2.08 MB
          user-68c81
        4. 2021-04-23_19.00.07.png
          2.68 MB
          user-68c81

            Unassigned Unassigned
            jirauser631802 user-68c81 (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: