MC-11303Hopper "regenerating" items
I open my survival inventory in creative. I place 3 stacks of 64 hoppers inside. I stand on top of a hopper. I open my inventory (NOT the hopper GUI) and put the cursor over the stacks of hoppers and press ctrl-z (z is my drop key) and drop the 3 stacks into the hopper. Then I open the hopper GUI and the 3 stacks of hoppers reappear in my inventory. This has been happening in the previous snapshots as well and has not been solved...
Environment
Mac OS X 10.8, newest Java (at the moment)
Linked Issues
Created Issue:
Hopper "regenerating" items
I open my survival inventory in creative. I place 3 stacks of 64 hoppers inside. I stand on top of a hopper. I open my inventory (NOT the hopper GUI) and put the cursor over the stacks of hoppers and press ctrl-z (z is my drop key) and drop the 3 stacks into the hopper. Then I open the hopper GUI and the 3 stacks of hoppers reappear in my inventory. This has been happening in the previous snapshots as well and has not been solved...
Environment
Mac OS X 10.8, newest Java (at the moment)
Attachments3
duplicates
![[Mod] Torabi](../../../data/assets/gravatar/torabi.png){kind=small}
Duplicate of
MC-5415, please use the search function to see if your bug has already been submitted. Currently over 53% of tickets are being closed as duplicate.There are two reasons for this:
1- The hopper's 5 slots are full
2 - You picked the items up before the hopper could.
OK, I tried this again. First i removed all the items from the hopper. Then I cleared my inventory with /clear. After that, I put 3 stacks of hoppers in my survival inventory. Note that this duplication did not happen when I put the stacks in my hot-bar. Then I open my inventory, ctrl-z, and opened the hopper GUI. There were 3 stacks of hoppers, the first already transferring. The 3 stacks of hoppers reappeared in my inventory.
People, I am very concerned that I posted this when I downloaded the 1.5pre-release, no one has responded, and the fact that this bug has NOT been fixed in the official release of 1.5. I am also concerned about the fact that someone has marked this bug as "resolved" when it is obvious that this bug has NOT been fixed.
Did you bother to check Tails' post or the "Resolution:"? They both say that this is a duplicate.
Yes, I did check Tails' comment and I did see that the resolution says that this a duplicate but what bothers me is the fact that it says that the status is "resolved" when I can clearly reproduce this bug countless times.
The resolution field applies to the issue report, not the bug itself.
This issue report is resolved. The resolution is that it's a duplicate report of
MC-5415. If you examine that report, its status is Unresolved. So while the bug has not been fixed, as indicated byMC-5415, this issue report is closed, and further comments on the bug should be posted atMC-5415. Also, if you voted for this issue to be fixed, you should go vote onMC-5415. Votes do not currently transfer from the duplicate issue to the it is marked a duplicate of, as per JRA-3731, so if you want the issue fixed, you should vote for the issue this has been marked a duplicate of.Oh. Thanks! I didn't know that.