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

Adding a biome to a datapack shifts biome IDs in existing chunks

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Fixed
    • 20w30a, 1.16.3, 1.16.4 Release Candidate 1, 1.16.4, 20w46a, 21w03a, 1.16.5, 21w17a, 1.17.1
    • 21w38a
    • None
    • Confirmed
    • Custom Worlds
    • Normal

    Description

      When a datapack with custom biomes is loaded, the biomes it defines are assigned IDs according to their lexicographic order. When a new biome is added to an existing world but its name gets sorted anywhere else than at the end, it causes the biomes that follow it to shift. Chunks only store the resulting IDs in their biome maps and not the names, so they become corrupted, showing the biome that precedes the correct one.

       

      This can be quite easily fixed if chunks stored not only the biome IDs, but also a mapping that allowed retrieving the actual name, kinda like the block palette already works for a chunk section. Since there is usually only one biome per chunk, it's just a matter of storing one additional pair in the chunk data. This would also make it possible to define more than 256 biomes for a world.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              IllidanS4 IllidanS4
              Votes:
              66 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                CHK: