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

Ominous Banner's orange name is handled as a custom text color, rather than as a rarity

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • 24w33a
    • 1.21
    • None
    • Confirmed
    • Text, UI

      The bug

      Most Survival-obtainable items with non-white name colours have this aspect defined through the rarity system. Ominous banners do not, which is the root cause for some inconsistent behaviour when compared to items using rarity:

      • MC-132201: items with rarity don't display name colours in shulker box tooltips; ominous banners correctly do
      • MC-249067: ominous banners lose their name colour when renamed, which does not happen for items with rarity

      Steps to Reproduce

      • Obtain an Ominous Banner
      • Run /data get entity @s SelectedItem while holding the Ominous Banner

      Observed Behavior

      The color field is used in the item_name component to specify the Ominous Banner's name's color.

      Expected Behavior

      The rarity component is used to specify the Ominous Banner's name's color.

      How to fix

      Introduce a dedicated rarity for the ominous banner and apply it.

        1. 2024-07-25_10.49.37.png
          2024-07-25_10.49.37.png
          188 kB
        2. 2024-07-25_10.49.39.png
          2024-07-25_10.49.39.png
          182 kB
        3. 2024-07-25_10.49.50.png
          2024-07-25_10.49.50.png
          171 kB
        4. 2024-07-25_10.49.51.png
          2024-07-25_10.49.51.png
          167 kB
        5. 2024-07-25_10.50.28.png
          2024-07-25_10.50.28.png
          128 kB
        6. 2024-07-25_10.50.29.png
          2024-07-25_10.50.29.png
          128 kB
        7. 2024-07-25_10.50.33.png
          2024-07-25_10.50.33.png
          184 kB

            Unassigned Unassigned
            Awesoman3000 Connor Steppie
            Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: