Hoppers don't pick up items above non full blocks > 5/8 block tall
Updated description by [Mod] GoldenHelmet
The bug: hoppers do not search the entire block space above themselves for items to collect, as they do on Java. Instead, they search only + 0.625 Y (5/8 block or 10 pixels) above themselves.
Steps to reproduce
- Put a pointed dripstone, enchanting table, or horizontal grindstone on top of a hopper.
- Drop an item on top.
Expected result
The hopper collects the item.
Observed result
The hopper does not collect the item.
Note: The original report here focused on hoppers not collecting items from above soul sand, dirt path, and farmland blocks, as they do on Java. However, those blocks (along with honey blocks) have full-height collision in Bedrock (MCPE-12109, MCPE-87458) so they cannot be used to show the bug in the hopper collection range.
Hoppers will not pick up items through soul sand, path, and farmland blocks.
Linked Issues
is duplicated by10
MCPE-79133Hoppers under soul sand do not pick up dropped items.DuplicateMCPE-93548Incorrect Collision boxes for non full blocksDuplicateMCPE-95099Hoppers don’t pick up items which were dropped on a farmland, soul sand, and honey block.DuplicateMCPE-131123Items can not pass through small pointed dripstone on hoppersDuplicateMCPE-141388The hopper does not collect more than half a block, but in Java it does.DuplicateMCPE-155479Wrong range of the hopper to fetch entitiesDuplicateMCPE-164733Hopper with mud block on top are not taking itemsDuplicateMCPE-164997Items can't sink into mud, soul sand, dirt path, and farmlandDuplicateMCPE-166061Hoppers can not pick up items through mud like in Java edition.DuplicateMCPE-166198Hoppers Don't Pull Items Through FarmlandDuplicate![[Mod] GoldenHelmet](../../../data/avatars/users/18951.svg){kind=small}
- Fixed
Prudii Gaming- 70
- 30
- Confirmed
- 140972
- Multiple
- java-parity
1.19.60.22 Preview - 1.19.51
1.19.60.22 Preview 1.19.60.20 Preview 1.19.50.22 Preview 1.19.50.21 Preview 1.18.32 1.19.0.31 Preview 1.19.0.30 Beta 1.17.11 Hotfix 1.17.10.22 Beta 1.16.20.54 Beta 1.13.1 1.13.0 1.14.0 1.14.60 Hotfix 1.16.1 1.16.10 1.16.40 Hotfix 1.16.100 1.16.200 1.16.201 Hotfix 1.16.210 1.16.221 Hotfix 1.17.0 1.17.30 1.17.41 Hotfix 1.18.2 Hotfix 1.18.30 1.18.31 1.19.2 Hotfix 1.19.21 Hotfix 1.19.31 Hotfix 1.19.40 1.19.50 1.19.51- 1.19.70.20 Preview 1.19.70
Created Issue:
Hoppers dont pick up items above non full blocks.
Hoppers will not pick up items through soul sand, path, and farmland blocks.
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
relates to
is duplicated by
![[MCPE Mod] Celesian](../../../data/avatars/users/81635.png){kind=small}
is blocked by
is duplicated by
relates to
Hoppers dont pick up items above non full blocks.Hoppers don't pick up items above non full blocks > 5/8 block tall
relates to
is duplicated by
is duplicated by
Updated description by [Mod] GoldenHelmet
The bug: hoppers do not search the entire block space above themselves for items to collect, as they do on Java. Instead, they search only + 0.75 Y above themselves.More technically, from the hopper's exact block coordinate it searches for items between +0.75 Y and +1.75 Y. Presumably it starts at +0.75 Y instead of +1 Y so that it can collect items that sit inside the funnel. If that is intended then the Y range should be 1.25 blocks so that it reaches up to Y + 2, covering a full block height above itself.
Steps to reproduce
- Put an enchanting table or horizontal grindstone on top of a hopper.
- Drop an item on top.
Expected result
The hopper collects the item.
Observed result
The hopper does not collect the item.
Note : The original report here focused on hoppers not collecting items from above soul sand, dirt path, and farmland blocks, as they do on Java. However, those blocks (along with honey blocks) have full-height collision in Bedrock (
MCPE-12109,MCPE-87458) so they cannot be used to show the bug in the hopper collection range.
Hoppers will not pick up items through soul sand, path, and farmland blocks.
Updated description by [Mod] GoldenHelmet
The bug:hoppers do not search the entire block space above themselves for items to collect, as they do on Java. Instead, they search only + 0.75 Y above themselves.More technically, from the hopper's exact block coordinate it searches for items between +0.75 Y and +1.75 Y. Presumably it starts at +0.75 Y instead of +1 Y so that it can collect items that sit inside the funnel. If that is intended then the Y range should be 1.25 blocks so that it reaches up to Y + 2, covering a full block height above itself.
Steps to reproduce
- Put an enchanting table or horizontal grindstone on top of a hopper.
- Drop an item on top.
Expected result
The hopper collects the item.
Observed result
The hopper does not collect the item.
Note: The original report here focused on hoppers not collecting items from above soul sand, dirt path, and farmland blocks, as they do on Java. However, those blocks (along with honey blocks) have full-height collision in Bedrock (
MCPE-12109,MCPE-87458) so they cannot be used to show the bug in the hopper collection range.
Hoppers will not pick up items through soul sand, path, and farmland blocks.
Updated description by [Mod] GoldenHelmet
The bug: hoppers do not search the entire block space above themselves for items to collect, as they do on Java. Instead, they search only + 0.75 Y above themselves.More technically, from the hopper's exact block coordinate it searches for items between +0.75 Y and +1.75 Y. Presumably it starts at +0.75 Y instead of +1 Y so that it can collect items that sit inside the funnel. If that is intended then the Y range should be 1.25 blocks so that it reaches up to Y + 2, covering a full block height above itself.
Steps to reproduce
- Put an enchanting table or horizontal grindstone on top of a hopper.
- Drop an item on top.
Expected result
The hopper collects the item.
Observed result
The hopper does not collect the item.
Note: The original report here focused on hoppers not collecting items from above soul sand, dirt path, and farmland blocks, as they do on Java. However, those blocks (along with honey blocks) have full-height collision in Bedrock (
MCPE-12109,MCPE-87458) so they cannot be used to show the bug in the hopper collection range.
Hoppers will not pick up items through soul sand, path, and farmland blocks.
Updated description by
[Mod] GoldenHelmet
The bug: hoppers do not search the entire block space above themselves for items to collect, as they do on Java. Instead, they search only + 0.75 Y above themselves.More technically, from the hopper's exact block coordinate it searches for items between +0.75 Y and +1.75 Y. Presumably it starts at +0.75 Y instead of +1 Y so that it can collect items that sit inside the funnel. If that is intended then the Y range should be 1.25 blocks so that it reaches up to Y + 2, covering a full block height above itself.
Steps to reproduce
- Put an enchanting table or horizontal grindstone on top of a hopper.
- Drop an item on top.
Expected result
The hopper collects the item.
Observed result
The hopper does not collect the item.
Note: The original report here focused on hoppers not collecting items from above soul sand, dirt path, and farmland blocks, as they do on Java. However, those blocks (along with honey blocks) have full-height collision in Bedrock (
MCPE-12109,MCPE-87458) so they cannot be used to show the bug in the hopper collection range.
Hoppers will not pick up items through soul sand, path, and farmland blocks.
Updated description by [Mod] GoldenHelmet
The bug: hoppers do not search the entire block space above themselves for items to collect, as they do on Java. Instead, they search only + 0.75 Y above themselves.More technically, from the hopper's exact block coordinate it searches for items between +0.75 Y and +1.75 Y. Presumably it starts at +0.75 Y instead of +1 Y so that it can collect items that sit inside the funnel. If that is intended then the Y range should be 1.25 blocks so that it reaches up to Y + 2, covering a full block height above itself.
Steps to reproduce
- Put an enchanting table or horizontal grindstone on top of a hopper.
- Drop an item on top.
Expected result
The hopper collects the item.
Observed result
The hopper does not collect the item.
Note: The original report here focused on hoppers not collecting items from above soul sand, dirt path, and farmland blocks, as they do on Java. However, those blocks (along with honey blocks) have full-height collision in Bedrock (
MCPE-12109,MCPE-87458) so they cannot be used to show the bug in the hopper collection range.
Hoppers will not pick up items through soul sand, path, and farmland blocks.
Updated description by [Mod] GoldenHelmet
The bug: hoppers do not search the entire block space above themselves for items to collect, as they do on Java. Instead, they search only + 0.75 Y above themselves.More technically, from the hopper's exact block coordinate, it searches for items between +0.75 Y and +1.75 Y. Presumably it starts at +0.75 Y instead of +1 Y so that it can collect items that sit inside the funnel. If that is intended then the Y range should be 1.25 blocks so that it reaches up to Y + 2, covering a full block height above itself.
Steps to reproduce
- Put an enchanting table or horizontal grindstone on top of a hopper.
- Drop an item on top.
Expected result
The hopper collects the item.
Observed result
The hopper does not collect the item.
Note: The original report here focused on hoppers not collecting items from above soul sand, dirt path, and farmland blocks, as they do on Java. However, those blocks (along with honey blocks) have full-height collision in Bedrock (
MCPE-12109,MCPE-87458) so they cannot be used to show the bug in the hopper collection range.
Hoppers will not pick up items through soul sand, path, and farmland blocks.
is blocked by
![[MCQA] v-magwar](../../../data/avatars/users/18935.svg){kind=small}
is duplicated by
Updated description by [Mod] GoldenHelmet
The bug: hoppers do not search the entire block space above themselves for items to collect, as they do on Java. Instead, they search only + 0.75 Y above themselves.More technically, from the hopper's exact block coordinate, it searches for items between +0.75 Y and +1.75 Y. Presumably it starts at +0.75 Y instead of +1 Y so that it can collect items that sit inside the funnel. If that is intended then the Y range should be 1.25 blocks so that it reaches up to Y + 2, covering a full block height above itself.
Steps to reproduce
- Put a
nenchanting table or horizontal grindstone on top of a hopper.- Drop an item on top.
Expected result
The hopper collects the item.
Observed result
The hopper does not collect the item.
Note: The original report here focused on hoppers not collecting items from above soul sand, dirt path, and farmland blocks, as they do on Java. However, those blocks (along with honey blocks) have full-height collision in Bedrock (
MCPE-12109,MCPE-87458) so they cannot be used to show the bug in the hopper collection range.
Hoppers will not pick up items through soul sand, path, and farmland blocks.
Updated description by [Mod] GoldenHelmet
The bug: hoppers do not search the entire block space above themselves for items to collect, as they do on Java. Instead, they search only + 0.6875 Y above themselves.Steps to reproduce
- Put a pointed dripstone, enchanting table, or horizontal grindstone on top of a hopper.
- Drop an item on top.
Expected result
The hopper collects the item.
Observed result
The hopper does not collect the item.
Note: The original report here focused on hoppers not collecting items from above soul sand, dirt path, and farmland blocks, as they do on Java. However, those blocks (along with honey blocks) have full-height collision in Bedrock (
MCPE-12109,MCPE-87458) so they cannot be used to show the bug in the hopper collection range.
Hoppers will not pick up items through soul sand, path, and farmland blocks.
Updated description by [Mod] GoldenHelmet
The bug: hoppers do not search the entire block space above themselves for items to collect, as they do on Java. Instead, they search only + 0.6875 Y above themselves.Steps to reproduce
- Put a pointed dripstone, enchanting table, or horizontal grindstone on top of a hopper.
- Drop an item on top.
Expected result
The hopper collects the item.
Observed result
The hopper does not collect the item.
Note: The original report here focused on hoppers not collecting items from above soul sand, dirt path, and farmland blocks, as they do on Java. However, those blocks (along with honey blocks) have full-height collision in Bedrock (
MCPE-12109,MCPE-87458) so they cannot be used to show the bug in the hopper collection range.
Hoppers will not pick up items through soul sand, path, and farmland blocks.
Updated description by [Mod] GoldenHelmet
The bug: hoppers do not search the entire block space above themselves for items to collect, as they do on Java. Instead, they search only + 0.625 Y (5/8 block or 10 pixels) above themselves.Steps to reproduce
- Put a pointed dripstone, enchanting table, or horizontal grindstone on top of a hopper.
- Drop an item on top.
Expected result
The hopper collects the item.
Observed result
The hopper does not collect the item.
Note: The original report here focused on hoppers not collecting items from above soul sand, dirt path, and farmland blocks, as they do on Java. However, those blocks (along with honey blocks) have full-height collision in Bedrock (
MCPE-12109,MCPE-87458) so they cannot be used to show the bug in the hopper collection range.
Hoppers will not pick up items through soul sand, path, and farmland blocks.
![[Mod] EVGENSYPERPRO](../../../data/avatars/users/92853.png){kind=small}
![[MCQA] Justyna Oleś](../../../data/avatars/users/18934.svg){kind=small}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Confirmed in 1.13.1 on Windows 10.
I have attached a demo world MCPE-55824.mcworld. I suspect that the reason it works this way is that when an item entity is floating above one of these blocks, its Y coordinate is 1.1 blocks above the hopper, which would put it out of range. For an item entity floating above a bottom slab, on the other hand, its Y coordinate is 0.6 blocks above the hopper, which is in range so the hopper sucks it in.
Duplicate of MCPE-55824
Thank you for your report!
We're actually already tracking this issue at MCPE-55824, so I will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue at MCPE-55824, so I will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Tal, as I explained on MCPE-46746, it's the next shulker box being placed, and not the piston, that forces the shulker box item entity to pass through the full/solid blocks. So what you have described cannot be reproduced.
My guess is that what you expect to happen in the build in your picture, is that all of the shulker boxes would be collected by the hopper underneath. The actual reason that all of the shulker boxes are not collected is that (a) hoppers do not collect item entities from the entire block space above them (MCPE-55824), and (b) the next shulker box is placed before the broken one falls into range of the hopper. Notice that if you slow down the circuit then all of the shulker boxes get collected.
I do think that you've found a significant issue here, so I will update MCPE-55824 when I have some time.
When an armor stand is broken by an arrow in Minecraft Java Edition and the items are sucked up by a hopper the order of those items seems to be consistently from left to right: Boots, Leggins, Chestplate, Helmet, Armor Stand.
This allows for consistent item sorting as displayed in this video: https://www.youtube.com/watch?v=xFFK_NXNMqk
In Minecraft Bedrock however, using the same setup (obviously using a half-slab above the hopper for the armor stand to be placed on due to MCPE-55824) the order of items is NOT consistent - apart from the armor stand landing in the 4th slot - the armor items are in a random order.
It would indeed be pretty helpful to have this consistent order in MCPE as well.
Kai
Demonstration: The problem.mp4
This is caused by the minecart item entity receiving random momentum upon creation. Sometimes the random momentum also causes the minecart item to be destroyed (MCPE-94879).
However, regardless of the random momentum, the problem reported here would not even exist if hoppers were to check the entire block space above when collecting items, as they do in Java Edition. Hoppers in Bedrock only search up 0.75 blocks above for items (MCPE-55824). The reason the random momentum is able to throw items off to the side (or into the cactus itself) is because the items spawn near the top of the block, above the search range of hoppers.
That being the case, you can work around this bug by embedding a hopper minecart in the block in front of the cactus, as shown here: A workaround.mp4
Thank you for your report!
We're tracking this issue in MCPE-55824, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit
Thank you for your report!
We're tracking this issue in MCPE-55824, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-55824 and MCPE-99462, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Anatole: You're right. This is the MCPE-55824 report.
Thank you for your report!
We're tracking this issue in MCPE-55824, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
The issue with hoppers not pulling items through these blocks is already tracked at MCPE-55824, so I am resolving this report as a duplicate.
We initially misunderstood this report to be about the visual disparity between Java and Bedrock in how high items appear to float. In the future, please include Steps to reproduce with unambiguous Observed results and Expected results. Even the Observed/Expected results you copied from the comment do not make clear that the problem you are reporting is the interaction with hoppers.
Thank you for your report!
We're tracking this issue in MCPE-55824, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-55824, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Can confirm. Items in the groove of hopper block cannot be collected by the hopper.
Caused by the fix for MCPE-55824.
In the 1.19.70 Previews hoppers collect items from the full block space above them (fixing MCPE-55824). That should make shulker box collection after breaking very close to Java Edition. Does that address the issue raised here, or do you still feel that there is a bug?
Thank you for your report!
However, this issue is Working as Intended.
The report you have submitted is working as intended, based on MCPE-55824 having been fixed.
Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.
Full Version History – Snapshot Version History – Feature Requests and Suggestions
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Note: this behavior was described in MCPE-155479, but because that report also described other issues that were already reported it was resolved as a duplicate. This issue is causally unrelated to either MCPE-99462 or MCPE-55824.
Steps to reproduce
- Place a hopper at 2049 100 2049 or -2050 100 -2050.
- Place a column of several blocks of glass or stone on top of the hopper.
- Toss items against each side of the column.
Expected result
The hopper does not collect the items.
Observed result
The hopper collects the items.
Code analysis (from MCPE-155479)
Hopper::_getItemAt() defines a cube fetch range with a side length of 1, and inwards in all axes shrink by 0.0001. The float in C++ is only accurate to 6-7 digits in decimal, so when the value exceeds 2048, the shrinking by 0.0001 does not have any effect. (MCPE-99462 supersedes this bug at chunk borders, so it cannot be observed at X/Z +2048 or -2049.)
Confirmed in 1.13.1 on Windows 10.
I have attached a demo world
MCPE-55824.mcworld. I suspect that the reason it works this way is that when an item entity is floating above one of these blocks, its Y coordinate is 1.1 blocks above the hopper, which would put it out of range. For an item entity floating above a bottom slab, on the other hand, its Y coordinate is 0.6 blocks above the hopper, which is in range so the hopper sucks it in.Could we potentially see this as a feature? It would match Java, and also be super useful, as well as make sense. When a player stands on soul sand, they are lower than a full block.
There's a difference between an item entity, which floats above the surface, and other kinds of entities that rest on the surface, and that might be the issue here. I don't have Java so I can't compare the behavior, but if Java hoppers suck item entities floating on these blocks, I believe the developers will treat this as a parity bug and fix it.
I find it suspicious that item entities have the same Y coordinate for all three of these blocks as they do for a full-size solid block. I know the hit boxes of these blocks are < 1 block tall, and if the item entity sinks to the hit box of a bottom slab or pressure plate (which it does) then why wouldn't it do the same for these? Maybe they did something weird like hard code the item entity Y calculation instead of doing collision detection, who knows?
Confirmed on 1.14.0. The following non-cubic solid blocks let hoppers suck in item entities on them:
But these don't:
Farmland and grass path blocks actually have full-block collision boxes, so it's no mystery why hoppers underneath don't suck items floating on top of them. See
MCPE-12109.Soulsand was given a full collision box in 1.16. See
MCPE-87458. This was probably done in 1.16.0.63 beta, based on the changelog statement:They cant pick up items from over honey blocks
Something similar applies to honey blocks. Their top surface is slightly higher up so that mobs can pathfind on them.
Yes this affects honey blocks too (on 1.16.40). Most likely
MCPE-12109is the cause of this, as it is natural that hopper can't pick up items through blocks which have (wrongly) a full hitbox.The horizontal hitbox of Honey is smaller than the full box (correctly), but the vertical one is as tall as Stone.
Hoppers do not collect items from above anything higher than a stonecutter. In other words, they search only within the lower 5/8 of the block space above them for items. (Items on a stonecutter sit at +0.5625 and get collected by hoppers, while items on an enchanting table sit at +0.75 and do not get collected by hoppers.) This is inconsistent with the fact that hoppers pull from hopper/chest-minecarts sitting on top of bocks like enchanting tables and horizontal grindstones. I can't think of a reason why the hopper's item collection range should be restricted to less than a full block while their pulling range is not.
Affects 1.16.201
This still affects 1.16.210
Affects 1.17.41
In
MCPE-155479, it had describe the difference between java and bedrock edition with a detail analysis, which the difference feature is more or less causing players unable to manipulate most hopper-related contraption that collect item entities.Comment updated 8/24/22 with new analysis based more precise test results from teleporting items to fractional coordinate positions on every tick.
From the hopper's exact Y coordinate (its bottom edge) , it collects items whose positions are +0.375 Y < POS < +1.625 Y, or in other words within 5/8 of a block (10 pixels) above or below its top. Presumably, the search range of the hopper starts below the top of the hopper instead of at the top (at +1 Y) so that it can collect items that sit inside the funnel. I have also checked Java for comparison, and in Java hoppers can also pick up items at +0.375 Y from the bottom of the hopper (-0.625 Y or 5/8 block below the top) of the hopper.
It may be that the search range actually starts at +0.625 and it grabs items that sit at > +0.375 because their collision box extends upward by 0.25 and, therefore, into the search range. If that is the case then the full search range in Bedrock is actually 1 block. That sure looks like a simple mistake of thinking only of the space above the hopper and forgetting that collection starts deep inside its funnel. The range ought to be 1.375 blocks if it does start at +0.625, or if I am wrong about the impact of items' collision box height and the search starts at +0.375, then the range ought to be 1.625 blocks.
Affects 1.19.40.21.
Since the collision height of mud and soul sand has been lowered from 1.19.40.21, this has become a very urgent issue for technology users(even for users who just make sugar cane or bamboo farms!).
Affects 1.19.31