<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 12:10:17 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-6162] Unexpected behavior with stacked hoppers and chests</title>
                <link>https://bugs.mojang.com/browse/MC-6162</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;Perhaps not a bug.  I&apos;ll let you be the judge.  (Sorry for the wall of text.)&lt;/p&gt;

&lt;p&gt;The attached screenshots tell a bit of a story.  The first shows the front of a simple sorting system built with chests and hoppers (in the back).  Items are put into the top hopper (perhaps by water stream).  Shot #2 shows that inside each chest is at least one of each item (as labeled) so only that items gets put into that chest.  Shot #3 shows the back, including a fourth hopper at the bottom to catch anything that doesn&apos;t fit into the chests.&lt;/p&gt;

&lt;p&gt;Now, the behavior I would expect goes like this: Seeds, wheat, and eggs would get into the top hopper.  After a time all of the seeds would be in the top chest, all of the wheat would be in the middle chest, etc.  Anything not seeds, wheat, or eggs would end up in the bottom-most hopper.&lt;/p&gt;

&lt;p&gt;What actually happens is the top hopper tries to put seeds into the top chest, and sometimes succeeds.  But, the second hopper starts pulling items out of the top hopper, so they start competing to grab items.  Some seeds get into the chest as intended, but some get passed down the system with nowhere to fit and end up at the bottom hopper.  The same is true for the wheat and the eggs.  Shot #4 shows the contents of the bottom hopper, containing items that should be in chests higher up.&lt;/p&gt;</description>
                <environment></environment>
        <key id="18823">MC-6162</key>
            <summary>Unexpected behavior with stacked hoppers and chests</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="6">Works As Intended</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="rocketturtle">Rocket Turtle</reporter>
                        <labels>
                            <label>chest</label>
                            <label>hopper</label>
                    </labels>
                <created>Sat, 5 Jan 2013 03:33:03 +0100</created>
                <updated>Sat, 8 Jun 2024 15:19:15 +0200</updated>
                            <resolved>Mon, 21 Oct 2013 13:26:54 +0200</resolved>
                                    <version>Snapshot 13w01b</version>
                    <version>Snapshot 13w02a</version>
                    <version>Snapshot 13w02b</version>
                    <version>Snapshot 13w03a</version>
                    <version>Snapshot 13w04a</version>
                    <version>Snapshot 13w05a</version>
                    <version>Snapshot 13w05b</version>
                    <version>Snapshot 13w06a</version>
                    <version>Snapshot 13w07a</version>
                    <version>Snapshot 13w09a</version>
                    <version>Snapshot 13w09b</version>
                    <version>Snapshot 13w09c</version>
                    <version>Snapshot 13w10a</version>
                    <version>Minecraft 1.5</version>
                                                                        <votes>37</votes>
                                    <watches>8</watches>
                                                                            <comments>
                            <comment id="189985" author="neurospex" created="Mon, 18 Aug 2014 02:04:31 +0200"  >&lt;p&gt;@Phil71994 Please don&apos;t make duplicate reports.&lt;/p&gt;

&lt;p&gt;Having done more thinking on this issue, here is what I propose:&lt;br/&gt;
If a hopper points into anything other than a hopper, then if the object it points in to can accept items, that should take priority over a hopper below that hopper. If a hopper points into another hopper, than the hopper below the original hopper should take priority over the direction the original hopper is pointing. This allows all old contraptions to still work while making new contraptions allow for storage item sorting.&lt;/p&gt;</comment>
                            <comment id="149412" author="neurospex" created="Mon, 31 Mar 2014 03:50:10 +0200"  >&lt;p&gt;This seems to be broken again. I if I make a vertical stack of chests and point hoppers into them, items which go into the top hopper will either all end up in the bottom chest, or half in the top and half in the bottom. Any middle chests will be skipped for some reason.&lt;/p&gt;

&lt;p&gt;It should be desired that if a hopper is pointing in to a chest or another hopper, that should take priority. Items should be fed from the hopper into the desired destination with a higher priority than another hopper trying to pull from that hopper by being below it.&lt;/p&gt;

