<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 11:53:06 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-1040] Tools with unbreaking enchantment break, disappear from slot then reappear</title>
                <link>https://bugs.mojang.com/browse/MC-1040</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;What happened:&lt;br/&gt;
I was mining to the last of a diamond pick, it broke and I went to replace it with a new one. When I placed the new pick in the slot the old one reappeared and I was able to place it back in my bar. Sometimes I can use the pick, have it break, reappear and be reused several times before it breaks for good. As the pick breaks no breaking sound is heard.&lt;/p&gt;

&lt;p&gt;What I expected to happen:&lt;br/&gt;
My pickaxe breaks... The end...&lt;/p&gt;

&lt;p&gt;How to reproduce:&lt;br/&gt;
This seems very intermittent, there seems to be no link to anything. It&apos;s not every pick and I haven&apos;t noticed it on other items.&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;/give @p diamond_pickaxe 1 1561 {ench:[{id:34s,lvl:2s}]}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Code analysis: &lt;a href=&quot;https://bugs.mojang.com/browse/MC-1040?focusedCommentId=288014&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-288014&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://bugs.mojang.com/browse/MC-1040?focusedCommentId=288014&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-288014&lt;/a&gt;&lt;/p&gt;</description>
                <environment>Windows 64bit, up to date Java.</environment>
        <key id="12339">MC-1040</key>
            <summary>Tools with unbreaking enchantment break, disappear from slot then reappear</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="Excited">Maria Lem&#243;n</assignee>
                                    <reporter username="lurkinback">Darren Hiles</reporter>
                        <labels>
                    </labels>
                <created>Sun, 28 Oct 2012 16:00:46 +0100</created>
                <updated>Thu, 20 Oct 2016 14:51:57 +0200</updated>
                            <resolved>Thu, 20 Oct 2016 14:51:57 +0200</resolved>
                                    <version>Minecraft 1.4.2</version>
                    <version>Minecraft 1.4.5</version>
                    <version>Minecraft 1.4.6</version>
                    <version>Minecraft 1.4.7</version>
                    <version>Snapshot 13w04a</version>
                    <version>Minecraft 1.5</version>
                    <version>Snapshot 13w11a</version>
                    <version>Minecraft 1.5.1</version>
                    <version>Minecraft 1.5.2</version>
                    <version>Minecraft 1.6.1</version>
                    <version>Minecraft 1.6.2</version>
                    <version>Minecraft 13w39b</version>
                    <version>Minecraft 13w42b</version>
                    <version>Minecraft 13w43a</version>
                    <version>Minecraft 1.7.1</version>
                    <version>Minecraft 1.7.2</version>
                    <version>Minecraft 1.7.4</version>
                    <version>Minecraft 14w02b</version>
                    <version>Minecraft 14w02c</version>
                    <version>Minecraft 14w03b</version>
                    <version>Minecraft 14w04a</version>
                    <version>Minecraft 14w04b</version>
                    <version>Minecraft 14w06b</version>
                    <version>Minecraft 14w07a</version>
                    <version>Minecraft 14w08a</version>
                    <version>Minecraft 1.7.9</version>
                    <version>Minecraft 14w18b</version>
                    <version>Minecraft 1.7.10</version>
                    <version>Minecraft 14w34d</version>
                    <version>Minecraft 1.8</version>
                    <version>Minecraft 1.8.1-pre3</version>
                    <version>Minecraft 1.8.8</version>
                    <version>Minecraft 15w33b</version>
                    <version>Minecraft 15w47c</version>
                    <version>Minecraft 1.8.9</version>
                    <version>Minecraft 15w51b</version>
                    <version>Minecraft 16w02a</version>
                    <version>Minecraft 16w03a</version>
                    <version>Minecraft 1.9 Pre-Release 1</version>
                    <version>Minecraft 1.9</version>
                    <version>Minecraft 1.9.1 Pre-Release 3</version>
                    <version>Minecraft 1.9.2</version>
                    <version>Minecraft 1.9.3 Pre-Release 3</version>
                    <version>Minecraft 1.9.4</version>
                    <version>Minecraft 16w20a</version>
                    <version>Minecraft 16w21a</version>
                    <version>Minecraft 16w21b</version>
                    <version>Minecraft 1.10 Pre-Release 1</version>
                    <version>Minecraft 1.10 Pre-Release 2</version>
                    <version>Minecraft 1.10</version>
                    <version>Minecraft 1.10.1</version>
                    <version>Minecraft 1.10.2</version>
                    <version>Minecraft 16w32a</version>
                    <version>Minecraft 16w32b</version>
                    <version>Minecraft 16w33a</version>
                    <version>Minecraft 16w35a</version>
                                    <fixVersion>Minecraft 16w43a</fixVersion>
                                                        <votes>181</votes>
                                    <watches>22</watches>
                                                                            <comments>
                            <comment id="327167" author="farogaming" created="Sun, 28 Aug 2016 01:57:19 +0200"  >&lt;p&gt;Or it could just not make a different calculation of whether to break the tool or not client-side, but immediately ask for the one of the server.&lt;br/&gt;
