Vegard Bakke
- vbakke
- vbakke
- Europe/Stockholm
- Yes
- No
1 issues
Key
Summary
Status
Reporter
Assignee
Created
MCPE-5248Changed Description:
Both in Survival and Creative, animals get stuck in deep water.
Easiest way to reproduce
- In Creative:
- Start new world
- Go near the shore
- Spawn lots of sheep or cows onshore
- Fly up and watch
Naturally lots of the animals end up in the water. But some of them get stuck in the same position. They can turn, and bob, but don't seem to move.Sometimes by knocking the animal, it starts moving, and can swim around.
- In Survival:
- Start new world
- Run around until you find some animals near the shore
- Climb up into a tree and watch.
Same here. Some animals get stuck in the same position. They can turn, and bob, but don't seem to move.This issue is a duplicate of
MCPE-992, but that issue has not been updated with affected version since 0.6.1. Please updateMCPE-992before you close this issue.(I tested on Xperia Z, but according to the comments in
MCPE-992, it is not device dependant..)
I can confirm that cows, pigs, sheep and chickens stay in the water in version 0.7.2 alpha.
(Only on rare occasions, a couple of them manage to exit the water themselves.)
The bug still applies to v.0.7.4.
By the way,
MCPE-992is the highest voted PE issue.Please please please fix....
It's a bit silly herding your sheep with a snorkel instead of a crook
Yiihaaaa! We're all looking forwards to go shearing the sheep and still keep our boots dry!
Thank you! : )))
Please, if proper AI handling is too much work to make it into 0.8, then please make a quick fix in 0.8.
If any mob falls into water, and a land block is nearby, make the mob go to the land block and not to another water block.
Won't be as realistic, but at least the most voted bug can be ticked as fixed. Then improvements can be added in 0.9.
The shipped version of log4j-core-2.14.1.jar may be patched. But I get security alerts and our IT security will remove this file.
Not only is the shipped log4j version listed as a vulnerable version.
It contains org\apache\logging\log4j\core\lookup\JndiLookup.class.
If you fingerprint the jar-file, it has even been tampered with.(Oops. Sorry. I crisscrossed)And the JAR-file still containes the vulnerability, (even if Minecraft may be blocking the exploits).
Lot's a reasons that a security scanner will identify the shipped jar file as a security risk.
I don't understand why we can't upgrade to a known not-vulnerable version og log4j.
Best regards : )
My solution is to delete the jar file after every time I've played, to avoid being called up by the security next time they scan.
Not ideal, but works