&lt;p&gt;A player shows intention with a hopper by directing it at a destination. This should be higher priority than placing a hopper below another, with the upper hopper /not/ pointing directly at the lower hopper.&lt;/p&gt;</comment>
                            <comment id="56636" author="matrixhacker" created="Sat, 23 Mar 2013 19:23:55 +0100"  >&lt;p&gt;May be related to &lt;a href=&quot;https://bugs.mojang.com/browse/MC-8457&quot; title=&quot;Chest sometimes doesn&amp;#39;t activate Redstone Comparator when Hopper is below it&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-8457&quot;&gt;MC-8457&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="50099" author="jespertheend" created="Tue, 5 Mar 2013 20:27:25 +0100"  >&lt;p&gt;horizontal works as expected now, hoppers got waaayy slower though, but I can live with that.&lt;/p&gt;</comment>
                            <comment id="49684" author="hfog" created="Mon, 4 Mar 2013 20:38:36 +0100"  >&lt;p&gt;@Kumasasa: I can confirm Rocket Turtle&apos;s observations. Horizontal hopper behavior now appears to work correctly. Vertical behavior still seems to be a little less correct.&lt;/p&gt;

&lt;p&gt;This is a great improvement and I could live with this just it is now but it doesn&apos;t appear to be 100% correct just yet.&lt;/p&gt;</comment>
                            <comment id="49682" author="zipron" created="Mon, 4 Mar 2013 20:35:06 +0100"  >&lt;p&gt;&lt;a href=&quot;http://youtu.be/gROZ6Ip2ZhE&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://youtu.be/gROZ6Ip2ZhE&lt;/a&gt; proof that this works&lt;/p&gt;</comment>
                            <comment id="49678" author="kumasasa" created="Mon, 4 Mar 2013 20:22:33 +0100"  >&lt;p&gt;Ok, thanks for the feedback. &lt;/p&gt;</comment>
                            <comment id="49677" author="rocketturtle" created="Mon, 4 Mar 2013 20:20:53 +0100"  >&lt;p&gt;@Kumasasa The original behavior that I reported to start this ticket does persist into 13w10a (I reran my original tests in a new map).  However, even then I suspected what I saw wasn&apos;t the result of a bug per se, but unfortunate behavior in stacked hoppers.&lt;/p&gt;

&lt;p&gt;tl;dr Yes, still going in 13w10a.&lt;/p&gt;</comment>
                            <comment id="49675" author="zipron" created="Mon, 4 Mar 2013 20:16:24 +0100"  >&lt;p&gt;It is definitly fixed the way I used to encounter it. I&apos;ll upload a video about it in an hour to confirm. Tested it in creative and survival now, the same setup I had since 13w05a, and it works like a charm with 500+ hoppers.&lt;/p&gt;</comment>
                            <comment id="49674" author="jlbshecky" created="Mon, 4 Mar 2013 20:12:46 +0100"  >&lt;p&gt;Looking at how things were affected in this update I would say that we have been seeing two different bugs/game mechanics actually occurring.&lt;/p&gt;

&lt;p&gt;The first bug/mechanic is when when hoppers are stacked vertically. Hoppers constantly try to pull things out of the hopper above them. Prior to 13w10a, when hoppers did their pulling was rather unpredictable. To demonstrate this unpredictably build a tower of 4 hoppers when a chest at the top and bottom and comparators + repeaters reading the levels of every hopper. If you put a stack of items in the top chest in 13w09a/b/c some of the repeaters with light, some will blink and some will just stay off. It appears as if there is no ryhme or reason behind the pattern as it will change if you rebuild the test in a different location or re-log. In 13w10a, the test stack becomes more predictable, but it still does not match up with what is expected as only the bottom repeater will light up for me, no matter the stack size or if I point the hoppers down or to the side. Watching the slots in the hopper tower it seems that hoppers are sucking items before the comparitors have had a chance to update, and since the bottom hopper doesn&apos;t have anything sucking items from it, one item appears to get stuck until the bottom is not able to suck stuff from above.&lt;/p&gt;