Also please don&apos;t comment that you experienced the same bug, that&apos;s redundant. Exceptions are:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Confirmation status is &quot;Cannot reproduce&quot; or &quot;unconfirmed&quot; or&lt;/li&gt;
	&lt;li&gt;the version you tested it in is not in the affected versions list (and active, meaning that it&apos;s the latest release or a relatively new snapshot)&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="327165" author="echoblade" created="Sun, 28 Aug 2016 01:41:34 +0200"  >&lt;p&gt;I, too have experienced this bug. I was playing on a 1.10.2 server grinding cobblestone with an Unbreaking pick (I was using a book to hold down the mouse to mine) and whenever my pickaxe broke, I would wait a few seconds, and it would reappear with the durability I started mining with. I think this may have something to do with the fact that picks with Unbreaking do not get more durability. They still have the same amount of durability, but it doesn&apos;t decrease as often. This bug may be able to be fixed by adding more durability to a tool when it is enchanted with Unbreaking, or by adding a tag that only appears on tools with Unbreaking that tells the game how many more uses the tool has before it decreases its durability.&lt;/p&gt;</comment>
                            <comment id="321313" author="husky2490" created="Tue, 19 Jul 2016 03:43:20 +0200"  >&lt;p&gt;I doubt it&apos;s permanent&lt;/p&gt;</comment>
                            <comment id="320527" author="lordulster" created="Tue, 12 Jul 2016 04:11:19 +0200"  >&lt;p&gt;If you have space in your bag, and don&apos;t pick up any items that would fill the slot when the item breaks, you can press Q to drop the tool even if it &quot;breaks&quot; and it will very often drop the tool.  If immediately following the tool being broken you pick up an item that would fill the inventory space that that tool was in the tool will no longer exist.&lt;/p&gt;</comment>
                            <comment id="317451" author="farogaming" created="Sun, 26 Jun 2016 01:06:26 +0200"  >&lt;p&gt;That&apos;s not the same bug, that&apos;s just server lag. Let me guess: The blocks you mined also appeared again.&lt;/p&gt;</comment>
                            <comment id="317450" author="husky2490" created="Sun, 26 Jun 2016 00:28:07 +0200"  >&lt;p&gt;I&apos;ve had this happen on a notoriously laggy server (not in 1.10 nor was the server vanilla) while strip mining with unenchanted stone picks.  I would mine some blocks, they would disappear without dropping items and my pick would break.  I wait a few seconds (as it was normal on that server) and some of the blocks would return and I got my tool back.  It is also normal on that server to fall twice from the same point &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="316854" author="__null" created="Thu, 23 Jun 2016 18:09:05 +0200"  >&lt;p&gt;Confirmed for &lt;font color=&quot;#060&quot;&gt;&lt;b&gt;1.10.2&lt;/b&gt;&lt;/font&gt;.&lt;/p&gt;</comment>
                            <comment id="316054" author="__null" created="Wed, 22 Jun 2016 19:02:48 +0200"  >&lt;p&gt;Confirmed for &lt;font color=&quot;#060&quot;&gt;&lt;b&gt;1.10.1&lt;/b&gt;&lt;/font&gt;.&lt;/p&gt;</comment>
                            <comment id="311883" author="__null" created="Wed, 8 Jun 2016 23:36:49 +0200"  >&lt;p&gt;Confirmed for &lt;font color=&quot;#060&quot;&gt;&lt;b&gt;1.10&lt;/b&gt;&lt;/font&gt;.&lt;/p&gt;</comment>
                            <comment id="311439" author="__null" created="Wed, 8 Jun 2016 00:53:36 +0200"  >&lt;p&gt;Confirmed for &lt;font color=&quot;#060&quot;&gt;&lt;b&gt;1.10-pre2&lt;/b&gt;&lt;/font&gt;.&lt;/p&gt;</comment>
                            <comment id="309458" author="__null" created="Fri, 3 Jun 2016 03:42:39 +0200"  >&lt;p&gt;Confirmed for &lt;font color=&quot;#060&quot;&gt;&lt;b&gt;1.10-pre1&lt;/b&gt;&lt;/font&gt;.&lt;/p&gt;</comment>
                            <comment id="307777" author="__null" created="Fri, 27 May 2016 00:54:48 +0200"  >&lt;p&gt;Confirmed for &lt;font color=&quot;#060&quot;&gt;&lt;b&gt;16w21b&lt;/b&gt;&lt;/font&gt;.&lt;/p&gt;</comment>
                            <comment id="307456" author="__null" created="Thu, 26 May 2016 01:01:48 +0200"  >&lt;p&gt;Confirmed for &lt;font color=&quot;#060&quot;&gt;&lt;b&gt;16w21a&lt;/b&gt;&lt;/font&gt;.&lt;/p&gt;</comment>
                            <comment id="305379" author="__null" created="Wed, 18 May 2016 23:59:27 +0200"  >&lt;p&gt;Confirmed for &lt;b&gt;16w20a&lt;/b&gt;.&lt;/p&gt;</comment>
                            <comment id="304179" author="__null" created="Thu, 12 May 2016 01:04:09 +0200"  >&lt;p&gt;Confirmed for &lt;b&gt;1.9.4&lt;/b&gt;.&lt;/p&gt;</comment>
                            <comment id="303229" author="__null" created="Fri, 6 May 2016 01:57:21 +0200"  >&lt;p&gt;Confirmed for &lt;b&gt;1.9.3-pre3&lt;/b&gt;.&lt;/p&gt;</comment>
                            <comment id="294969" author="james549" created="Wed, 16 Mar 2016 00:22:10 +0100"  >&lt;p&gt;Confirmed for &lt;b&gt;1.9.1-pre3&lt;/b&gt;.&lt;/p&gt;</comment>
                            <comment id="288015" author="marcono1234" created="Sat, 20 Feb 2016 13:17:31 +0100"  >&lt;p&gt;Please add this example command to the description:&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;/give @p diamond_pickaxe 1 1561 {ench:[{id:34s,lvl:2s}]}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="288014" author="marcono1234" created="Sat, 20 Feb 2016 13:17:04 +0100"  >&lt;p&gt;Please link to this comment in the description of the report.&lt;/p&gt;

&lt;p&gt;The following is based on decompiled version of Minecraft 1.8 using MCP. All method and class names are the names used in the decompiled version.&lt;/p&gt;

&lt;p&gt;The reason why this happens it that the method &lt;tt&gt;public boolean attemptDamageItem(int amount, Random rand)&lt;/tt&gt; of the &lt;tt&gt;net.minecraft.item.ItemStack&lt;/tt&gt; class runs for the client and the server. This method tries to damage an item and returns &lt;tt&gt;true&lt;/tt&gt; if the item broke. The problem is that Unbreaking is random, the higher the enchantment, the higher the chance that the item does not break. As it is random it is very likely that the client and the server get different results, for example the client thinks the item broke already whereas for the server the item is still there (this is described in this report).&lt;br/&gt;
This method should be only called from the server which needs to send then the according package and send that the client should display the breaking particles.&lt;/p&gt;</comment>
                            <comment id="286717" author="immaterialise" created="Wed, 17 Feb 2016 18:31:28 +0100"  >&lt;p&gt;Confirmed for 1.9-pre1&lt;/p&gt;</comment>
                            <comment id="282832" author="cowtip" created="Wed, 3 Feb 2016 23:32:11 +0100"  >&lt;p&gt;I am running 1.8.9 Vanilla. I was playing on single-player survival. I have a stone axe with Efficiency IV, Fortune III and Unbreaking III. I used it a few times and saw the durability bar appear. A short while later I noticed the durability bar had disappeared indicating the axe had full durability again. You probably would not notice small changes in durability while the bar is in the middle of its range. But it is obvious when a tool is resurrected or when the bar disappears. Based on these reports, the game seems to randomly update durability for Unbreaking tools. I don&apos;t think this is a special case just for destroyed tools. I know that there are background checks that randomly update blocks. What routine can destroy a tool? And are there any background routines that affect tools? In my experience, there is always a random delay before the durability is increased. &lt;/p&gt;</comment>
                            <comment id="280139" author="pascallj" created="Tue, 26 Jan 2016 20:53:48 +0100"  >&lt;p&gt;Confirmed for &lt;b&gt;16w03a&lt;/b&gt;.&lt;/p&gt;</comment>
                            <comment id="277852" author="james549" created="Wed, 13 Jan 2016 23:56:43 +0100"  >&lt;p&gt;Confirmed for &lt;b&gt;16w02a&lt;/b&gt;.&lt;/p&gt;</comment>
                            <comment id="274321" author="james549" created="Wed, 23 Dec 2015 23:47:01 +0100"  >&lt;p&gt;Confirmed for &lt;b&gt;1.8.8&lt;/b&gt; and &lt;b&gt;15w51b&lt;/b&gt;. &lt;a href=&quot;https://youtu.be/m5gpY0gyqRY&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Here&lt;/a&gt;&apos;s a video demonstrating it.&lt;/p&gt;</comment>
                            <comment id="267871" author="wisely" created="Tue, 24 Nov 2015 14:58:09 +0100"  >&lt;p&gt;Confirmed for 15w47c!&lt;br/&gt;
