Minecart Hitboxes Too Large
The minecart hitboxes are too large which messes up redstone contraptions that require minecarts to be side by side. A minecart beside another will push the other minecart out of the way.
Linked Issues
is duplicated by6
Created Issue:
Minecart Hitboxes Too Large
The minecart hitboxes are too large which messes up redstone contraptions that require minecarts to be side by side. A minecart beside another will push the other minecart out of the way.
is duplicated by
1.14.30.51 also
is duplicated by
relates to
Can confirm on retail version 1.14.3, and the 1.16.0.51 beta as well. This bug greatly affects technical builds in a negative way and should be moved to a higher priority.
is duplicated by
is duplicated by
is duplicated by
Duplicate of MCPE-59302
Thank you for your report!
We're actually already tracking this issue at MCPE-59302, so I resolved and linked 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.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue at MCPE-59302, so I resolved and linked 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 – ☃D83D? Game Wiki
Does the fix to minecart hitboxes in 1.16.0.57 (MCPE-59302) not impact this bug?
Nope, it's unrelated. This bug is in the the hopper-minecart search function.
Now, the fix for MCPE-54244 in 1.15.0.53 does impact this bug, because that fix allows hoppers and hopper-minecarts to ignore blocks with inventory above them and continue searching through hopper/chest-minecarts above and/or to the S or E side of those blocks. So now this bug is worse. (See MCPE-80555.)
Thank you for your report!
We're tracking this issue under MCPE-59302 so I've requested this report be resolved and linked as a duplicate.
This issue is reported as fixed in bedrock 1.16 beta
Quick Links:
📓 Issue Guidelines – 💬 Community Support Discord – 📧 Mojang Customer Support – 📖 Game Wiki
Thank you for your report!
We're tracking this issue as MCPE-59302, so this ticket is being resolved and linked as a duplicate.
That ticket has already been marked as fixed. The fix will arrive in the next version or is already included in an available version of the game, you can check the Fix Version/s field in that ticket to learn more.
If you haven't already, you might like to make use of the search feature to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue as MCPE-59302, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Fixed or has a Fix Version that relates to an ongoing BETA phase. The fix will arrive in a future version, you can check the Fix Version/s field in that ticket to learn more.
If you haven't already, you might like to make use of the search feature to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Hello,
I think we’re all familiar with hopper-minecarts pulling from other minecarts with inventory diagonally on X+1, Y+2, Z+1 going back years now MCPE-57637 and recently hopper-carts began going even more crazy with the fix for MCPE-54244 where new items in “infected” hopper-mc MUST be drained first.
I had done some reading and I believe the main reason behind this bug existing for so long is the lack of details on previous tickets to explain how serious this issue is and its connection and history of fixes I believe are related all together:
MCPE-57637, MCPE-54244, MCPE-80555, MCPE-94293, MCPE-59302, MCPE-68912
Lets start building:
1. Place chest and attach hopper to top side and then add 1 upside down slab to side of hopper and 4 more slabs to the other side to make flat surface for 3 activator rails.
2. Then place full block on top of slab furthest way from hopper and add redstone torch and repeater towards activator rails and place activator rails on 3 remaining blocks, on the full block, place lever on top and then place observer facing out and place lever on its face as well.
3. Add 2x2 inverted slabs on top of activator rail and place 4 detector rails on top of slabs, parallel to rails bellow.
4. Block each of detector rail exits with full blocks.
5. Add frames with items for orientation for example:
White – X=X, Y=Y+2, Z=Z; - Correct pull
Red – X=X+1, Y=Y+2, Z=Z; - 1 off to Right
Green – X=X+1, Y=Y+2, Z=Z+1; 1 off to Right and Bottom
Blue – X=X, Y=Y, Z=Z+1; 1 off to Bottom
6. Place hopper-cart on activator rail and use lever on observer to send a test pulse.
7. Place 4 remaining hopper-carts on top for each colour code in order: Blue, Green, Red, White.
8. Fill containers with matching colours
9. Use either of levers.
Experiment
Expected Results:
- On Pulse - Chest contain white wool
- On Switch – Hopper-mc pulls white wool from hopper-mc directly above it.
Actual Results:
- On Pulse – Chest contain blue wool
- On Switch – Hopper-mc pulled from each container above in the same order I placed them it. Blue, Green, Red, White
Additional Observation:
- For hopper-mc to pull white wool, red wool container must be empty; to pull red wool, green container must be empty; to pull green wool, blue container must be empty.
- This order is fixed. While white wool is pulled, if any other containers receive more wool, it will force pulling from that container instead. I assume
MCPE-54244is related to this. - Pull order is based on order in which hopper-minecarts were placed.
- If 2x2 square of hopper-minecarts cross chunk border the pulling hopper-mc would only remember order of those within its own chunk.
- Hopper-mc pushed towards brick wall pole is still able to pull diagonally. Tile-able designs require each hopper-mc to be placed individually and be equally pushed to the brick wall to prevent cross-contamination (very time consuming).
- Most effective way to keep hopper-carts pulling from Y+2 only was by having content in that container only when bottom hopper-cart is placed.
In summary:
Hopper-carts pull diagonally if given a chance to
Hopper-cart bellow can pull from chest-minecarts
Must pull in the same order minecart-containers above were placed – has the ability to prioritize pulling
Pushing towards brick wall did not affect pulling range
Also suggest that the source of the bug is a result of upper minecarts having their “collision box?” overlaying each other at the edge of scan from minecart bellow
Diagonal pulling only pulls from minecarts towards positive X Y Z and since I could not find any information as to how does hopper-minecart actually scans for target (mathematical formula), I can only assume this is caused by the lack of off-set for the calculation resulting in either bottom hopper-cart scanning extra area towards positive or hopper-cart invading scanned area of a hopper bellow with extra size towards negative. It could be both actually although I guess it is the second one.
I am aware that this could be considered a “duplicate” ticket and I really hope Moderators won’t close it so that players can find it and learn how to manage this diagonal pulling effect until developers can deal with it. I should probably point out that his is a new behaviour that I assume is the result of fix to MCPE-54244 and unresolved issue MCPE-57637 which exists for about 2 years now with label “won’t fix” or “work-as-intended” and now not only “can” pull diagonally but now hopper “must” stop pulling from hopper-cart directly above to pull from “infected” hopper-carts first if they have items inside.
This bug affects builds such as: Storage/item-transportation systems, Super-smelters which are the most complicated and time-consuming builds with practical application in survival worlds. It took me two days of experimenting in creative world with different combinations until I found a behaviour pattern that I want to share with you…
2 Clips attached and world in creative mode with example ready, one shows the “new” bug, the other solution – Make sure to focus on the order of hopper-carts being placed. (I am facing East on clips (X=X++))
That’s all I can do for now, I gathered the all information I could, so don’t hesitate to ask me any questions, I will answer as soon as I can.
Thank you very much for reading,
P.S. Ticket MCPE-46706 describes a behaviours which have very similar "angle" of operation - perhaps it is worth reading through as well.
I can confirm this issue as well. Very annoying and it basically breaks every red Stone contraption built with minecarts in the design.
Can confirm as well, also affects 1.14.1 and 1.14.2, very annoying when trying to make simple minecart unloaders.
You can see a bit of this bug in action here: https://youtu.be/9QVb8NtbU34?t=236
This also prevents multiple minecarts from being next to each other, when inside of blocks. For instance pushing 4 minecarts into a 2x2 of blocks, will always eject one of the carts. This was never an issue before.
Can confirm too. Very annoying
(Tested before reported - from 'Technical Bugs List' https://docs.google.com/document/d/1nziKYzCr4pBdCRj2gIMlfr9MVdWHd6HyafdiBHx9F0c/edit)
This issue happens in 1.14.30 hotfix and 1.15.0.51 also.
Also makes it impossible to remove a rail from under the mine cart once placed.
To help the developers, I've attached small world K1 that demonstrates the problem. Just place minecarts as shown in the video the OP included and you can easily test this.
1.15.0.54 also
Affects 1.16.0.53.
Affects 1.16.0.55.
Same problem here. 1.14.30 Bedrock Edition Windows 10!
This bug is fixed in the latest beta version, and the fix will be included in a future update when that is ready for full release (no specific date can be given). We will leave this ticket open as a point of reference until the fix has been fully released.
It definitely was fixed. The hitboxes are normal again. Thanks a lot to the developers!