This may be an old bug, but I notieced it in update 1.14.20, when I was designing mob transport system using water streams.
I have done a bunch of testing (mainly in 1.14.30 on my android 8.0 phone, but I hesitate that this is a device based problem) and I found out that:
Zombies and Villagers are able to stay at the same spot in flowing water stream, if they are heading towards the source of water stream (pathfinding against the flow) - their momentum has the same energy as the flowing water, so they will not move at all until they change the direction of pathfinding.
Drowneds are affected mostly the same way, but sometimes they do not even need to go against water stream.
Strangly enought, this bug does not affect neither the Zombie villagers or Zombie pigmen (and also husks, as I've found out later)
Husks are completely broken. They DO NOT need to even try to move. They are just ignoring the water flow entirely. Or that is what I thought. I find out that they are just for some reason taller that 2 blocks (I was testing it in two blocks high and one block wide tunnel) Husks are currently something like 2.2 blocks high. Within further testing I have found out, that they after all have no issues with pathfinding in water. By their increased high si indeed a problem (check this reddit post I've made: https://www.reddit.com/r/Minecraft/comments/f2df53/i_have_found_out_this_what_i_consider_a_bug_for/?utm_medium=android_app&utm_source=share )
Neither of these issues apply to the baby versions of these mobs.
Linked issues
Attachments
Comments 9


You originally included husks as a mob that this (the momentum issue) affects, but then you withdrew husks after further testing. Yet you left all that stuff about husks in the description, presumably because of the issue with their 2.2 block height. That's a separate issue needing its own report. I will be ignoring the information about husks in this report.
I was not able to reproduce this issue using the information provided in 1.14.30 on Windows 10. I agree with you that it probably isn't platform dependent, so it's most likely either
A difference in how your test is set up (terrain, blocks beneath the water, distance to target, etc.) or
That momentum is variable depending on what the pathfinding target is.
Here's the setup I used. Can you provide a screenshot of your setup?
[media][media]
You can't see it very well, but in the villager test the villager was spawned next to a bed, then transported by minecart to the test setup, which is outside the village boundaries.

You originally included husks as a mob that this (the momentum issue) affects, but then you withdrew husks after further testing. Yet you left all that stuff about husks in the description, presumably because of the issue with their 2.2 block height. That's a separate issue needing its own report. I will be ignoring the information about husks in this report.
I was not able to reproduce this issue using the information provided in 1.14.30 on Windows 10. I agree with you that it probably isn't platform dependent, so it's most likely either
A difference in how your test is set up (terrain, blocks beneath the water, distance to target, etc.) or
That momentum is variable depending on what the pathfinding target is.
Here's the setup I used. Can you provide a screenshot of your setup?
[media][media]
You can't see it very well, but in the villager test the villager was spawned next to a bed, then transported by minecart to the test setup, which is outside the village boundaries.
@Auldrick
Here is the bug itself:
And here is the tested enviroment:
But I've found out, what special curcomstance caused this issue, but it sill need to be fixed, but not as urgently.
I've summoned the zombies via commands, but I've used the Mob event. Bud not finished. First time, I was testing it only with baby variants (because that's what is it made for), and, because I am lazy and I know from the past, that if I do not delete the whole spawn event (f.e.: minecraft:as_baby), just one letter or something, that it will spawn adult variants of the mob. So my final command looked exactly like: summon zombie -117 26 1246 minecraft:as_ba
So it spawned as usually adult zombie, but it was broken for some reason. After further testing, I know that mobs spawned naturally or with spawneggs or properly via commands (/command blocks) are behaving as they should. This strange glitch occurs only when you spawn adult version via commands with unfinished mobevent. At least that's what I've found out. Thanks.

@Auldrick
Here is the bug itself:
And here is the tested enviroment:
But I've found out, what special curcomstance caused this issue, but it sill need to be fixed, but not as urgently.
I've summoned the zombies via commands, but I've used the Mob event. Bud not finished. First time, I was testing it only with baby variants (because that's what is it made for), and, because I am lazy and I know from the past, that if I do not delete the whole spawn event (f.e.: minecraft:as_baby), just one letter or something, that it will spawn adult variants of the mob. So my final command looked exactly like: summon zombie -117 26 1246 minecraft:as_ba
So it spawned as usually adult zombie, but it was broken for some reason. After further testing, I know that mobs spawned naturally or with spawneggs or properly via commands (/command blocks) are behaving as they should. This strange glitch occurs only when you spawn adult version via commands with unfinished mobevent. At least that's what I've found out. Thanks.
Thank you for your report!
However, this issue has been temporarily resolved as Awaiting Response
Is this still an issue in the latest version?
If it is, please be sure to include steps to reproduce the problem:
Steps to Reproduce:
1.
2.
3.Observed Results:
(Briefly describe what happens)Expected Results:
(Briefly describe what should happen)
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Thank you for your report!
However, this issue has been temporarily resolved as Awaiting Response
Is this still an issue in the latest version?
If it is, please be sure to include steps to reproduce the problem:
Steps to Reproduce:
1.
2.
3.Observed Results:
(Briefly describe what happens)Expected Results:
(Briefly describe what should happen)
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

@Lenny Face: thank you for updating the ticket some time ago. What you determined about the summon command is being tracked at MCPE-50328, so I will resolve this ticket as a duplicate.

@Lenny Face: thank you for updating the ticket some time ago. What you determined about the summon command is being tracked at MCPE-50328, so I will resolve this ticket as a duplicate.