Just happend yesterday to me on a diamond shovel.&lt;/p&gt;</comment>
                            <comment id="242643" author="fenhl" created="Fri, 14 Aug 2015 14:19:38 +0200"  >&lt;p&gt;&lt;b&gt;Affects 15w33b&lt;/b&gt;, and perhaps the summary and/or description should be updated to include at least some mention of the Unbreaking enchantment?&lt;/p&gt;</comment>
                            <comment id="239711" author="wingsandgills" created="Mon, 3 Aug 2015 14:41:10 +0200"  >&lt;p&gt;Confirmed in 1.8.7 with a player connected by LAN to my game, his enchanted picks break and then reappear when he tries to replace it in hotbar. (The &quot;replacement&quot; falls on the ground and the &quot;broken&quot; pick reappears in hotbar.) He can do this several times before it truly breaks.&lt;/p&gt;</comment>
                            <comment id="208280" author="lurkinback" created="Sat, 8 Nov 2014 17:44:43 +0100"  >&lt;p&gt;Also F3+H(PC) works way more effectively at preventing you from going through a pick/tool you don&apos;t want to lose rather than hoping on a random bug to occur.&lt;/p&gt;</comment>
                            <comment id="208261" author="williewillus" created="Sat, 8 Nov 2014 16:46:33 +0100"  >&lt;p&gt;No this isn&apos;t an &quot;undocumented feature&quot;&lt;br/&gt;
The bug is that the item is breaking visually when it&apos;s not supposed to.&lt;br/&gt;
The client should always reflect the server accurately so this is a bug.&lt;/p&gt;</comment>
                            <comment id="208163" author="smashedagainst" created="Fri, 7 Nov 2014 22:26:13 +0100"  >&lt;p&gt;I actually kind of like this &quot;undocumented feature&quot; as I can safely use my more enchanted tools without worry of actually killing them. It took a lot of experience and two anvils to make my diamond pickaxe get efficiency IV unbreaking III. &lt;img class=&quot;emoticon&quot; src=&quot;https://bugs.mojang.com/images/icons/emoticons/biggrin.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="200557" author="connah0047" created="Thu, 18 Sep 2014 19:35:01 +0200"  >&lt;p&gt;This happened to me in Minecraft 1.8 in single player survival. I had an iron pickaxe with Efficiency IV and Unbreaking III. When it ran out on the last block I was mining, the pickaxe made the breaking sound and disappeared like normal. I opened my inventory and moved a diamond pickaxe into the slot the enchanted iron pickaxe used to be in. When I did, the enchanted iron pickaxe suddenly reappeared and was thrown to the ground. I exited my inventory and picked it up off the ground. I was able to use it a few more times before it made the breaking sound again, broke for good and disappeared permanently. See attachments. Image &quot;&lt;a href=&quot;https://bugs.mojang.com/browse/MC-1040&quot; title=&quot;Tools with unbreaking enchantment break, disappear from slot then reappear&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-1040&quot;&gt;&lt;del&gt;MC-1040&lt;/del&gt;&lt;/a&gt;_1.png&quot; shows the enchanted iron pickaxe suddenly being thrown to the ground after the actions described above. Image &quot;&lt;a href=&quot;https://bugs.mojang.com/browse/MC-1040&quot; title=&quot;Tools with unbreaking enchantment break, disappear from slot then reappear&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-1040&quot;&gt;&lt;del&gt;MC-1040&lt;/del&gt;&lt;/a&gt;_2.png&quot; shows it back in my hotbar after I picked it back up off the ground.&lt;/p&gt;</comment>
                            <comment id="191799" author="amethystzhou" created="Thu, 21 Aug 2014 10:46:14 +0200"  >&lt;p&gt;Confirm in 14w34d, pickaxe and axe re-appear after broken. Not sure if it has anything to do with the Unbreaking enchantment though.&lt;/p&gt;</comment>
                            <comment id="178046" author="antofthy" created="Wed, 23 Jul 2014 05:53:47 +0200"  >&lt;p&gt;Perhaps a solution is to have unbreaking enchant not work for the last use or last few uses.&lt;/p&gt;

&lt;p&gt;That is when a pick only has one use left, it always breaks, regardless of unbreaking enchant.  That way randomness caused by server-client sync does not play a part.&lt;/p&gt;

&lt;p&gt;As this may happen quickly perhaps the last 5 or 10 uses of a tool does not allow unbreaking, so as to ensure client-servers are in sync in a tools last moments of life.&lt;/p&gt;</comment>
                            <comment id="171127" author="wpalmer" created="Sun, 6 Jul 2014 00:44:14 +0200"  >&lt;p&gt;I think part of the same issue: placing a new, undamaged tool, in the same hotbar slot as a recently-broken tool, can sometimes cause the &lt;b&gt;new&lt;/b&gt; tool to disappear&lt;/p&gt;</comment>
                            <comment id="164277" author="jonathan.hynes" created="Wed, 18 Jun 2014 20:00:18 +0200"  >&lt;p&gt;I&apos;ll mention 1.7.9 just because it&apos;s not listed yet in the Versions Affected.&lt;/p&gt;</comment>
                            <comment id="161799" author="williewillus" created="Fri, 6 Jun 2014 04:27:49 +0200"  >&lt;p&gt;Simple solution is to only damage tools on the serverside. This unfortunately gives the aesthetic glitch of not having the tool break apart animation.&lt;/p&gt;</comment>
                            <comment id="154817" author="whilyam" created="Fri, 2 May 2014 17:10:12 +0200"  >&lt;p&gt;This remains an issue in the newest snapshot.&lt;/p&gt;</comment>
                            <comment id="141769" author="whilyam" created="Thu, 20 Feb 2014 00:11:26 +0100"  >&lt;p&gt;This is indeed because of Unbreaking. Tested multiple times. Only Unbreaking tools come back from the dead. It seems that tools that have one use left break before the game calculates if the use counts or is absorbed by the Unbreaking enchantment.&lt;/p&gt;</comment>
                            <comment id="140309" author="garyclosse" created="Fri, 14 Feb 2014 21:14:27 +0100"  >&lt;p&gt;Still affects 14w07a&lt;/p&gt;</comment>
                            <comment id="131993" author="lurkinback" created="Thu, 16 Jan 2014 14:56:14 +0100"  >&lt;p&gt;It&apos;s been a while since I experienced this but from what I remember it was always with the Unbreaking enchantment on. To me that suggests a calculation of amount of durability left before calculation of unbreaking effect.&lt;/p&gt;

&lt;p&gt;I.e. Pickaxe has 1 durability left.&lt;br/&gt;
I use that 1 durability and pick breaks&lt;br/&gt;
Unbreaking effect is then calculated, and says nope it didn&apos;t break.&lt;/p&gt;

&lt;p&gt;Not saying thats a conclusive answer or anything lol&lt;/p&gt;</comment>
                            <comment id="131989" author="galaxy_2alex" created="Thu, 16 Jan 2014 14:18:00 +0100"  >&lt;p&gt;Darren Hills: It should only have a problem in Singleplayer with Pickaxes with Unbreaking on them. Do you also experince this issue without Unbreaking being on the Pickaxe?&lt;/p&gt;</comment>
                            <comment id="131981" author="lurkinback" created="Thu, 16 Jan 2014 13:30:13 +0100"  >&lt;p&gt;If it was just a server lag problem I would have thought it would not exist in Single Player as well?&lt;/p&gt;</comment>
                            <comment id="131974" author="nekojonez" created="Thu, 16 Jan 2014 11:49:57 +0100"  >&lt;p&gt;Honestly, I think server lag might be involved. Maybe the game thinks you still have some uses left while the server says no? Or am I understanding MC&apos;s logic wrong? &lt;/p&gt;</comment>
                            <comment id="131973" author="galaxy_2alex" created="Thu, 16 Jan 2014 11:48:21 +0100"  >&lt;p&gt;So, to summarize it:&lt;br/&gt;
It can be caused by server lag and/or the Unbreaking enchantment.&lt;br/&gt;
I can confirm the part with the Unbreaking enchantment, not the one with the server lag though.&lt;/p&gt;</comment>
                            <comment id="131971" author="nekojonez" created="Thu, 16 Jan 2014 11:41:09 +0100"  >&lt;p&gt;I&apos;m playing on a 1.7.4 server, and this is still the case.  Mostly when I have an unbreaking pickaxe. I click on the slot with another tool and it&apos;s back for 2-3 uses. &lt;/p&gt;</comment>
                            <comment id="116113" author="emoluvjd2" created="Mon, 28 Oct 2013 01:53:13 +0100"  >&lt;p&gt;This used to happen to me on servers way back in beta 1.2, but I did have it happen somewhat recently with enchanted tools.&lt;/p&gt;</comment>
                            <comment id="110931" author="rancore202" created="Sat, 12 Oct 2013 04:25:31 +0200"  >&lt;p&gt;I should think it would be easiest to take away the job of determining when a tool is broken from the client. Only the server/internal server should track the tool&apos;s status. (Not really sure why the client does it anyway, after release 1.3)&lt;br/&gt;
(There are probably two bugs present here, my proposal should fix at least one of them.)&lt;/p&gt;</comment>
                            <comment id="107259" author="galaxy_2alex" created="Sat, 28 Sep 2013 15:44:35 +0200"  >&lt;p&gt;Not only servers, but what I&apos;m experiencing is maybe another bug.&lt;br/&gt;
What I can confirm is that at the end of a life of a tool with Unbreaking on it, the pickaxe sometimes behaves very strange (especially with higher levels of Unbreaking).&lt;/p&gt;</comment>
                            <comment id="107248" author="marcono1234" created="Sat, 28 Sep 2013 14:08:20 +0200"  >&lt;p&gt;This is often in muliplayer when it lags:&lt;br/&gt;
You break a block, but the server doesn&apos;t answer but your client version already subtract one health point of your tool. When the lag is away the client and the server synchronise and you get the tool back &lt;/p&gt;

&lt;p&gt;I suppose it is like this&lt;/p&gt;</comment>
                            <comment id="89597" author="mightypork" created="Fri, 12 Jul 2013 02:25:35 +0200"  >&lt;p&gt;@Th3F4114n0n3 I&apos;ve had this regularly happening with plain stone swords, so I conclude the enchantment is not the (only) cause.&lt;/p&gt;</comment>
                            <comment id="84477" author="_zombiehunter" created="Sat, 6 Jul 2013 19:22:36 +0200"  >&lt;p&gt;Just had this problem in SMP (1.6.2), would anyone be so kind and update the &quot;affects versions&quot; ?&lt;/p&gt;</comment>
                            <comment id="75360" author="jeepguy42" created="Wed, 19 Jun 2013 18:23:45 +0200"  >&lt;p&gt;It has to do with the formula they use to determine how much the tools durability goes up due to the enchantment level.. it can result that when the tool breaks the enchanment deletes first by mistake and then you get a negative durability... because negative durability cant exist is change the negative number into a positive (i.e. -15 becomes 15) making it restore in your inventory.&lt;/p&gt;</comment>
                            <comment id="69830" author="mattbasta" created="Thu, 30 May 2013 17:33:19 +0200"  >&lt;p&gt;This seems to happen with unbreaking tools when the tool would otherwise break (i.e.: it has a single unit of durability remaining), but the unbreaking subsequently re-adds the use to the tool. The client doesn&apos;t know that the server might un-break the tool, so it subtracts one durability, makes the tool break, then the server responds, &quot;Oh no, it&apos;s fine don&apos;t worry about it, it&apos;s still got a use left.&quot;&lt;/p&gt;</comment>
                            <comment id="66668" author="rebane2001" created="Tue, 14 May 2013 16:49:27 +0200"  >&lt;p&gt;If i use something to freecam in server and then break blocks, client will show that pickaxe is used!&lt;/p&gt;</comment>
                            <comment id="43037" author="dotzo" created="Sun, 3 Feb 2013 07:00:06 +0100"  >&lt;p&gt;I just had this happen to me on 13w05b on an Unbreaking I Iron Shovel, so it has yet to be fixed.&lt;/p&gt;</comment>
                            <comment id="42482" author="shufboyardee" created="Fri, 1 Feb 2013 20:24:24 +0100"  >&lt;p&gt;What you say makes sense, Marios.  It sounds like a case of client-server sync issues.&lt;/p&gt;</comment>
                            <comment id="42479" author="purple" created="Fri, 1 Feb 2013 19:57:40 +0100"  >&lt;p&gt;If the durability drops to 0 don&apos;t use it again because it is unpredictable whether it is going to break, not just because of the bug but because of the unbreaking enchantment. As I mentioned before, because of the bug the durability meter is not reliable. In order to make it refresh and show the real value what I do is pick up the tool and place again in the inventory. The durability meter will then refresh and show the actual value. I&apos;m sure this behavior is connected with the breaking and reappearance of the tool and both are connected with this bug on unbreaking enchantment.&lt;/p&gt;</comment>
                            <comment id="42435" author="shufboyardee" created="Fri, 1 Feb 2013 17:41:02 +0100"  >&lt;p&gt;Will, I tried doing that, and I&apos;m finding that &apos;actually breaking&apos; is a hard thing to predict with an Unbreaking tool.  On an unenchanted tool, you could accurately say that a durability of 0 means that the next use will break the tool.  But an Unbreaking tool can remain at 0 for several uses.  To directly answer your suggestion, the glitchy breaks as well as the real breaks all occur when durability is 0.  Maybe though, I misunderstand what you might mean by &apos;actually breaking&apos;?&lt;/p&gt;</comment>
                            <comment id="40842" author="willco2" created="Tue, 29 Jan 2013 04:07:52 +0100"  >&lt;p&gt;To see if it is actually breaking, someone might want to press F3 + H to get the durability shown.&lt;/p&gt;</comment>
                            <comment id="40737" author="shufboyardee" created="Mon, 28 Jan 2013 19:20:16 +0100"  >&lt;p&gt;This happened to me just now in 1.4.7 with an Unbreaking III pickaxe.&lt;/p&gt;</comment>
                            <comment id="40719" author="thehungrycamel24" created="Mon, 28 Jan 2013 18:27:21 +0100"  >&lt;p&gt;This happens for me in singleplayer and multiplayer when using any tool that has an Unbreaking enchantment on it. &lt;/p&gt;</comment>
                            <comment id="36963" author="purple" created="Tue, 15 Jan 2013 15:11:26 +0100"  >&lt;p&gt;I agree about the unbreaking enchantment but I&apos;m playing SSP so I confirm it in SSP 1.4.7 too.&lt;/p&gt;</comment>
                            <comment id="36744" author="thecorykid" created="Mon, 14 Jan 2013 16:33:13 +0100"  >&lt;p&gt;I&apos;ve only ever had this happen when using an unbreaking-enchanted pickaxe in multiplayer. So I assume (as others have said) that it&apos;s related to these two things.&lt;/p&gt;</comment>
                            <comment id="36706" author="purple" created="Mon, 14 Jan 2013 13:34:19 +0100"  >&lt;p&gt;Affects 1.4.7 too. Also the durability meter changes without using the tool.&lt;/p&gt;</comment>
                            <comment id="26817" author="demonstar502" created="Thu, 6 Dec 2012 18:16:24 +0100"  >&lt;p&gt;I host a server and play almost exclusively SMP as a result, and it seems like this is a bug related to the Unbreaking enchantment. From what I can tell, the client and server are having a disconnect somewhere, causing the client to say that the item &quot;Broke&quot; and remove it from your inventory temporarily, until the server corrects it and gives you the item back.&lt;/p&gt;</comment>
                            <comment id="15888" author="lurkinback" created="Wed, 31 Oct 2012 15:57:44 +0100"  >&lt;p&gt;Yeh I won&apos;t complain about getting full use out of it. If I try really hard I almost convince myself that I&apos;m getting more than I should lol&lt;/p&gt;

&lt;p&gt;The only reason I&apos;m saying anything is just the annoyance of having to do a pile of clicking when the game should remember what&apos;s left durability wise. =)&lt;/p&gt;</comment>
                            <comment id="15650" author="claycorp" created="Wed, 31 Oct 2012 00:09:39 +0100"  >&lt;p&gt;Its just lag or your digging really fast so it counts one block too many times ignore it its going to happen and at least your not losing uses you did not use.&lt;/p&gt;</comment>
                            <comment id="14946" author="lurkinback" created="Mon, 29 Oct 2012 11:44:01 +0100"  >&lt;p&gt;It&apos;s on single player I&apos;ve noticed it but I don&apos;t play a great deal on smp so it may occur but I haven&apos;t seen it. I&apos;m a fairly new player so I don&apos;t have much idea of what&apos;s old and new. It&apos;s more an annoyance by the old reporting system.&lt;/p&gt;</comment>
                            <comment id="14865" author="kumasasa" created="Mon, 29 Oct 2012 00:23:53 +0100"  >&lt;p&gt;Old bug, occuring also on vanilla servers&lt;/p&gt;</comment>
                            <comment id="14861" author="chalmes" created="Mon, 29 Oct 2012 00:12:41 +0100"  >&lt;p&gt;Is this singleplayer or SMP?&lt;/p&gt;

&lt;p&gt;I used to get this all the time when playing on a Bukkit server, but i&apos;ve not seen it since playing on vanilla.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="17961">MC-5361</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="21305">MC-8384</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="24536">MC-10573</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="24613">MC-10641</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="31854">MC-16046</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="32694">MC-16781</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="32841">MC-16916</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="37273">MC-18804</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="46326">MC-26700</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="57013">MC-35278</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="58473">MC-36375</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="62789">MC-40329</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="70035">MC-44839</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="73824">MC-48145</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="74436">MC-48714</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="76020">MC-50188</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80831">MC-54523</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="87884">MC-60616</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="97130">MC-69506</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="127375">MC-93144</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="137942">MC-99880</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="141455">MC-102471</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="146206">MC-105148</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="15776">MC-3652</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="16592">MC-4163</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10103">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="16244">MC-3960</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="83395" name="MC-1040_1.png" size="2112943" author="connah0047" created="Thu, 18 Sep 2014 19:35:18 +0200"/>
                            <attachment id="83396" name="MC-1040_2.png" size="1135443" author="connah0047" created="Thu, 18 Sep 2014 19:35:18 +0200"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 16 Jan 2014 11:48: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_10501" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Game Mode</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10304"><![CDATA[Survival]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_11100" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Linked</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0mz87:</customfieldvalue>

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