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

Using /fill to place walls (mossy and normal) does not fill top block properly

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Duplicate
    • Minecraft 18w11a
    • None
    • None
    • Unconfirmed

    Description

      When using the /fill command to place walls, the topmost changing layer doesn't properly place; the block will not exist until a block update happens near it, but still prevents other blocks from being placed in that location.

      Repeating the command makes further layers of invisible, non-solid wall blocks at the next level down from the first layer, and so on until all wall blocks in the affected area are invisible/non-solid. Also, it seems to treat the visible walls as a separate block, as the visible walls are replaced by a command to place them, but the invisible ones are marked as not needing to be replaced.

      Attachments

        1. 2018-03-21_00.54.03.png
          2018-03-21_00.54.03.png
          1.11 MB
        2. 2018-03-21_00.54.18.png
          2018-03-21_00.54.18.png
          1.12 MB
        3. 2018-03-21_00.54.23.png
          2018-03-21_00.54.23.png
          1.14 MB
        4. 2018-03-21_00.54.32.png
          2018-03-21_00.54.32.png
          1.13 MB
        5. 2018-03-21_00.54.36.png
          2018-03-21_00.54.36.png
          1.14 MB
        6. 2018-03-21_00.54.47.png
          2018-03-21_00.54.47.png
          1.00 MB
        7. 2018-03-21_00.54.48.png
          2018-03-21_00.54.48.png
          948 kB
        8. 2018-03-21_00.54.50.png
          2018-03-21_00.54.50.png
          1.08 MB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              Natourious Nathan Grant Taylor
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: