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

Large Chests cannot be named

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 1.14.2
    • None
    • Unconfirmed
    • (Unassigned)

      When combined to make a Large Chest, neither of the chest's names (when renamed in the Anvil) show in the GUI, it only shows "Large Chest".
      Singular chests work fine, the name of the chest shows, but once combined, the name doesn't show. Both chests' names are still there if you break them and pick them up again.

      I tried the following combinations (in every direction as well, in case it was something like "north-facing chests don't work". this is not the case, it is all directions.)

      Unnamed chest, then named chest.
      Named chest, then unnamed chest.
      Named chest, then another of the same name chest.
      Named chest, then a DIFFERENTLY named chest.

      None of which had any name aside from "Large Chest" when combined. Upon removing one of the chests (making it a single-sized chest) the chest's name displays in the GUI.

      I also tried placing the unnamed chest, then the named chest on the right side, as well placing an unnamed chest, then the named chest on the left. And vice-versa with named first, then unnamed on either side.

      Pictures included are the names of the chests in the hotbar, the result of combining 2 chests into a large chest, and the aftermath of my testing various positions.

        1. 2019-06-05_09.42.15.png
          2019-06-05_09.42.15.png
          468 kB
        2. 2019-06-05_09.42.26.png
          2019-06-05_09.42.26.png
          598 kB
        3. 2019-06-05_09.42.37.png
          2019-06-05_09.42.37.png
          379 kB
        4. 2019-06-05_09.52.53.png
          2019-06-05_09.52.53.png
          2.15 MB

            Unassigned Unassigned
            kerfy03 Charles
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: