Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-156074

Decorative sculk vein patches are still clamped to generating below Y 20 in the Deep Dark

XMLWordPrintable

    • Confirmed
    • Multiple
    • 787487

      This vanilla parity issue is related to MCPE-155213. The fix for that issue was to raise the Y height in the 'sculk_patch_feature.json' file to allow sculk patches to generate up to Y 256, which was successfully deployed in 1.19.0.34 / 1.19.0.35.

      However, there is a related file named 'sculk_vein_feature.json' which controls generation of the isolated decorative sculk veins in the Deep Dark. This file still has its Y range limited to 20 instead of 256, causing the decorative sculk veins to stop generating at that height. (It also has its low-end value set to -64 instead of -63, which seems odd since the world bottom does not go below Y -63. But perhaps there is a technical reason for allowing generation to Y -64 with sculk veins?)

      While this is not a big deal, the fix is fairly quick and it would be nice to have the decorative sculk veins in sync with their sculk patch counterparts for all the permanent worlds generated by the official 1.19 Wild Update release. Java edition already generates both the sculk patches and decorative sculk veins up to Y 256, which is why this issue is labeled as a parity issue.

      Attached are screenshots highlighting the differences between Java and Bedrock. The seed and coordinates are displayed in the screenshots.
      bedrockY14.jpg - proper sculk veins below Y 20.
      javaY64.jpg - proper sculk veins above Y 20.
      bedrockY64.jpg - missing sculk veins above Y 20.

        1. javaY64.jpg
          javaY64.jpg
          140 kB
        2. bedrockY64.jpg
          bedrockY64.jpg
          84 kB
        3. bedrockY14.jpg
          bedrockY14.jpg
          114 kB

            MCExplorer44 MCExplorer44
            Votes:
            4 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: