Hoppers fail to suck item entities from above, if the first slot is occupied with a stack of the same item floating above them, and their cooldown counter is non-zero.
Steps to reproduce:
Place down a chest (or any other containers).
Connect a hopper to it.
Throw a stack of cobblestone (or any other items) onto it.
It sucks in the stack as expected, and its first slot is now occupied with the stack. All of the remaining 4 slots are still empty.
It starts to push the items into the container.
Throw in another stack of the same item before the hopper becomes empty.
Observe that the hopper doesn't suck in the second stack even though it has enough space to be filled up.
Throw in a stack of torches (or any other different items) before the hopper becomes empty.
Observe that the hopper successfully sucks in torches into its second slot.
This doesn't happen when the cooldown counter is zero, i.e. the hopper isn't pushing items into some other containers.
What I expect:
Hoppers should ignore the cooldown counter while trying to suck in item entities.
Linked issues
Comments 2
Cleaning up old tickets: This ticket has not been updated recently (1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
It actually does continue to suck the same items, but only one at a time. If you look at the hopper's inventory after throwing the second stack on top of it, you'll see that the first slot, which had a partial stack of torches when you threw the second stack, fills up again one item at a time (since the hopper sucks items twice as fast as it pushes them out). So apparently what's happening is that when a hopper sucks an item and finds that it already has a partial stack of that item, it only sucks one item at a time instead of sucking the whole stack. It works this way even if it has an empty slot. For example, if you put a partial stack in slot 3 and then throw a full stack on top, it sucks the items from the full stack one at a time and puts them in slot 1, even though there is room for a full stack in slot 1. This might be a "works as intended".