<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 12:21:50 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-9661] Custom mob loot ignores set durability.</title>
                <link>https://bugs.mojang.com/browse/MC-9661</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;Using customized mob spawners, you were allowed to give mobs customized equipment with all of the normal information, including damage values. In this most recent version, durability seems to be bugged &amp;#8211; regardless of what value I set for the damage, it seems to want to drop items with 25 durability remaining, with a rare variance. It &lt;b&gt;never&lt;/b&gt; has the damage amount set in the NBT data of the spawner itself, however (well, maybe if I set it to leave 25 durability remaining).&lt;/p&gt;

&lt;p&gt;For those who wish to test this themselves, you may use these two schematics (spawners, requires MCEdit) &amp;#8211; you may also check the NBT tags in NBTedit for confirmation that there is definitely some sort of buggy behavior going on.&lt;/p&gt;</description>
                <environment>Windows 7, Java version 6.0.290</environment>
        <key id="23384">MC-9661</key>
            <summary>Custom mob loot ignores set durability.</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="4">Incomplete</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="ix10510ix">Novi Bliss</reporter>
                        <labels>
                    </labels>
                <created>Tue, 12 Feb 2013 09:52:01 +0100</created>
                <updated>Thu, 17 Mar 2016 16:56:15 +0100</updated>
                            <resolved>Thu, 17 Mar 2016 16:56:15 +0100</resolved>
                                    <version>Snapshot 13w06a</version>
                    <version>Snapshot 13w07a</version>
                    <version>Minecraft 1.5</version>
                    <version>Minecraft 1.5.1</version>
                    <version>Minecraft 14w17a</version>
                                                                        <votes>3</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="295215" author="JIRAUSER71590" created="Thu, 17 Mar 2016 16:56:15 +0100"  >&lt;p&gt;1. No response for over a year.&lt;br/&gt;
2. most likely intended, drop chance =&amp;lt; 1.0 random damage drop chance &amp;gt; 1.0 set damage value&lt;/p&gt;</comment>
                            <comment id="205277" author="galaxy_2alex" created="Sat, 25 Oct 2014 13:02:39 +0200"  >&lt;p&gt;Is this still a concern in the &lt;em&gt;current Minecraft version&lt;/em&gt; &lt;b&gt;1.8.1 Prerelease 3&lt;/b&gt; / Launcher version &lt;b&gt;1.5.3&lt;/b&gt; or later? If so, please &lt;em&gt;update the affected versions&lt;/em&gt; in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.&lt;/p&gt;</comment>
                            <comment id="156666" author="JIRAUSER71590" created="Fri, 9 May 2014 12:49:55 +0200"  >&lt;p&gt;confirmed&lt;/p&gt;</comment>
                            <comment id="152182" author="escorefairplay" created="Thu, 24 Apr 2014 17:18:48 +0200"  >&lt;p&gt;Having the problem now in minecraft 14w11b&lt;/p&gt;</comment>
                            <comment id="55746" author="ix10510ix" created="Wed, 20 Mar 2013 05:42:03 +0100"  >&lt;p&gt;Yes, I&apos;ve tested and it is still the case that set damage values on weapons and armor are ignored in 1.5. I will update it now, thank you.&lt;/p&gt;</comment>
                            <comment id="45401" author="ix10510ix" created="Tue, 12 Feb 2013 10:01:57 +0100"  >&lt;p&gt;Sorry, I&apos;m new to this and wasn&apos;t aware of the built-in attachment system. Now you don&apos;t have to go through an external website!&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="79588">MC-53368</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="21664" name="twoschematics.zip" size="2325" author="ix10510ix" created="Tue, 12 Feb 2013 10:01:57 +0100"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Fri, 9 May 2014 23:14:00 +0200</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10302"><![CDATA[Community Consensus]]></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_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0m587:</customfieldvalue>

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