<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 12:09:13 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-5835] Hopper and Enderchest</title>
                <link>https://bugs.mojang.com/browse/MC-5835</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;Hopper does not placed items in ender chests&lt;/p&gt;</description>
                <environment></environment>
        <key id="18488">MC-5835</key>
            <summary>Hopper and Enderchest</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="7">Invalid</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="ileon">Leon</reporter>
                        <labels>
                    </labels>
                <created>Thu, 3 Jan 2013 21:44:53 +0100</created>
                <updated>Fri, 20 Jun 2014 08:53:06 +0200</updated>
                            <resolved>Fri, 4 Jan 2013 10:49:38 +0100</resolved>
                                    <version>Snapshot 13w01a</version>
                                                                        <votes>0</votes>
                                    <watches>1</watches>
                                                                            <comments>
                            <comment id="165491" author="eareos" created="Fri, 20 Jun 2014 08:53:06 +0200"  >&lt;p&gt;Items Have A Owner Tag (Used In The Diamonds to You Achevement)&lt;/p&gt;</comment>
                            <comment id="67227" author="legionmammal978" created="Sat, 18 May 2013 20:58:55 +0200"  >&lt;p&gt;In SMP: It could go to the player that attached the hopper to the enderchest.&lt;br/&gt;
In SSP: It could go to the player that is on the world.&lt;br/&gt;
Also, Matt Lafreniere, you brought up a good point about multiple hoppers. For that you could make it so that the enderchest has multiple hopper inventories according to name.&lt;br/&gt;
Ex:&lt;br/&gt;
A hopper named &quot;Test1&quot; puts 64 diamonds into an enderchest.&lt;br/&gt;
The enderchest directs it into its &quot;Test1&quot; hopper inventory.&lt;br/&gt;
Another hopper named &quot;Test1&quot; will take 64 diamonds out of the enderchest&apos;s &quot;Test1&quot; hopper inventory but not the 64 emeralds in the enderchest&apos;s &quot;Test2&quot; hopper inventory (Which were put in there by a hopper named &quot;Test2.&quot;)&lt;/p&gt;</comment>
                            <comment id="46674" author="mattlafy" created="Wed, 20 Feb 2013 02:57:19 +0100"  >&lt;p&gt;why not give hoppers their own enderchest inventory? That way enderchests can still be used normally by players, but hoppers can also use them for instant automated transportation.  Obviously there&apos;s a potential issue of having multiple hoppers emptying multiple enderchests at once, but I would assume they would just each take an item in a somewhat random order. &lt;/p&gt;</comment>
                            <comment id="45456" author="ypetremann" created="Tue, 12 Feb 2013 22:36:32 +0100"  >&lt;p&gt;Why not having the hopper to put in the enderchest or get from it only when somebody looks in, if somebody looks when another, it could transfer only to the first player that opened it and is currently looks in.&lt;/p&gt;</comment>
                            <comment id="43578" author="stigofthetrack" created="Tue, 5 Feb 2013 00:07:17 +0100"  >&lt;p&gt;I&apos;ve heard this works with the equivalent items in FTB (I&apos;ve not got this installed, so can&apos;t verify this).&lt;/p&gt;

&lt;p&gt;I&apos;d second the suggestion by guillermo le metayer rodriguez to have the hopper use a non-accessible &apos;world&apos; inventory for the chest, one there only for use by hoppers. This would avoid the per player issues, while still allowing the ender chest to be used as a long-range link between hoppers.&lt;/p&gt;</comment>
                            <comment id="34686" author="paus3d" created="Thu, 10 Jan 2013 16:43:41 +0100"  >&lt;p&gt;I think it&apos;s not a bug. Hopper don&apos;t know who dropped item and can&apos;t place it to personal ender chest.&lt;/p&gt;</comment>
                            <comment id="32892" author="meta" created="Fri, 4 Jan 2013 21:55:20 +0100"  >&lt;p&gt;The reason is the hopper can&apos;t know in whose players enderchest the items should be placed in.&lt;br/&gt;
@Dinnerbone: you could add NBT data to dropped items to hold the player who dropped it maybe ...&lt;/p&gt;</comment>
                            <comment id="32825" author="guillermolmr" created="Fri, 4 Jan 2013 19:27:07 +0100"  >&lt;p&gt;i have an idea, they can make that the things you throw to the hopper to the ender chest gets in a invisible inventory and the only way to take them is puting a hopper under a ender chest (the same one or other), so in multiplayer will be a public chest our something like that&lt;/p&gt;</comment>
                            <comment id="32613" author="ileon" created="Fri, 4 Jan 2013 12:58:04 +0100"  >&lt;p&gt;Sorry.&lt;/p&gt;</comment>
                            <comment id="32600" author="dinnerbone" created="Fri, 4 Jan 2013 10:49:38 +0100"  >&lt;p&gt;It can&apos;t work.&lt;/p&gt;</comment>
                            <comment id="32344" author="rene_z" created="Thu, 3 Jan 2013 21:53:52 +0100"  >&lt;p&gt;How should that work? The Enderchest has different inventories for each player, and there&apos;s no way to detect into which inventory the items should go.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="18557">MC-5903</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="18827">MC-6166</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="18974">MC-6305</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="20550">MC-7740</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="20658">MC-7845</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="49411">MC-28929</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                        <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Unconfirmed]]></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>5.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i015gn:</customfieldvalue>

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