<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 12:23:30 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-10174] 2 stacked droppers do not always send correctly</title>
                <link>https://bugs.mojang.com/browse/MC-10174</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;When sending an item through 2 hoppers and then into a dropper pointed up through another dropper with a chest on top (see attached screenshot), the item will always end up in one or the other, depending on how it is made.&lt;/p&gt;

&lt;p&gt;This will always happen one way or the other.  I built about 5 different setups exactly alike, and 2 of them always had the passed item stop in the top dropper, and the other times they always ended up in the chest.&lt;/p&gt;</description>
                <environment>Java V7 Update 11.  Windows XP, I3</environment>
        <key id="24047">MC-10174</key>
            <summary>2 stacked droppers do not always send correctly</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="3">Duplicate</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="noonga123">Mike Wheeler</reporter>
                        <labels>
                            <label>dropper</label>
                            <label>redstone</label>
                    </labels>
                <created>Sat, 23 Feb 2013 00:53:51 +0100</created>
                <updated>Thu, 15 Jun 2017 03:35:16 +0200</updated>
                            <resolved>Thu, 15 Jun 2017 03:27:41 +0200</resolved>
                                    <version>Snapshot 13w07a</version>
                    <version>Snapshot 13w09c</version>
                    <version>Snapshot 13w10a</version>
                    <version>Snapshot 13w10b</version>
                    <version>Minecraft 1.5</version>
                    <version>Minecraft 1.5.1</version>
                    <version>Minecraft 1.5.2</version>
                    <version>Snapshot 13w18c</version>
                    <version>Snapshot 13w19a</version>
                    <version>Minecraft 1.7.4</version>
                    <version>Minecraft 14w02c</version>
                    <version>Minecraft 14w03b</version>
                    <version>Minecraft 14w04a</version>
                    <version>Minecraft 14w04b</version>
                    <version>Minecraft 14w05a</version>
                    <version>Minecraft 14w05b</version>
                    <version>Minecraft 1.8</version>
                    <version>Minecraft 1.8.1</version>
                    <version>Minecraft 1.8.2-pre1</version>
                    <version>Minecraft 1.10.2</version>
                    <version>Minecraft 16w41a</version>
                    <version>Minecraft 16w42a</version>
                    <version>Minecraft 1.12</version>
                                                                        <votes>25</votes>
                                    <watches>7</watches>
                                                                            <comments>
                            <comment id="388819" author="zebulanstanphill@gmail.com" created="Thu, 15 Jun 2017 03:27:41 +0200"  >&lt;p&gt;Resolving as a duplicate in favor of &lt;a href=&quot;https://bugs.mojang.com/browse/MC-11193&quot; title=&quot;The order in which powerable blocks (e.g. redstone dust blocks) along a wire are powered or de-powered is not clearly defined and causes a non-deterministic behavior for redstone contraptions&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-11193&quot;&gt;MC-11193&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="387453" author="kingsupernova" created="Wed, 7 Jun 2017 23:33:15 +0200"  >&lt;p&gt;Pretty sure this is a dupe of &lt;a href=&quot;https://bugs.mojang.com/browse/MC-11193&quot; title=&quot;The order in which powerable blocks (e.g. redstone dust blocks) along a wire are powered or de-powered is not clearly defined and causes a non-deterministic behavior for redstone contraptions&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-11193&quot;&gt;MC-11193&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="336324" author="miwob" created="Fri, 21 Oct 2016 19:05:18 +0200"  >&lt;p&gt;Is this still an issue in the most recent versions (i.e. 1.10.2, or 16w42a) of Minecraft?&lt;/p&gt;</comment>
                            <comment id="221130" author="kingsupernova" created="Fri, 6 Mar 2015 08:12:19 +0100"  >&lt;p&gt;Dupe of &lt;a href=&quot;https://bugs.mojang.com/browse/MC-11193&quot; title=&quot;The order in which powerable blocks (e.g. redstone dust blocks) along a wire are powered or de-powered is not clearly defined and causes a non-deterministic behavior for redstone contraptions&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-11193&quot;&gt;MC-11193&lt;/a&gt;?&lt;/p&gt;</comment>
                            <comment id="150542" author="001bluecheetah" created="Fri, 11 Apr 2014 02:26:30 +0200"  >&lt;p&gt;I always thought that this bug was because redstone wire is unpredictable in the order that it updates blocks. This can be exemplified by having a line of droppers all being powered by the same line of redstone dust. How far an item goes down the line of droppers depends what order the redstone decides to update the droppers in. If it is intended for redstone to be slightly indeterminate, then this is not a bug, however I would argue that it is.&lt;/p&gt;</comment>
                            <comment id="116950" author="fullmontague" created="Fri, 1 Nov 2013 02:17:07 +0100"  >&lt;p&gt;I seem to have the same issue in 1.7.2 - though mine will generally go farther.&lt;/p&gt;

&lt;p&gt;My dropper column seems to drive/push items through ~19-20 transfers, but no farther.&lt;/p&gt;

&lt;p&gt;I took items out where they got stuck, and put them back a few droppers earlier, and they got stuck the same place - however! - when I inserted a new stack of material a few droppers farther along than my original &apos;start&apos; and the new stack got transfered that same number of transfers and stopped at a later point than the original stack stopped.&lt;/p&gt;

&lt;p&gt;I have dug out and verified the direction of all the droppers multiple times, as well as the redstone signal.&lt;/p&gt;

&lt;p&gt;(oh, and I&apos;ve also tried a bunch of different &apos;clock&apos; speeds of redstone pulse to drive the droppers, I&apos;m currently using a very slow one just to make sure that speed isn&apos;t causing this issue.)&lt;/p&gt;</comment>
                            <comment id="69733" author="bob anonymous" created="Thu, 30 May 2013 03:35:25 +0200"  >&lt;p&gt;This glitch sometimes occurs in horizontally placed droppers as well. Sometimes it will travel two blocks, sometimes one, or sometimes gets stuck...&lt;/p&gt;</comment>
                            <comment id="66649" author="enellgmz" created="Tue, 14 May 2013 13:12:53 +0200"  >&lt;p&gt;I am in 1.5.2 and this happened to me too. I don&apos;t know if it is exactly the same.&lt;/p&gt;

&lt;p&gt;I have 2 droppers facing up both and placed vertically attached to each other. Sometimes the down dropper will move the item to the top dropper but not always. Even if this is not the same as your&apos;s, even though I really do think it is, I am voting for a fix.&lt;/p&gt;</comment>
                            <comment id="56459" author="mt.andi" created="Sat, 23 Mar 2013 01:18:32 +0100"  >&lt;p&gt;Still exist in 1.5.1&lt;/p&gt;</comment>
                            <comment id="51585" author="mt.andi" created="Sun, 10 Mar 2013 15:01:16 +0100"  >&lt;p&gt;Update Affects Versions to 10b and pre-release. &lt;/p&gt;

&lt;p&gt;I thought the BUD nerf will do the job, but it fixed nothing. Why was the BUD ability removed then?&lt;/p&gt;</comment>
                            <comment id="49931" author="noonga123" created="Tue, 5 Mar 2013 09:20:56 +0100"  >&lt;p&gt;Yuki, that can&apos;t be it because none of the chests were ever even opened.&lt;/p&gt;</comment>
                            <comment id="49810" author="yuki-nagato" created="Tue, 5 Mar 2013 00:16:22 +0100"  >&lt;p&gt;I have determined the cause of the seemingly random behavior of this bug.  When a dispenser or dropper is powered, opening a normal chest causes that dropper or dispenser to update as if the normal chest was a trapped chest.  In this case, if you open the chest when the dropper is momentarily powered when it is transporting the very last item, it will cause that dispenser to update and thus transport the last item into the chest.  This is of course, not intentional and thus unless you knew what was happening, the times when you open that chest when the dispenser is unpowered would not trigger the dropper to transport the last item into the chest which is why a lot of you can not reproduce it and why it appears to be random at first glance. see &lt;a href=&quot;https://mojang.atlassian.net/browse/MC-10997&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://mojang.atlassian.net/browse/MC-10997&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="49519" author="mt.andi" created="Mon, 4 Mar 2013 07:39:44 +0100"  >&lt;p&gt;I think the problem came from dispensers that are too sensitive when powered. The droppers are so fast that they react at Redstone updates not like an instant update but like frequent block changes. Maybe adding 1 tick delay before item drop will fix the problem.&lt;/p&gt;

&lt;p&gt;Please add a picture from &lt;a href=&quot;https://mojang.atlassian.net/browse/MC-10667&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://mojang.atlassian.net/browse/MC-10667&lt;/a&gt; It is easier to reproduce and a bit different.&lt;br/&gt;
Or a picture from setup like here, that should be more realible &lt;a href=&quot;http://www.youtube.com/watch?v=E4FuwPPcpds&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://www.youtube.com/watch?v=E4FuwPPcpds&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="49515" author="noonga123" created="Mon, 4 Mar 2013 04:09:26 +0100"  >&lt;p&gt;Ah, I did not know that Tails, thanks!&lt;/p&gt;</comment>
                            <comment id="49360" author="mt.andi" created="Sun, 3 Mar 2013 15:12:43 +0100"  >&lt;p&gt;In the 13w09c still exist. &lt;/p&gt;</comment>
                            <comment id="48502" author="bljat" created="Fri, 1 Mar 2013 00:05:57 +0100"  >&lt;p&gt;You can update affected versions yourself. Just fyi &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;</comment>
                            <comment id="48499" author="noonga123" created="Fri, 1 Mar 2013 00:04:16 +0100"  >&lt;p&gt;Still happens with 13w09b as well.  Just fyi&lt;/p&gt;</comment>
                            <comment id="47172" author="noonga123" created="Sat, 23 Feb 2013 04:47:35 +0100"  >&lt;p&gt;Thanks for going that extra mile Tails, I appreciate it.  Strange, but it does happen.  It happens close to 50% of the time for me.  If I can assist in any way, let me know.&lt;/p&gt;

&lt;p&gt;Thanks!&lt;/p&gt;</comment>
                            <comment id="47165" author="bljat" created="Sat, 23 Feb 2013 03:12:21 +0100"  >&lt;p&gt;After building a couple more found one which did skip the top hopper. After messing around for an hour could still not find a reason why it does that, seems random. Confirmed anyways.&lt;/p&gt;</comment>
                            <comment id="47162" author="noonga123" created="Sat, 23 Feb 2013 02:19:53 +0100"  >&lt;p&gt;Third picture with open chest showing: Item ended up in chest, EVERY time.  Bug.&lt;/p&gt;</comment>
                            <comment id="47160" author="noonga123" created="Sat, 23 Feb 2013 02:15:24 +0100"  >&lt;p&gt;Just made another setup FAR away from any work I have done, and: Item ended up in chest.&lt;/p&gt;

&lt;p&gt;It is certainly random, and can easily be reproduced for me.  So not sure what else to tell you other than if that happens in the production update than I can never trust a dropper to do what it is designed to do.&lt;/p&gt;

&lt;p&gt;How else can I assist to show you this is messing up for me.&lt;/p&gt;</comment>
                            <comment id="47159" author="noonga123" created="Sat, 23 Feb 2013 02:09:41 +0100"  >&lt;p&gt;Adding another picture of 5 setups exactly alike. The redstone was NEVER active aside from each setup being used at the time.&lt;/p&gt;

&lt;p&gt;Starting with the left setup and dropping one item into each hopper:&lt;/p&gt;

&lt;p&gt;Setup1 from left: Item always ends up in top dropper.&lt;br/&gt;
Setup2 from left: Item always ends up in chest.&lt;br/&gt;
Setup3 from left: Item always ends up in top dropper.&lt;br/&gt;
Setup4 from left: Item always ends up in chest.&lt;br/&gt;
Setup5 from left: Item always ends up in chest.&lt;/p&gt;</comment>
                            <comment id="47157" author="noonga123" created="Sat, 23 Feb 2013 01:54:59 +0100"  >&lt;p&gt;I just built another 5 setups. 2 in dropper, 3 in chest.&lt;/p&gt;</comment>
                            <comment id="47156" author="bljat" created="Sat, 23 Feb 2013 01:44:52 +0100"  >&lt;p&gt;Unable to reproduce either. One item is always left in the top dropper.&lt;/p&gt;</comment>
                            <comment id="47151" author="noonga123" created="Sat, 23 Feb 2013 01:20:24 +0100"  >&lt;p&gt;All setups are exactly alike, there are no differences. I thought the rapid fire might be the issue, but it is a constant output depending on something.  I have no clue what it is.  If I knew how to make a movie of it I would show you, two exact builds per the screenshot, two different outputs.&lt;/p&gt;

&lt;p&gt;My guess is that it MIGHT be related to rapid fire, but if the trigger is going to be permanent random, for lack of a better phrase, then trying to move items UP through droppers will be a pain.&lt;/p&gt;</comment>
                            <comment id="47150" author="banana478" created="Sat, 23 Feb 2013 01:17:09 +0100"  >&lt;p&gt;The second dropper will only send items through when it receives a redstone update because it is not being powered directly. Once the last item goes through the bottom dropper, the top one won&apos;t keep getting updates. Are you sure that nothing around the second dropper would be updating it?&lt;/p&gt;</comment>
                            <comment id="47149" author="noonga123" created="Sat, 23 Feb 2013 01:14:53 +0100"  >&lt;p&gt;But it is not always staying in the second dropper.  On some it will go straight through the second dropper and into the chest, and will always do it.  I did see &lt;a href=&quot;https://bugs.mojang.com/browse/MC-846&quot; title=&quot;Dispenser and Dropper shooting out when updated&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-846&quot;&gt;&lt;del&gt;MC-846&lt;/del&gt;&lt;/a&gt;, this bug is nothing like that.&lt;/p&gt;</comment>
                            <comment id="47146" author="banana478" created="Sat, 23 Feb 2013 01:07:57 +0100"  >&lt;p&gt;I cannot reproduce. One item will always stay in the second dropper and the rest will go to the chest, which is expected behavior. See &lt;a href=&quot;https://bugs.mojang.com/browse/MC-846&quot; title=&quot;Dispenser and Dropper shooting out when updated&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-846&quot;&gt;&lt;del&gt;MC-846&lt;/del&gt;&lt;/a&gt; for an explanation.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="25303">MC-11193</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="22255" name="2013-02-22_16.47.29.png" size="545734" author="noonga123" created="Sat, 23 Feb 2013 00:53:51 +0100"/>
                            <attachment id="22261" name="2013-02-22_17.59.45 5 chests.png" size="323284" author="noonga123" created="Sat, 23 Feb 2013 02:09:51 +0100"/>
                            <attachment id="22262" name="2013-02-22_18.16.00 dropper bug.png" size="442864" author="noonga123" created="Sat, 23 Feb 2013 02:19:53 +0100"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Sat, 23 Feb 2013 03:12: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>6.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0lscn:</customfieldvalue>

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