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

Escape characters don't work with items

XMLWordPrintable

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

      In 1.14 Lore formatting changed and you have to use  "\n" for new lines unlike 1.13 where you could put a simple coma between lines. However using "\n" does not put the text in the second line instead it creates (I believe) a "Line Feed" symbol between lines.

      ex.

        1. Bug1.png
          Bug1.png
          21 kB
        2. Bug2.png
          Bug2.png
          4 kB
        3. BugC2.png
          BugC2.png
          11 kB
        4. Screenshot_2.png
          Screenshot_2.png
          11 kB

          [MC-154787] Escape characters don't work with items

          James Jenour added a comment - - edited

          MC-39987 which was marked "Working as Intended", was not actually "Working as Intended".
          MC-39987 has been fixed. You can now use \n in chat.
          However, you still can't use \n in item lore.

          This report is neither a duplicate (since it's about items, not chat) nor working as intended (see above). Please reopen it.

          As for why I'd like this bug fixed:
          While it is possible to simply use a "list of lines", this is not possible when working with translations.
          I would like to be able to have a translation that is 2-lines long (eg. English) and a translation that is 1-line long (eg. Japanese).
          This would be really easy to do if \n worked in item lore, because I could simply make it so that the English translation has a \n in it.

          James Jenour added a comment - - edited MC-39987 which was marked "Working as Intended", was not actually "Working as Intended". MC-39987 has been fixed. You can now use \n in chat. However, you still can't use \n in item lore. This report is neither a duplicate (since it's about items, not chat) nor working as intended (see above). Please reopen it. As for why I'd like this bug fixed: While it is possible to simply use a "list of lines", this is not possible when working with translations. I would like to be able to have a translation that is 2-lines long (eg. English) and a translation that is 1-line long (eg. Japanese). This would be really easy to do if \n worked in item lore, because I could simply make it so that the English translation has a \n in it.

          [Mod] CubeTheThird added a comment -

          zippee100, as indicated in this report, it is a duplicate of MC-39987, which has been resolved as Working as Intended.

          [Mod] CubeTheThird added a comment - zippee100 , as indicated in this report, it is a duplicate of MC-39987 , which has been resolved as Working as Intended.

          zippee100 added a comment -

          this bug is still ongoing.

          zippee100 added a comment - this bug is still ongoing.

          [Mod] tryashtar added a comment - 
          /give @p pufferfish{display:{Lore:['"Line1"','"Line2"']}}

          [Mod] tryashtar added a comment - /give @p pufferfish{display:{Lore:[ ' "Line1" ' , ' "Line2" ' ]}}

          Ayberk added a comment -

          Are you sure? Because first thing I tried was that and it gave me an item without a lore

          Ayberk added a comment - Are you sure? Because first thing I tried was that and it gave me an item without a lore

          [Mod] tryashtar added a comment -

          The old way is still used, a list of lines

          [Mod] tryashtar added a comment - The old way is still used, a list of lines

          Ayberk added a comment -

          No, it just adds a carriage return symbol as well.

           

          Ayberk added a comment - No, it just adds a carriage return symbol as well.  

          [Mod] CubeTheThird added a comment -

          Does using the carriage return make a difference? E.g. \r or \n\r ?

          [Mod] CubeTheThird added a comment - Does using the carriage return make a difference? E.g. \r or \n\r ?

            Unassigned Unassigned
            PwParadox Ayberk
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: