<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 11:50:44 UTC 2025

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Mojang Studios Jira</title>
    <link>https://bugs.mojang.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en</language>    <build-info>
        <version>9.12.2</version>
        <build-number>9120002</build-number>
        <build-date>10-01-2024</build-date>
    </build-info>


<item>
            <title>[MC-349] Villagers ignore data tags in trading</title>
                <link>https://bugs.mojang.com/browse/MC-349</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;&lt;font color=&quot;red&quot;&gt;&lt;br/&gt;
Re-opening applies specifically to data tags such as having a custom name&lt;/font&gt;&lt;/p&gt;

&lt;p&gt;Villagers will only check an item&apos;s ID, not its damage value or any other data, in determining whether they will accept it. This leads to interesting situations where a priest will fully restore an item&apos;s durability when enchanting it, and a modified villager requesting bonemeal will just as easily accept ink sacs.&lt;/p&gt;

&lt;p&gt;This bug also prevents map makers from designating custom items for villager trade (e.g. a piece of glowstone with a custom name and enchantment will be treated the same as an ordinary piece of glowstone).&lt;/p&gt;

&lt;p&gt;&lt;b&gt;What I expected to happen was...:&lt;/b&gt;&lt;br/&gt;
The villager would only accept the item if it was the same as the item they request - not if it merely shared the same data value.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;What actually happened was...:&lt;/b&gt;&lt;br/&gt;
Priests would accept damaged tools and fully restore them when enchanting them. Modified wool-buyers were colorblind. Names and enchantments on items were ignored.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Steps to Reproduce:&lt;/b&gt;&lt;br/&gt;
1. Find a priest with an offer to enchant an item. Enchantment offers are rarer than other offers, so this can take some time/spawning.&lt;br/&gt;
2. Attempt to enchant a badly damaged tool using this priest.&lt;br/&gt;
3. Observe that the item has been enchanted, and has also been restored to its maximum durability.&lt;/p&gt;

&lt;p&gt;3b. If you attempt to enchant a previously enchanted item with this priest, you will observe that the old enchantment is ignored and the new one is placed. However, normally it is not possible to unenchant an item, and even anvils will charge extra for overwritten enchantments, so this behavior is not consistent.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Caveat to fixing:&lt;/b&gt;&lt;br/&gt;
Although making trades strict would fix the issues outlined above, it would cause other issues. Farmers would then only accept white wool, and it would be impossible to fulfill a librarian&apos;s request for a Written Book.&lt;/p&gt;

&lt;p&gt;Instead, it may be preferable (if anything is done about this issue at all) to add a new tag to an offer, determining whether it is to be considered strict. Thus, among vanilla Minecraft offers, the priest&apos;s enchantment offers would be marked &apos;strict&apos;, requiring unenchanted items at full durability. As this would be an NBT tag, map-makers would also be able to make use of it to prevent the aforementioned issues in custom traders.&lt;/p&gt;</description>
                <environment></environment>
        <key id="11612">MC-349</key>
            <summary>Villagers ignore data tags in trading</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="5" iconUrl="https://bugs.mojang.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="searge">[Mojang] Searge (Michael Stoyke)</assignee>
                                    <reporter username="wolfiemario">WolfieMario</reporter>
                        <labels>
                    </labels>
                <created>Thu, 25 Oct 2012 06:37:18 +0200</created>
                <updated>Wed, 19 Nov 2014 16:47:01 +0100</updated>
                            <resolved>Thu, 30 Oct 2014 17:05:53 +0100</resolved>
                                    <version>Minecraft 1.4.2</version>
                    <version>Minecraft 1.4.6</version>
                    <version>Minecraft 1.4.7</version>
                    <version>Snapshot 13w01a</version>
                    <version>Snapshot 13w01b</version>
                    <version>Snapshot 13w02a</version>
                    <version>Snapshot 13w03a</version>
                    <version>Snapshot 13w04a</version>
                    <version>Snapshot 13w06a</version>
                    <version>Snapshot 13w09a</version>
                    <version>Snapshot 13w09b</version>
                    <version>Snapshot 13w10b</version>
                    <version>Minecraft 1.5</version>
                    <version>Minecraft 1.5.2</version>
                    <version>Snapshot 13w19a</version>
                    <version>Snapshot 13w21a</version>
                    <version>Snapshot 13w23b</version>
                    <version>Snapshot 13w24a</version>
                    <version>Snapshot 13w24b</version>
                    <version>Snapshot 13w25a</version>
                    <version>Snapshot 13w25b</version>
                    <version>Snapshot 13w25c</version>
                    <version>Minecraft 1.6</version>
                    <version>Minecraft 1.6.1</version>
                    <version>Minecraft 1.6.2</version>
                    <version>Minecraft 1.6.4</version>
                    <version>Minecraft 13w37a</version>
                    <version>Minecraft 13w37b</version>
                    <version>Minecraft 13w38c</version>
                    <version>Minecraft 13w39b</version>
                    <version>Minecraft 13w41a</version>
                    <version>Minecraft 13w41b</version>
                    <version>Minecraft 13w42a</version>
                    <version>Minecraft 13w42b</version>
                    <version>Minecraft 1.7</version>
                    <version>Minecraft 1.7.1</version>
                    <version>Minecraft 1.7.2</version>
                    <version>Minecraft 1.7.3</version>
                    <version>Minecraft 1.7.4</version>
                    <version>Minecraft 14w02b</version>
                    <version>Minecraft 14w02c</version>
                    <version>Minecraft 14w04b</version>
                    <version>Minecraft 14w05b</version>
                    <version>Minecraft 14w06a</version>
                    <version>Minecraft 14w06b</version>
                    <version>Minecraft 14w07a</version>
                    <version>Minecraft 14w08a</version>
                    <version>Minecraft 1.7.5</version>
                    <version>Minecraft 14w11b</version>
                    <version>Minecraft 1.7.6-pre1</version>
                    <version>Minecraft 1.7.6-pre2</version>
                    <version>Minecraft 1.7.10</version>
                    <version>Minecraft 14w27b</version>
                    <version>Minecraft 14w28a</version>
                    <version>Minecraft 14w28b</version>
                    <version>Minecraft 14w29a</version>
                    <version>Minecraft 14w29b</version>
                    <version>Minecraft 14w30a</version>
                    <version>Minecraft 14w30b</version>
                    <version>Minecraft 14w30c</version>
                    <version>Minecraft 14w31a</version>
                    <version>Minecraft 1.8-pre3</version>
                    <version>Minecraft 1.8</version>
                                    <fixVersion>Minecraft 14w02a</fixVersion>
                    <fixVersion>Minecraft 1.8.1-pre4</fixVersion>
                                                        <votes>36</votes>
                                    <watches>17</watches>
                                                                            <comments>
                            <comment id="197647" author="panguino" created="Fri, 5 Sep 2014 00:41:42 +0200"  >&lt;p&gt;Aaron PLEASE stop editing your comments after you post, re-read them carefully before you submit your posts.  Every time you edit them it sends everyone watching this Bug which is 30 people.   &lt;/p&gt;

&lt;p&gt;So far I have gotten 20+ emails of you editing the post you made, this is pretty irritating.&lt;/p&gt;

&lt;p&gt;Thank you.&lt;/p&gt;</comment>
                            <comment id="197641" author="redstoneexplorer" created="Fri, 5 Sep 2014 00:25:54 +0200"  >&lt;p&gt;The only fix for it repairing an item that gets enchanted by a villager seems to be that they just changed it to giving you an enchanted item for emeralds instead of enchanting an item you give them.&lt;/p&gt;</comment>
                            <comment id="197638" author="redstoneexplorer" created="Thu, 4 Sep 2014 23:57:15 +0200"  >&lt;p&gt;Sorry, I just tested that and you are right. Thank you for the input, I have only recently started trying to help on bugs/glitchs and have also only started testing them, so I don&apos;t know exactly when these fixes were implemented. &lt;/p&gt;

&lt;p&gt;It only applies the data under the tag data tag to the item under the trading gui.&lt;br/&gt;
The code is probably just missing for checking for a complete match, and it might be a simple fix.&lt;/p&gt;</comment>
                            <comment id="197627" author="skylinerw" created="Thu, 4 Sep 2014 23:23:29 +0200"  >&lt;p&gt;@Aaron, the problems is the inability to define the &quot;tag&quot; tag in the &quot;buy&quot; compound to force players to provide an item that has specific extra data, such as a display name or custom data. The &quot;Damage&quot; value detection was originally the issue, but was fixed a while ago in the 1.8 snapshots. The report remains open for the &quot;tag&quot; tag, specifically for the &quot;buy&quot; tag. The &quot;sell&quot; tag has always worked as far as I can recall.&lt;/p&gt;</comment>
                            <comment id="197625" author="redstoneexplorer" created="Thu, 4 Sep 2014 23:17:32 +0200"  >&lt;p&gt;In the 1.8 update, it seems this might have been partially fixed, probably because they went through and rebalanced villager trading. For the modified trades, the commands might not have been set up properly.&lt;br/&gt;
{Offers:{Recipes:[0:{buy:&lt;/p&gt;
{id:&quot;minecraft:Item name&quot;,Damage:0s,Count:1b}
&lt;p&gt;,sell{id:&quot;minecraft:Item name&quot;,Damage:0s,Count:1b,&lt;br/&gt;
tag:{ench:[0:&lt;/p&gt;
{id:1s,lvl:1s}
&lt;p&gt;,]}}},]}}&lt;br/&gt;
Mapmakers can easily set up villager trading using this data tag set up; tag:{ench:}} is optional.&lt;br/&gt;
Villagers will only accept the specified data values, so items like dyes and wool will work as intended now.&lt;/p&gt;

&lt;p&gt;entitydata @e&lt;span class=&quot;error&quot;&gt;&amp;#91;type=Villager&amp;#93;&lt;/span&gt; {Offers:{Recipes:[0:{sell:{id:&quot;minecraft:wool&quot;,Damage:14s,Count:1b,tag:{}},buy:&lt;/p&gt;
{id:&quot;minecraft:wool&quot;,Damage:0s,Count:1b}
&lt;p&gt;,buyB:{id:&quot;minecraft:dye&quot;,Damage:1s,Count:1b}},]}}&lt;/p&gt;

&lt;p&gt;This command will make a villager accept regular white wool and red dye and trade you red wool. It will not accept any other wool or dye color.&lt;/p&gt;

&lt;p&gt;Try using the command:&lt;br/&gt;
/entitydata @e&lt;span class=&quot;error&quot;&gt;&amp;#91;type=Villager,r=5&amp;#93;&lt;/span&gt; {Offers:{Recipes:[0:{sell:{id:&quot;minecraft:diamond_pickaxe&quot;,Damage:0s,Count:1b,tag:{ench:[0:&lt;/p&gt;
{id:35s,lvl:5s}
&lt;p&gt;,]}},buy:&lt;/p&gt;
{id:&quot;minecraft:diamond_pickaxe&quot;,Damage:0s,Count:1b}
&lt;p&gt;,buyB:{id:&quot;minecraft:emerald&quot;,Damage:0s,Count:10b}},]}}&lt;/p&gt;

&lt;p&gt;If I typed it correctly, this should change any villager within a radius of 5 blocks to offer the trade of a special diamond pickaxe with a fortune 5 enchant for a regular diamond pickaxe and 10 emerald. Unfortunately, this requires a fully repaired diamond pickaxe to work; trying to trade a damaged one will fail to work. If you wanted to have it not repair the pickaxe, you would have to change the value for the Damage tag under sell and buy so that they match.&lt;/p&gt;

&lt;p&gt;For an easier solution, there would have to be a way where it checks the damage value on the tool being bought by the villager and apply that value to the tool being sold.&lt;br/&gt;
The problem is that these data tags apply to the items seen under the trading gui, and it simply checks for a match on your item and applies the values under the sell tag to the item being given to you. It would have to apply the damage value of your item to the item being sold, and take the values under the tag data tag from the sell tag, and merge that with the data of your item.&lt;/p&gt;

&lt;p&gt;Sorry for the long explanation, but I hope this helps.&lt;/p&gt;</comment>
                            <comment id="183710" author="katipo" created="Sat, 2 Aug 2014 01:27:39 +0200"  >&lt;p&gt;Confirmed for 14w31a&lt;/p&gt;</comment>
                            <comment id="182202" author="naista2002" created="Wed, 30 Jul 2014 13:06:46 +0200"  >&lt;p&gt;Hello. I&apos;m mostly talking about Pocket Edition bugs (such as &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-1319&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;MCPE-1319 texture bug&lt;/a&gt;), but this bug made me worrying about custom maps and things like that.&lt;/p&gt;

&lt;p&gt;I agree with people who want the &apos;strict&apos; tags to be in Minecraft. Sometimes, one may need or just want to trade an used tool (enchanted or not) for a better one, but he/she may see a trade needing a fully-repaired tool. This is not a problem if you have an anvil, but custom tools may not be repaired like that (unless using custom attributes), while &lt;em&gt;repairing by crafting will remove all enchantments and revert attributes to normal&lt;/em&gt;. So, the &apos;strict&apos; tag will save most custom maps.&lt;/p&gt;

&lt;p&gt;Also note that I only played PC Minecraft on my brother&apos;s computer (versions 1.5.2 and 1.7.4). Other times, I played Minecraft Pocket Edition (demo and v0.8.1), but stopped due to &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-1319&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;MCPE-1319 texture bug&lt;/a&gt;, plus I cannot update to 0.9.5.&lt;/p&gt;</comment>
                            <comment id="178617" author="panguino" created="Wed, 23 Jul 2014 22:33:56 +0200"  >&lt;p&gt;Confirmed still broken in 14w30b&lt;/p&gt;</comment>
                            <comment id="173031" author="panguino" created="Thu, 10 Jul 2014 18:46:46 +0200"  >&lt;p&gt;Confirmed in 14w28b as well.&lt;/p&gt;</comment>
                            <comment id="172373" author="jeuvke" created="Wed, 9 Jul 2014 22:26:16 +0200"  >&lt;p&gt;Confirmed for 14w28a.&lt;/p&gt;</comment>
                            <comment id="138231" author="skylinerw" created="Wed, 5 Feb 2014 20:13:14 +0100"  >&lt;p&gt;Confirmed for 14w05b and now 14w06a/b. Present in 14w07a/14w08a.&lt;/p&gt;</comment>
                            <comment id="130172" author="ezekielelin" created="Fri, 10 Jan 2014 13:56:43 +0100"  >&lt;p&gt;Reopened specifically for data tags. May be working as intended, however.&lt;/p&gt;</comment>
                            <comment id="130166" author="skylinerw" created="Fri, 10 Jan 2014 13:07:57 +0100"  >&lt;p&gt;@Ezekiel I can confirm that the Damage tag in this is fixed, but can also confirm that dataTags are still ignored.&lt;/p&gt;</comment>
                            <comment id="130164" author="ezekielelin" created="Fri, 10 Jan 2014 13:02:17 +0100"  >&lt;p&gt;Does the damage value still not matter?&lt;/p&gt;</comment>
                            <comment id="130154" author="wolfiemario" created="Fri, 10 Jan 2014 10:00:41 +0100"  >&lt;p&gt;This is &lt;em&gt;not&lt;/em&gt; actually fixed. Villagers will still ignore NBT tags. For example, you can trade the following villager ordinary bedrock instead of bedrock named &quot;CustomBedrock&quot;:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;/summon Villager ~ ~ ~ {Profession:1,Offers:{Recipes:[{buy:{id:7,tag:{display:{Name:CustomBedrock}},Count:2},sell:{id:1,Count:64}}]}}&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Confirmed for 14w02b; &lt;b&gt;can this please be reopened&lt;/b&gt;?&lt;/p&gt;</comment>
                            <comment id="129568" author="branza" created="Wed, 8 Jan 2014 17:31:48 +0100"  >&lt;p&gt;This has been fixed by Jeb: &lt;a href=&quot;https://twitter.com/jeb_/status/420896850879987712&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://twitter.com/jeb_/status/420896850879987712&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="126057" author="skylinerw" created="Sat, 21 Dec 2013 11:06:57 +0100"  >&lt;p&gt;Confirmed for 1.7.4&lt;/p&gt;</comment>
                            <comment id="114782" author="wolfiemario" created="Fri, 25 Oct 2013 09:06:53 +0200"  >&lt;p&gt;It&apos;s probably either the caveats, or Mojang being busy.&lt;/p&gt;

&lt;p&gt;Looking at the code, it wouldn&apos;t be complicated to fix: if you ignore the caveats, it&apos;s literally a change to one line (compare items by their existing equality method, rather than the equality of their IDs). My suggestion of adding an &quot;offer strictness&quot; tag to workaround those caveats would take a little more, but it wouldn&apos;t actually be complicated.&lt;/p&gt;

&lt;p&gt;I&apos;m guessing there&apos;s a chance this issue will be revisited once Mojang removes block metadata, as it will break the farmer&apos;s wool offer (as I mentioned a while back). I&apos;m interested in seeing if/how they will fix that.&lt;/p&gt;</comment>
                            <comment id="114775" author="taybosquee" created="Fri, 25 Oct 2013 07:33:11 +0200"  >&lt;p&gt;Today marks this issue&apos;s 1 year anniversary. Even though it has not been seen to yet, I&apos;m glad people have not forgot about it. Thank you mods and OP for keeping the issue up to date.&lt;br/&gt;
Just out of curiosity, what do people think is the biggest issue holding this up? Complicated coding, Mojang just being busy with bigger things, or the caveats Gerrard mentioned at the bottom of the original post?&lt;/p&gt;</comment>
                            <comment id="78827" author="taybosquee" created="Sat, 29 Jun 2013 23:38:37 +0200"  >&lt;p&gt;I think they just prioritize bug types (Which makes sense of course). Although this is a big issue with a lot of people, it&apos;s just not high on their to-do list. I just hope they find time for it eventually. :/&lt;/p&gt;</comment>
                            <comment id="78543" author="jespertheend" created="Sat, 29 Jun 2013 12:29:49 +0200"  >&lt;p&gt;yeah, for some reason some bugs take a looooongg time to fix&lt;/p&gt;</comment>
                            <comment id="78257" author="taybosquee" created="Fri, 28 Jun 2013 20:02:56 +0200"  >&lt;p&gt;I&apos;m glad I&apos;m not the only one having this problem. I tried making villagers trade items for custom items (Dmg values/Name/ect) for my adventure map and ran into this. My problem is not related to enchantments but it&apos;s caused by the same issue.&lt;br/&gt;
When I found out the villagers did not respect NBT tags, I thought &quot;No biggy. I&apos;ll just use bogus damage values to force them to only accept custom items.&quot; So when I try that, it fails also.&lt;br/&gt;
Hopefully Mojang gives us more of a answer then the villager did when I asked. All I got from him was &quot;Hmm.&quot; &lt;img class=&quot;emoticon&quot; src=&quot;https://bugs.mojang.com/images/icons/emoticons/wink.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;

&lt;p&gt;Edit: I just saw the post date for this bug... &lt;b&gt;Sigh&lt;/b&gt; Remember to up vote it or they&apos;ll never get to it at this rate. .-.&lt;/p&gt;</comment>
                            <comment id="67776" author="wolfiemario" created="Wed, 22 May 2013 01:31:39 +0200"  >&lt;p&gt;I agree with that; it should honestly be fixed - I suppose I should clarify that my last post was addressed to Marcono1234 (which is describing a different, seemingly unrelated bug which I&apos;ve yet to actually witness).&lt;/p&gt;</comment>
                            <comment id="67747" author="jespertheend" created="Tue, 21 May 2013 22:39:09 +0200"  >&lt;p&gt;I use an &lt;a href=&quot;http://www.minecraftforum.net/topic/1558668-152forgesspsmp-in-game-nbtedit-edit-nbt-tags-without-leaving-your-game-updated/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;NBTedit mod&lt;/a&gt; I created a trade where 2 different maps (with different damage values) are traded for another map (so map 1 + map 2 --&amp;gt; map 3) but it is still possible to put in map 1 twice and still get map 3. Without even gaining map 2.&lt;/p&gt;

&lt;p&gt;That&apos;s my problem but this can also be a problem for vanilla survival. For example it is very easy to repair tools now using the Priest.&lt;/p&gt;</comment>
                            <comment id="67741" author="wolfiemario" created="Tue, 21 May 2013 22:02:34 +0200"  >&lt;p&gt;I wouldn&apos;t say it&apos;s a bug for Minecraft to not interact correctly with MCedit, considering MCedit&apos;s a third-party tool. Does the same happen when creating a villager with &lt;em&gt;any&lt;/em&gt; tool? If so, that would imply something changed in the NBT format or the game isn&apos;t loading the villagers correctly - either case would also mean that bug applies to vanilla villagers, and if you have evidence of that, then file a report about it. I personally haven&apos;t noticed villagers reverting to &quot;1 Emerald for 8 Gold&quot;, although I haven&apos;t tested villagers on the snapshots - what version do you get this issue in?&lt;/p&gt;

&lt;p&gt;At any rate, how do you directly create a villager in MCedit? If you&apos;re importing a schematic, the villager will have the trades it has in that schematic - edit the NBT if you want something different. If the villager has no trades, vanilla will generate offers based on the villager&apos;s profession. If the profession is 5 (unused), the only offer that villager has is &lt;em&gt;8 gold ingots for 1 emerald&lt;/em&gt;, regardless of how many times you trade it. Vanilla has never had an offer of &quot;1 Emerald for 8 Gold&quot;, so if it&apos;s not MCedit&apos;s fault then it&apos;s a very strange bug indeed.&lt;/p&gt;</comment>
                            <comment id="67731" author="jespertheend" created="Tue, 21 May 2013 20:36:27 +0200"  >&lt;p&gt;hmm yeah that&apos;s weird&lt;/p&gt;</comment>
                            <comment id="67709" author="marcono1234" created="Tue, 21 May 2013 18:53:08 +0200"  >&lt;p&gt;There is also a bug: &lt;br/&gt;
If you create a villager with MCEdit, after some closing and opening from minecraft, he trades 1 Emerald for 8 Gold, and this is each time like this.&lt;/p&gt;</comment>
                            <comment id="53354" author="wolfiemario" created="Fri, 15 Mar 2013 02:04:35 +0100"  >&lt;p&gt;I&apos;d like to mention two things which worsen this bug:&lt;/p&gt;

&lt;p&gt;1. Anvils now allow you to abuse the enchantment offers like never before. The enchantment offer not only restores the durability - it also restores repair cost! At this point, you can buy something like Sharpness III on your 1-use-left dozen-times-repaired diamond sword, and use an anvil with a Sharpness III book to upgrade it to something respectable - at a very small fraction of the cost!&lt;/p&gt;

&lt;p&gt;2. On the Plugin API JIRA, Mojang&apos;s Grumm has revealed that Mojang plans to do away with block metadata altogether. This means each wool will have a different value - and thus, farmers will only buy white wool after this change. So, the main &lt;em&gt;good&lt;/em&gt; reason to have this bug will be removed in the future, leaving nothing but an exploitable bug and a headache to mapmakers.&lt;/p&gt;</comment>
                            <comment id="46583" author="jespertheend" created="Tue, 19 Feb 2013 19:20:41 +0100"  >&lt;p&gt;I&apos;ll go with &apos;only the green villager watches NBT data and damage values&apos; that&apos;s handy for mapmakers.&lt;/p&gt;</comment>
                            <comment id="46320" author="tyron" created="Sun, 17 Feb 2013 23:13:06 +0100"  >&lt;p&gt;That is a bad glitch in my opinion. You can forever repair your diamond tools at almost no cost. Enchanting damaged tools should at least retain the damage value.&lt;/p&gt;</comment>
                            <comment id="44460" author="jespertheend" created="Fri, 8 Feb 2013 08:21:25 +0100"  >&lt;p&gt;confirmed, NBT tags, I understand why villagers don&apos;t look at that.&lt;br/&gt;
Damage values too a bit, when we&apos;re talking about tools. Although when you make a custom villager, it would be handy to trade only with a certain map.&lt;/p&gt;</comment>
                            <comment id="12970" author="wolfiemario" created="Thu, 25 Oct 2012 06:56:08 +0200"  >&lt;p&gt;Yes, this is why I suggested the fix should only apply to priest&apos;s enchantments, and to whatever custom offers a map maker chooses to add the property to. I explicitly said that it would be an issue if farmers distinguished wool color &lt;img class=&quot;emoticon&quot; src=&quot;https://bugs.mojang.com/images/icons/emoticons/tongue.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                            <comment id="12955" author="cubethethird" created="Thu, 25 Oct 2012 06:44:53 +0200"  >&lt;p&gt;In terms of consistency, I agree that adding enchantments to items should not affect their durability. However, seeing as different colours of wool are not distinguished in terms of, say, crafting, it doesn&apos;t really make sense for villagers to make this distinction.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="24410">MC-10453</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="77591">MC-51637</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="88763">MC-61472</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="91380">MC-63968</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 11 Feb 2013 16:25:00 +0100</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10303"><![CDATA[Confirmed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_11700" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_11100" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Linked</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10900" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Pinned</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0mz1z:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>