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

Villagers ignore name/lore on custom trades, only care about damage values.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Duplicate
    • Affects Version/s: Minecraft 14w30c
    • Fix Version/s: None
    • Labels:
      None
    • Confirmation Status:
      Unconfirmed

      Description

      Example:

      Named: "Quest Item"
      Lore: "Turn this in for super rare reward!"
      (minecraft:paper)

      Villager will also accept a regular piece of paper, which ruins this attempt.

      Now, if you give said item a damage value, the villager will care.

      As a bonus, the item also won't be craftable in normal recipes, which means for a custom adventure the user can't consume a quest diamond for a shovel or what have you.

      Damage values have been great until recently... However, as of recent snapshots, damage values turn items into broken textures.

      I've been told a myriad of things on this:

      • Villagers acknowledge lore on items. THEY DON'T.
      • You can use a duplicate texture in a resource pack. HOW? I can find no evidence this is possible...
      • This is intended and no longer a feature – breaks all the custom maps people have been making recently I'm sure, if so. If this is intended, it just killed a 2 month project for me.

      Bottom line, I'm just desperate for a solution to a drastic game change of an important feature I and many others have been making brilliant uses of. If I can't keep textures on DV's, and I can't reskin them with a resource pack, then why don't villagers acknowledge everything else on an item?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              Spoon_Boy Spoon Boy
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: