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

Basalt and blackstone are not grouped together with other "polishable" stone types in the Creative inventory

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • 22w42a
    • 1.16.5, 21w08a, 21w08b, 21w11a, 1.17.1, 21w38a, 1.18.1, 22w12a, 22w15a
    • Confirmed
    • Creative
    • (Unassigned)

      For a comprehensive list of other examples of issues with item positions in the Creative inventory, click here.

      All tickets associated with item placement in the Creative inventory are valid for cases introduced in 1.16 and later as per this comment. Exceptions exist, which are valid for their own reasons.


      The bug

      These blocks, added in 1.16, have raw "normal" variants, as well as specifically titled "polished" variants. As such, it would be expected that they would be placed at the top of the creative inventory, as four other stone types of that specific description also are. However, they are instead found much farther down.

      It may also be worth noting on the side that smooth basalt is grouped with other basalt variants, whereas smooth stone is not grouped with stone itself.

      How to reproduce

      1. Open the Creative inventory
      2. Locate Polished Deepslate in Building Blocks
      3. Locate Polished Blackstone in Building Blocks
      4. Locate Polished Basalt in Building Blocks
      5. Note that there is a considerable distance between these items

        1. 2021-02-24_18.08.27.png
          2021-02-24_18.08.27.png
          371 kB
        2. 2021-02-24_18.08.28.png
          2021-02-24_18.08.28.png
          369 kB
        3. 2021-02-24_18.08.29.png
          2021-02-24_18.08.29.png
          372 kB
        4. 2021-02-24_18.08.41.png
          2021-02-24_18.08.41.png
          350 kB

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

              Created:
              Updated:
              Resolved:
              CHK: