The 1.16.0.61 beta introduces scaled instant despawn radius based on simulation distance. The radii for simulation distances 6 and 8 appear to be consistent with the forumula
(simulation_distance * 16) - 10
so that the instant despawn radius for sim 8 is 118, and the instant despawn radius for sim 6 is 86. This is consistent with the previous instant despawn radius since 1.16.0.51 beta being 54 based on the minimum simulation distance of 4. However, in 1.16.0.61, the instant despawn radius for sim 4 is 44 instead of 54. This appears to be a typo because it is inconsistent with the others, and because it causes mobs to be instantly despawned after they are spawned between r44 and r54.
Steps to reproduce
1. Set world simulation distance to 4
2. Allow a mob to spawn naturally and do not interact with it.
3. Move 44 blocks away from the mob.
Expected result
The mob stays in existence.
Actual result
The mob instantly despawns.
The attached test world contains a non-persistent creeper trapped at 0, 110, 0, and colored glass at Z = 44, 54, 86, and 118 to facilitate testing different instant despawn radii. Change the simulation distance of the world before opening it to test a particular distance.
Linked issues
is duplicated by 3
relates to 2
Attachments
Comments 25
Can confirm, I made a video testing all of the despawning ranges: https://youtu.be/vZCa7KcjT6I
While we are on the subject of despawning, I want to suggest a slight change in how despawning happens.
1) The beta documentation lists "despawn_from_simulation_edge" as a data-driven configuration option for mob despawning. I assume that this is supposed to despawn any mob that walks outside of simulation range or is in a chunk when it is taken out of simulation range. This would be a good thing. If this can be fully implemented and enabled for mobs, then I suggest that the despawning range be scaled to 16*simulation_distance, with 128 as the max. This would provide parity with Java Edition at simulation distance 8.
2) Scale the spawning distance to 16*simulation_distance-10, with 118 as the max. This would allow any mob to move 10 blocks away from a player before they instantly despawn, regardless of simulation distance.
Pretty sure this is a WAI change in the recent beta. A 44 block instant despawn range would make it so if you're in the corner of the center chunk the entire thing is still completely within the sim distance (54 extends into unloaded chunks if you're in the corner).
The despawn is WAI, perhaps. However, this bug highlights the inconsistency in the different sim distances. It does not scale consistently.
Can someone with access to the 1.16 beta code confirm that this is the difference between distance 4 and distance 6? I'm trying to understand how despawn_from_simulation edge works and interacts with realms or doesn't. Below is my best guess from testing and this thread.
Sim Distance 4 (realms)?
mobs spawn between r=24 and r=54 distance of the player (white arc)
instant despawning happens beyond r=44 (black circle), half of the spawning sphere is no longer useful.
instant despawning at simulation edge is disabled
Sim Distance 6 (not realms)?
spawning happens between r=24 and r=54 distance of the player (white arc)
instant despawning happens in the outer-most chunks, green squares.
instant despawning happens beyond r=128 (black circle, only matters vertically?)
Note that (at least in 1.14) the game will attempt to spawn mobs in all simulated chunks whose centers that are withing 96 blocks of the player, horizontally. However, the spawning will fail if the mobs are beyond r=54 of the player.
It makes sense for r128 to have a chance of despawn at certain range since the area is very large with more than 4x mob cap. TBH, 4 chunk never need 1/xxx chance of despawning since it falls within range, keeping mobs actively near the player in small area. They will be most likely insta-despawn when move away in seconds to a few minutes after they spawned. That said having despawn by chance is useless for 4 chunk simulation distance. It only need instant despawn and spawn range from the player.
Why mark something that is working as Intended, this is something that is an issue and seems like there is now more problems instead of fixing the issues they rather just push it to the side, spawning and despawning is a huge put of the game, I’m only going off what I have seen by silentwisperers video of it, but it definitely isn’t working as intended, anyways I think the new despawning and spawning should be push into another update and get a fully working system then releasing a buggy system of it and keeps breaking,
If this "Works As Intended" then perhaps we could revisit the intentions. Many people would be voting up this bug if it were still possible.
Keep in mind the Works As Intended resolution addresses the primary subject of this ticket, that the instant despawn at sim4 was reduced to r44. It does not address every possible unforeseen ramification of that change. MCPE-79359 focuses on one consequence that seems to call for further tweaking, which is beyond the scope of the original intention behind r44. You may wish to follow up with that ticket if you have information to add, and vote there to show your interest.
Here are three picture showing the despawn locations and ticking areas for sim distances of 4, 6, and 8. The player is standing at 0,0. Clearly there is an inconsistency with the scaling.
[media]
[media][media]