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

Multiple-blocks-in-one-space blocks have inconsistent placement behaviour

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • None
    • 1.18.2, 22w17a, 1.19.4, 23w17a, 1.20.2, 1.20.3 Release Candidate 1
    • Community Consensus
    • (Unassigned)

      The bug

      There exist several blocks in Minecraft in which several instances of them can be placed within a single block space. For this report, I will divide them into three main categories:

      • Stackables: all slabs, snow layers
      • Groupables: all candles, turtle eggs, sea pickles
      • Coverings: vines, glow lichen, sculk veins

      In certain situations, inconsistent and undesirable behaviour can be sighted when placing these blocks.

      Placement Stackables Groupables Coverings Notes
      On top of a base block Generally impossible Stack increases Generally impossible Stackables and coverings cover the full face of the target block.
      On the side face of another block Stack increases Stack increases Generally impossible Coverings cover the full face of a target block.
      On the top of an existing instance Stack increases Stack increases Amount increases
      On the side of an existing instance Generally impossible Stack increases Group increases Stackables, being square-based and 16x16, do not permit non-flush placement.
      On the side of an existing instance, flush with wall New stack created on adjacent block if possible Generally impossible Stack increases No groupables fill out a full block.

      Expected results

      For vines, glow lichen and sculk veins, targeted sections would create a new block on any adjacent walls.

      Actual results

      Doing this causes a new instance of the vine/sculk vein/glow lichen to be created inside of the targeted block. If no space exists for one, placement fails completely, even if there is valid space for the vine/etc. to be placed on in the adjacent block.

        1. 2022-04-17_16.53.21.png
          2022-04-17_16.53.21.png
          493 kB
        2. 2022-04-17_16.53.33.png
          2022-04-17_16.53.33.png
          168 kB
        3. 2022-04-17_16.53.44.png
          2022-04-17_16.53.44.png
          29 kB
        4. 2022-04-17_16.54.22.png
          2022-04-17_16.54.22.png
          378 kB
        5. 2022-04-17_16.54.34.png
          2022-04-17_16.54.34.png
          252 kB
        6. 2022-04-17_16.54.45.png
          2022-04-17_16.54.45.png
          223 kB
        7. 2022-04-17_16.54.56.png
          2022-04-17_16.54.56.png
          244 kB
        8. 2022-04-17_16.55.49.png
          2022-04-17_16.55.49.png
          500 kB
        9. 2022-04-17_16.56.08.png
          2022-04-17_16.56.08.png
          116 kB
        10. 2022-04-17_16.56.22.png
          2022-04-17_16.56.22.png
          143 kB
        11. 2022-04-17_16.56.35.png
          2022-04-17_16.56.35.png
          171 kB

            Unassigned Unassigned
            Awesoman3000 Connor Steppie
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: