Camels will not pathfind over 1.5 high blocks
Camels have the ability to step over 1.5 high blocks, but they never want to.
Expected:
Camels would naturally climb over 1.5 high blocks as they wander on their own.
Created Issue:
Camels will not pathfind over 1.5 high blocks.
Camels have the ability to step over 1.5 high blocks, but they never want to.
Expected:
Camels would naturally climb over 1.5 high blocks as they wander on their own.
Camels will not pathfind over 1.5 high blocks.
relates to
The Bug
Camels have the ability to walk over 1.5-tall blocks because of their height and long legs. When you ride them, they instantly walk over fences or blocks with a slab on them. However, they wouldn't idly path find over these blocks.
MC-256463 fixed this issue for fences; camels can walk over any fence without player input. However this was not fixed for a block with a slab on it, despite camels being able to easily clear them when ridden.
This video displays said behavior: CamelPathfind.mp4![]()
-----------------------------------------------------------------
Steps to reproduce:
1. Build and enclosure of fences, then spawn a camel within. It will easily walk out and escape.
2. Build a similar enclosure but with a block and a slab instead of fences. Despite being the same height and the camel being able to walk over them, it wont attempt to and will remain trapped.
Similar to MC-256463 (as of fixed in 22w44a), MC-259271 & MCPE-164906. Seems that not Pathfind in any fences


Although this was fixed and camels can indeed pathfind over fences and walls now, they still cannot pathfind over a block with a slab on it in 1.19.3 Pre-2, which is of a similar height. Is this intended? The original bug report had similar pictures to this.
I ask because a block with a slab is something they also automatically go over when riding them, just like fences. Whether or not they can go over them via riding or pathfinding is now inconsistent between this set up and walls/fences
Can confirm it's not fixed if this isn't inentional
Can confirm previous comment's behavior applies to 1.19.3 as well
Would it be best to report the previous comments as a new bug?
Yeah, I suggest making a new report for it; this would essentially a different situation that needs to be detected.