&lt;p&gt;The second bug/mechanic was visible prior to 13w10a, and it occured when items were moving sideways through hoppers. Items would seemingly skip hoppers and not get sucked down by hoppers below. This seems to be related to &lt;a href=&quot;https://bugs.mojang.com/browse/MC-10679&quot; title=&quot;Hopper Cool-Down is messed up&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-10679&quot;&gt;&lt;del&gt;MC-10679&lt;/del&gt;&lt;/a&gt;, as it now works correctly in 13w010a.&lt;/p&gt;</comment>
                            <comment id="49669" author="kumasasa" created="Mon, 4 Mar 2013 20:06:22 +0100"  >&lt;p&gt;@Zipron Brendt, Rocket Turtle: Is this bug fixed in 13w10a or still persisting in 13w10a ?&lt;/p&gt;</comment>
                            <comment id="49619" author="rocketturtle" created="Mon, 4 Mar 2013 18:10:30 +0100"  >&lt;p&gt;Confirmed in 13w10a.&lt;/p&gt;</comment>
                            <comment id="49611" author="zipron" created="Mon, 4 Mar 2013 17:54:13 +0100"  >&lt;p&gt;This bug is fixed in 13w01a!&lt;/p&gt;</comment>
                            <comment id="48856" author="jespertheend" created="Fri, 1 Mar 2013 23:19:48 +0100"  >&lt;p&gt;OK, I was wrong, it&apos;s still there, but at least it&apos;s better.&lt;/p&gt;</comment>
                            <comment id="48715" author="zipron" created="Fri, 1 Mar 2013 17:41:28 +0100"  >&lt;p&gt;Confirmed for 19w09c&lt;/p&gt;</comment>
                            <comment id="48692" author="samsolo97" created="Fri, 1 Mar 2013 17:12:02 +0100"  >&lt;p&gt;Ya, I checked if it was fixed and got really excited but turns out it&apos;s still broken... No easy Item sorting :&apos;( (unless you use minecarts)&lt;/p&gt;</comment>
                            <comment id="48683" author="hfog" created="Fri, 1 Mar 2013 17:03:25 +0100"  >&lt;p&gt;No. It&apos;s NOT fixed in 13w09c. And a sideways stacking system does NOT work perfectly. It works a little better than it used to but I have verified that it is still quite broken.&lt;/p&gt;</comment>
                            <comment id="48669" author="jespertheend" created="Fri, 1 Mar 2013 16:45:50 +0100"  >&lt;p&gt;I think it&apos;s kind of fixed in 13w09c, your system still doesn&apos;t work though, but a sideways stacking system works perfectly now.&lt;/p&gt;</comment>
                            <comment id="48097" author="zipron" created="Wed, 27 Feb 2013 22:21:38 +0100"  >&lt;p&gt;confirmed for 13w09b&lt;/p&gt;</comment>
                            <comment id="47667" author="zipron" created="Tue, 26 Feb 2013 15:58:51 +0100"  >&lt;p&gt;confirmed for 13w09a&lt;/p&gt;</comment>
                            <comment id="45687" author="zipron" created="Thu, 14 Feb 2013 16:01:01 +0100"  >&lt;p&gt;confirmed for 13w07a&lt;/p&gt;</comment>
                            <comment id="44320" author="jespertheend" created="Thu, 7 Feb 2013 21:48:42 +0100"  >&lt;p&gt;Confirmed for 16w06a&lt;/p&gt;</comment>
                            <comment id="44266" author="zipron" created="Thu, 7 Feb 2013 19:21:44 +0100"  >&lt;p&gt;Still bugged in 13w06a.&lt;/p&gt;</comment>
                            <comment id="42887" author="jespertheend" created="Sat, 2 Feb 2013 19:10:16 +0100"  >&lt;p&gt;that video (&lt;a href=&quot;http://youtu.be/jMszbxiBqKQ&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://youtu.be/jMszbxiBqKQ&lt;/a&gt;) really showed the problem, go watch that mojang!&lt;/p&gt;</comment>
                            <comment id="42807" author="wolfiemario" created="Sat, 2 Feb 2013 16:26:43 +0100"  >&lt;p&gt;I found a more elegant and compact workaround to this bug: you can manually control priority by powering hoppers you want to be lower priority, and depowering them with a comparator output from the hopper: This gives the &quot;higher priority&quot; hopper a better chance of grabbing the item if it can. Note, however, that this inconsistent timing bug is still present: you can make it less likely by increasing the delay before depowering the hopper, but it still can rarely happen (this really shouldn&apos;t be possible once more than 3.5 redstone ticks of delay have passed).&lt;br/&gt;
Here&apos;s a screenshot: &lt;a href=&quot;http://i.imgur.com/cBDxnCI.png&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://i.imgur.com/cBDxnCI.png&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I&apos;ve also added a schematic above.&lt;/p&gt;

&lt;p&gt;EDIT: Oh, and this version also has the issue of only being able to handle one item at a time.&lt;/p&gt;</comment>
                            <comment id="42704" author="wolfiemario" created="Sat, 2 Feb 2013 06:31:26 +0100"  >&lt;p&gt;Confirmed for 13w05b.&lt;/p&gt;

&lt;p&gt;Added a schematic of vertical and horizontal hopper sorters. Both are effected by this bug, and the behavior is &lt;b&gt;very&lt;/b&gt; inconsistent. This is problematic, as I wanted to make a multi-item detector with hoppers to replace my old ice-based one - hoppers would have allowed for faster rates (important for the system I&apos;m working on), but this would entirely fail to detect items at random - and worse, depending on unknown chunk loading factors, some items will be &lt;b&gt;impossible&lt;/b&gt; to detect until the chunk is reloaded. Thus, the behavior is very inconsistent to say the least.&lt;/p&gt;

&lt;p&gt;A possible fix would be to give higher precedence to sucking items from a container than pushing items to the next one: in this way, a horizontal sorter would function as intended, because all items would have a chance to be sucked out before they are pushed on to the next hopper.&lt;/p&gt;

&lt;p&gt;EDIT: A workaround for sorting items is to use Droppers, which work like the Allocator: when powered, they stick their contents into the next container. Chain droppers above a line of hoppers, and activate the dropper after a little delay if it has any contents (use a comparator, and feed the wire back to the dropper).&lt;/p&gt;

&lt;p&gt;The downside to this is that it fails if more than one item travels through at a time, so it&apos;d be slow at sorting, but still faster than an ice-based system for item detection (I believe forcing the dropper to dispense into the next dropper in the chain after a delay allows this to be faster than an ordinary hopper pipe: two ticks of redstone delay is less than the natural 3.5 ticks offered by hoppers. Thus, if an item is not the target, it will move along quicker than normal. I think you&apos;ll be forced to only have every other block a dropper, and the rest hoppers which feed into the next dropper, in order to avoid crossing wires when activating the dropper. Regardless, a width of two is faster than a width of five for an ice detection scheme: the ice scheme transports items at twice the rate of a hopper pipe (a normal ice pipe will transport items at four times the rate), but the distance is more than halved and the delay is reduced even more by each dropper, thus improving performance overall).&lt;/p&gt;

&lt;p&gt;Regardless, this workaround is very expensive for a survival setup, and far less compact (as I said above, to avoid crossing wires, you&apos;ll need a line of droppers/hoppers twice as long as normal).&lt;/p&gt;</comment>
                            <comment id="42522" author="zipron" created="Fri, 1 Feb 2013 22:14:45 +0100"  >&lt;p&gt;Made a quick video to illustrate the issue: &lt;a href=&quot;http://youtu.be/jMszbxiBqKQ&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://youtu.be/jMszbxiBqKQ&lt;/a&gt;&lt;br/&gt;
I can confirm this is just very random, and it will change when chunks are reloaded.&lt;/p&gt;</comment>
                            <comment id="39301" author="jub" created="Wed, 23 Jan 2013 21:43:12 +0100"  >&lt;p&gt;I thought my sorting system was fool proof until I tested it. The hopper priorities do not work as I expected or as the wiki stated so I am rather confused. I can CONFIRM this does happen.&lt;/p&gt;</comment>
                            <comment id="39287" author="jespertheend" created="Wed, 23 Jan 2013 18:38:09 +0100"  >&lt;p&gt;I added a world file (test) with two item sorters. If you want both item sorters to work, the item sorter has to look which hopper has the most amount of items of the item the hopper wants to move and go into the chest/furnance/hopper with the most items.&lt;/p&gt;</comment>
                            <comment id="39089" author="jespertheend" created="Tue, 22 Jan 2013 17:15:00 +0100"  >&lt;p&gt;I think this explains very well what is the way it should work: &lt;a href=&quot;http://youtu.be/h80qAGuJxkw?t=5m37s&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://youtu.be/h80qAGuJxkw?t=5m37s&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="39052" author="willrust303" created="Tue, 22 Jan 2013 12:19:52 +0100"  >&lt;p&gt;As a temporary fix, introduce a chest into the hopper system (i.e. somewhere are the top just before the hoppers start pushing different directions - I found this fixes the issue (temporarily - the big is still there). I believe it is to do with the hoppers placing items in either slot 1 or slot 2 of the hoppers&apos; inventory - this for some reason also dictates where the items end up further along the chain...&lt;/p&gt;</comment>
                            <comment id="39049" author="thodietho" created="Tue, 22 Jan 2013 11:59:14 +0100"  >&lt;p&gt;I confirm this bug and its REAALY ANNOYING&lt;/p&gt;</comment>
                            <comment id="38924" author="jespertheend" created="Mon, 21 Jan 2013 19:34:20 +0100"  >&lt;p&gt;Sometimes it works fine, but because of some sort of update the hopper get&apos;s &apos;broken&apos; and then it doesn&apos;t work the way it did anymore.&lt;/p&gt;</comment>
                            <comment id="38809" author="flapjacksmike" created="Mon, 21 Jan 2013 06:37:21 +0100"  >&lt;p&gt;I just tested this graphical example (&lt;a href=&quot;https://mojang.atlassian.net/secure/attachment/18903/2013-01-17_18.36.44.png&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://mojang.atlassian.net/secure/attachment/18903/2013-01-17_18.36.44.png&lt;/a&gt;) from the attachments above. All four cardinal directions work fine, and both blue and red wool go to the correct chest.&lt;/p&gt;</comment>
                            <comment id="37537" author="willrust303" created="Thu, 17 Jan 2013 20:37:43 +0100"  >&lt;p&gt;Items put into slot 1 a hopper will be pulled by hoppers underneath (as a priority over being pushed by the above hopper to the side). Items placed into slot 2 of a hopper will be pushed sideways (as a priority over being pulled by any hopper underneath)&lt;/p&gt;</comment>
                            <comment id="37508" author="willrust303" created="Thu, 17 Jan 2013 19:52:46 +0100"  >&lt;p&gt;I&apos;m confident that I have isolated a bug... (see screenshot above with words scribbled on it)... If a hopper pulls an item from a chest it is pulled by hoppers underneath... if it is placed (or pushed into by another hopper) into a hopper, it will take a different priority... that certainly seems like a bug to me!!&lt;/p&gt;</comment>
                            <comment id="37467" author="willrust303" created="Thu, 17 Jan 2013 18:47:26 +0100"  >&lt;p&gt;Issue still present in snapshot 12w03a &lt;img class=&quot;emoticon&quot; src=&quot;https://bugs.mojang.com/images/icons/emoticons/sad.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="37194" author="jespertheend" created="Wed, 16 Jan 2013 22:04:57 +0100"  >&lt;p&gt;Yup, I&apos;m having a same issue here, just a bit different I think.&lt;br/&gt;
I used this (take a look at attachment) for a sorting system and I want it to go down in to the bottom chest, but instead it goes to the chest on the right hand side.&lt;br/&gt;
Currently It is only sometimes going to the bottom chest, I don&apos;t know which way it is supposed to take (I prefer the bottom one) but the way it is now (random) is definitely wrong.&lt;/p&gt;</comment>
                            <comment id="37131" author="willrust303" created="Wed, 16 Jan 2013 12:35:50 +0100"  >&lt;p&gt;Since any issue relating to item transferring through hoppers is considered a duplicate with this, despite the specific nature of this Bug post... I will just like to point out a SIMILAR but definably different issue I am having with hoppers... That is a problem with their priorities, and that they don&apos;t seem to be consistent, and seem to change depending on if blocks are placed/removed around them (an updating issue?). This is especially the case when you have a hopper pushing items to a chest by its side, and another hopper under this first hopper. If this is built, initially the hopper below will take priority and will pull items from the above hopper before it gets the chance to push them into the chest. However after some block refreshing and/or restarting the game, the priority changes and the hopper now always pushes items into the chest. This issue seems to be more present, when a third hopper is feeding items into the inconsistent hopper - if this is the case items more often are pushed into the chest. However if items are placed STRAIGHT into the inconsistent hopper, then they will be pulled by the hopper below.&lt;/p&gt;

&lt;p&gt;Anyone get something similar? I&apos;m fairly sure this is subtly unique to this Bug report, yet its implications mean different things.&lt;/p&gt;</comment>
                            <comment id="37126" author="tadpoll27" created="Wed, 16 Jan 2013 09:01:23 +0100"  >&lt;p&gt;I have had a similar issue with this except I know my issue is a bug. I set up a pipe like system running horizontally about a dozen hoppers into them selves eventually leading to a chest. then below this row of hoppers I set up another row of hoppers pointing in various directions (left, right, and down). inside the lower hoppers I placed one item of various natures in each of the slots (one hoppers all oak saplings, one hopper all red stone dust, etc.) at the beginning of the top row of hoppers I placed a chest and proceed to place stacks of the items that were in the lower row of hoppers. about half the items went where I expected into the lower hoppers with their respective items inside and half continued onto the chest at the end of the top row of hoppers (all items of a specific type acted the same, ex. All birch saplings pasted their hopper and went to final chest, all oak leaves went to their hopper.) I looked for a pattern as to why they wouldn&apos;t go into the right hoppers but it appeared to be random. Replacing the hoppers fixed one of the infected hoppers but most of them continued to refuse their items. (playing in creative)&lt;/p&gt;</comment>
                            <comment id="36702" author="fmk" created="Mon, 14 Jan 2013 13:09:18 +0100"  >&lt;p&gt;Well, there are two somewhat simple solutions to the issue really, adding a Pipe item, which would also keep the Hopper &apos;simple&apos;, or giving Minecarts more love. Though I&apos;m sure Dinnerbone will have his own ideas on the matter, and sure, you could currently use dispensers and water and a space consuming setup as a filter to get a similar effect to pipes, but that doesn&apos;t work for projectiles or unstackable items, I figure I&apos;d put in my 2 cents on the matter.&lt;/p&gt;

&lt;p&gt;Pipes could have 2-6 slots (or however many one thinks would be needed), 1-5 to transfer items with, and the other to act as a filter (which if empty would let all items through), then the problem is solved. Though to solve the issue of pipes not knowing which way to go, you&apos;d want to make the face the pipe is placed against an input-only face, which would allow for the other 5 directions to either input items or receive items. Then you&apos;d just prioritize items going into filtered pipes first, and unfiltered pipes last.&lt;/p&gt;

&lt;p&gt;Of course, the pipes wouldn&apos;t be able to transfer items upwards, only sideways and down, as is logical and how hoppers already are, and thus still requiring minecarts or the like to move items upwards. Crafting recipe could probably be how rails are done but turned on their side, with a nether quartz replacing the stick, and could give 4-8 pipes per.&lt;/p&gt;

&lt;p&gt;More importantly, adding pipes would give a nice bit of aesthetics to moving items around, rather than the clunky mess that a chain of hoppers currently is.&lt;/p&gt;

&lt;p&gt;Alternatively, more functionality to minecarts, rails, and etc to make it possible to do something along the lines of the suggested pipes. Haven&apos;t really thought on it that too much though, so couldn&apos;t give any ideas on how one would do that.&lt;/p&gt;</comment>
                            <comment id="34156" author="corgano" created="Tue, 8 Jan 2013 07:37:29 +0100"  >&lt;p&gt;Hoppers need consistency - NEED it - if they will ever achieve their maximum usefulness. They should either always store the items before being able to be pulled form, or always have their items pulled to another hopper before being stored. Hell, even a switch between &quot;store&quot; and &quot;pass along&quot; mode. It just needs consistant&lt;/p&gt;</comment>
                            <comment id="33302" author="kpreid" created="Sat, 5 Jan 2013 18:53:15 +0100"  >&lt;p&gt;This may not be a &lt;em&gt;bug&lt;/em&gt; per se, but it is moderately inconsistent behavior &#8212; for example, I built a system like this but without intending to sort, merely three stacked chests &#8212; and the top and bottom chests got 50% split whereas the middle chest got nothing.&lt;/p&gt;

&lt;p&gt;I think it would be worth improving the behavior so that it is less obviously &quot;the effects of the precedence of a set of imperative rules&quot;.&lt;/p&gt;

&lt;p&gt;For example, what if, when a hopper grabs an item from a hopper above, it &lt;em&gt;doesn&apos;t&lt;/em&gt; grab the item &lt;em&gt;if it is possible for the hopper above to place an item&lt;/em&gt;? Thus hoppers below hoppers never starve the hoppers above, and this sorting system would work as intended.&lt;/p&gt;</comment>
                            <comment id="33161" author="shadowtani" created="Sat, 5 Jan 2013 11:37:03 +0100"  >&lt;p&gt;Duplicate of &lt;a href=&quot;https://bugs.mojang.com/browse/MC-6038&quot; title=&quot;Hopper doesnt always put items into the container it is &amp;quot;Connected&amp;quot; to&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MC-6038&quot;&gt;&lt;del&gt;MC-6038&lt;/del&gt;&lt;/a&gt;. It isn&apos;t a bug, the hopper retrieve items from the object above it automatically which is how they are supposed to work.&lt;/p&gt;

&lt;p&gt;The best solution for achieving what you are trying to achieve would be to have a pipe system so you can avoid stacking the hoppers under each other; maybe Mojang will add this together with filter objects such as a filter hopper and a filter pipe (can hope), if not, then compact and complex hopper designs won&apos;t be possible, and sadly neither automatic item sorting.&lt;/p&gt;</comment>
                            <comment id="33133" author="migsect" created="Sat, 5 Jan 2013 09:43:44 +0100"  >&lt;p&gt;I just tested this, and I can confirm this behavior.&lt;/p&gt;

&lt;p&gt;I think the hopper&apos;s top side&apos;s pull (topside) operation takes precedence over it&apos;s push (bottom and side) operation, which would cause this behavior.&lt;/p&gt;</comment>
                            <comment id="33129" author="kumasasa" created="Sat, 5 Jan 2013 09:36:37 +0100"  >&lt;p&gt;... sorry, wrong ticket.&lt;br/&gt;
Nothing happened here &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>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="18697">MC-6038</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="19786">MC-7009</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="19849">MC-7071</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="19859">MC-7081</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="19914">MC-7136</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="20188">MC-7402</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="20203">MC-7416</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="20551">MC-7741</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="20682">MC-7866</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="21055">MC-8179</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="21320">MC-8398</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="21650">MC-8687</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="24008">MC-10141</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="24022">MC-10150</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="24507">MC-10546</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="24552">MC-10586</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="24624">MC-10652</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="26540">MC-11828</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="26933">MC-12192</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="28510">MC-13418</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="50122">MC-29293</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="99789">MC-72009</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="541750">MC-265091</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="559958">MC-273025</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10103">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="58924">MC-36797</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="17075" name="2013-01-04_20.12.49.png" size="513796" author="rocketturtle" created="Sat, 5 Jan 2013 03:33:04 +0100"/>
                            <attachment id="17077" name="2013-01-04_20.14.02.png" size="434647" author="rocketturtle" created="Sat, 5 Jan 2013 03:33:04 +0100"/>
                            <attachment id="17078" name="2013-01-04_20.16.11.png" size="263721" author="rocketturtle" created="Sat, 5 Jan 2013 03:33:04 +0100"/>
                            <attachment id="17076" name="2013-01-04_20.16.45.png" size="299677" author="rocketturtle" created="Sat, 5 Jan 2013 03:33:04 +0100"/>
                            <attachment id="18808" name="2013-01-16_22.00.43.png" size="220966" author="jespertheend" created="Wed, 16 Jan 2013 22:04:50 +0100"/>
                            <attachment id="18903" name="2013-01-17_18.36.44.png" size="425861" author="willrust303" created="Thu, 17 Jan 2013 19:52:46 +0100"/>
                            <attachment id="20686" name="Hopper Item Sorter.schematic" size="594" author="wolfiemario" created="Sat, 2 Feb 2013 06:31:26 +0100"/>
                            <attachment id="20740" name="Partial Workaround.schematic" size="530" author="wolfiemario" created="Sat, 2 Feb 2013 16:23:12 +0100"/>
                            <attachment id="19470" name="test.zip" size="235532" author="jespertheend" created="Wed, 23 Jan 2013 18:38:09 +0100"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Fri, 1 Feb 2013 21:18:00 +0100</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_11100" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Linked</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>20.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0mzpb:</customfieldvalue>

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