The issue is exactly how it sounds. Minecarts will randomly get stuck when moving along diagonal tracks when said tracks are right next to a wall of blocks. Yes, minecarts would be slowed down in previous versions, but now they randomly get stuck on walls and it’s breaking the rides I’ve built for my theme park maps. I’ve tried reducing the size of the collision box for minecarts and it doesn’t make any difference. When the minecarts get stuck, you can’t push them along when walking through them or when riding. You have to break the cart and respawn it to undo the issue.
The last version I know of that minecarts worked properly in was 1.20.81. One of the updates since then has created this bug.
To replicate, simply build a track like the picture attached, and try to run minecarts along it. It may take spawning a few to make it happen but it does happen, especially when spawning them on an incline.
Thanks in advance to whoever sees this report.
Linked issues
Attachments
Comments 5
This is not a bug, but a result of collision physics. On a zig-zag track, the minecart's path inevitably hits the adjacent blocks. Since the motion is diagonal, it is split into x and z components.
When hitting a wall, one component is reduced to 0, leaving only the other direction—effectively reducing the velocity to (1/√2.approx 0.707x) per impact. Continuous turns lead to rapid momentum loss due to these repeated collisions. This is a normal physical interaction, so it should be "Works as Intended."
Apologies, I overlooked a key detail in my previous comment. The issue reported in MCPE-190781 does exist. In certain cornering scenarios, the motion isn't split between X and Z, but is instead focused entirely on one axis (either X or Z). If that axis hits a block, the velocity drops to zero instantly.
The gradual deceleration I described earlier should be the expected behavior, but the 'instant stop' at specific positions as reported is indeed an anomaly.
One more addition: this is unrelated to MCPE-225691. Factors like direction or whether there are other minecarts nearby do not matter; the instant stop occurs at random positions regardless.
To clarify what I mean by 'expected behavior': comparing the two tracks in my video, it is clearly visible that the minecart on the top row (which hits the wall) moves slower than the one on the bottom row (which does not hit the wall), excluding the MCPE-225691 bug.
Does this only happen when other minecarts are nearby? Does it only happen in certain directions?