Trevor Kensiski

Ok so finally had some free time to mess around with the linux VM again and got it updated to 1.18.

I have noticed a few hiccups where the game kinda stutters for a second (game saving?)
Either way these stutters while a bit detracting are not ruining the experience.

That being said at the moment the performance is much better than it was back in 1.14-16

Ill continue monitoring my VM and see how it continues to preform as we explore more of the world and start doing redstone etc... As well as dig in and see if anything stands out during the stuttering issues.

VM Config

• 8 vCPU

• 32 GB Ram

• 100 GB SSD

Minecraft Config:

• ticking distance of 12

• Render Distance of 32

• 2 Players via XBOX split screen

• Threads set to 0

• Defaults for everything else

Let me know if any other settings are useful for debugging this.

I too am still experiencing this issue. Nothing has been reported since nothing has changed. Please reopen this ticket as all of the contained information and comments are relevant to the issue. We were also told not to post unless there was new information to provide so now we are getting conflicting statements...

This is happening to me as of at least 1.11. Still happening in 1.14 too.

Seems to happen to Cows, Sheep and horses. I haven't really noticed it as much with other mobs but as OP stated, this will required more testing.

From what I can infer watching the animals in my screen shot is that they wont give up pathing to a point and as such they get bunched up and end up cramming in the SW corner of any pen I create for them.

Update: Pigs are now starting to cluster too. They are less prone to it due to how the fences are placed in my village. But I definitely see them hit their farthest SW corner then change directions but get blocked by other mobs pathing there as well causing them to bunch for a bit until the entire group pushes each other around enough to free the ones who got to their point.

You can sorta see this in the Sheep and Cow pen. Notice the one crammed into the corner is facing NE heading and the rest are still trying to shove into the SW corner.

Agreed, this ruins the game if more than a single player is in the world.

I had bumped my tick-distance up to 12 on a private alpha server I run for my partner and myself. My partner and I were in our village which was THRIVING with probably close to 100 villages and I had built a few animal farms 20+ of each, sheep, cows, chickens and pigs. In total we maybe had 150 of the 200 mob cap just in our village.

The rest I believe went to cave spawns around the area over weeks of gameplay before we realized that nothing was spawning around us, not even phantoms.

Before that I had noticed my slime farm (which had a dedicated 5x5 chunk area where I lit up everything within to force the spawns in my farm) was not producing anything which seemed rather odd but figured it was due to not being close enough for them to spawn in.

In the end I figured out that the 12 chunk ticking distance was causing all mobs to stay loaded around our main village and even if I left the village while my partner stayed nothing would spawn, even if I traveled 1000's of blocks which effectively breaking the game since nothing could be spawned as I explored. Which included many villages that I ran into and everything else for that matter...

So far my solution has been to turn the tick-distance down back to 4, which sucks since I was using the higher tick distance for redstone projects... However this is still not a cure but it seems to at least keep things spawning around the game...

Can confirm this is occurring with my worlds as well, New and existing.

Survival - Normal game settings, seems to be worse on hard.

Pretty easy to reproduce, just wander around and you will start to see them. Seems like Creepers, Zombies and Skeletons spawn up on trees now.

I also have experienced this issue a few times. I am unsure of how to reproduce as it happened randomly upon joining the world. This was a local game on my Xbox One X.

Edit: Noticed that this tracks the issue first: https://bugs.mojang.com/browse/MCPE-38374