The bug
All mobs recognize bottom half slabs as air blocks and therefore
can't pathfind on them if there are no blocks below them
try to pathfind through them when they can't
How to reproduce
Create a void world
Replace the starting platform by either lower slabs or air
Build the test setup from the screenshots
and/or
(armor stand marks player position)
Go to where the armor stand is located in the screenshots above
Switch to survival mode
In the first setup, the zombie will only be able to walk towards the player until the stone blocks end. In the second setup, the zombie will take the path that goes straight towards the player and gets stuck in the stone slab.
There are a few videos attached to this report which also showcase this issue.
Original report
Mobs wont pathfind on only slabs when there is a block underneath its fine like in clip 1.
When there is a gap they will only pathfind when the blocks underneath them are connected to the blocks they want to go(clip 3).
I think they don't see slabs as blocks they can pathfind over, they think they fall through them.
Related issues
is duplicated by
relates to
Attachments
Comments


See MC-92466

I can confirm this issue. Also, @Matthew I don't think it's related to MC-92466.

Can also confirm.

confirmed for 18w48b

19w06a affected

Confirmed on 19w06a

i apparently have a similar issue on 1.11.0.5 in the Bedrock edition where mobs often try to jump over fences and slabs to pathfind.
(sorry if i posted it in the wrog place, i don't know how to report Minecraft Bedrock issues.)

Wilker, this is where you report Minecraft Bedrock issues
https://bugs.mojang.com/projects/MCPE/summary

19w13a affected

1.14 pre2 affected

1.14 pre4 affected
[media]

1.14 affected

fixed on 1.14.1 pre 1

Mobs start jumping when they go near vertical placed trapdoors, they start jumping thinking its a full block, same with slabs, stairs, fences etc.

it's still fixed in 1.14.1 pre 2
Behaviour described by Damir might be related to this bug though.
@unknown, see MC-92466
Can confirm, this has been fixed in 1.14.1 Pre-Release 1! 🎉 Here's a very interesting video about this bug being tested.