Mobs max spawn radius is now 44 blocks at all sim distance
The fix to MCPE-79359 makes no mobs spawn beyond a radius of 44 blocks. According to the 1.16.20 changelog and tweets from Mojang representatives this is not supposed to happen when the simulation distance is set at 6 or greater. R44 is intended behavior only on sim 4 but it occurs at all simulation distances.
To test:
- Create a flat world with sim 6 or greater
- Repeat command block with: execute @e[type=creeper] ~~~ setblock ~ ~-1 ~ concrete 0
- From the above block -> chain command block with: kill @e[type=creeper]
- Repeat command block: kill @e[type=!creeper]
- Afk and check that nothing spawns beyond r44
This issue has a severe impact on mob farms: the area of a circle with r54 is 9161 and with 44 is 6082, minus the area of a circle with 24 = 1809, that's a loss of 42%
Linked Issues
Created Issue:
Mobs max spawn radius is now 44 blocks at all sim distance
The solution of this ticket https://bugs.mojang.com/browse/MCPE-79359 have an undesired side effect when the simulation distance is set at 6 or greater and makes no mob can spawn beyond a radius of 44 blocks. This is the intended behavior on sim 4 but its present on all of them.
To test:
- Create a flat word
- Repeat command block with: execute @e[type=creeper] ~~~ setblock ~ ~-1 ~ concrete 0
- From the above block -> chain command block with: kill @e[type=creeper]
- Repeat command block: kill @e[type=!creeper]
- Afk and check that nothing spawns beyond r44
This issue have a severe impact on mob farms: the area of a circle with r54 is 9161 and with 44 is 6082, minus the area of a circle with 24=1809, thats a loss of 42%
The solution of this ticket
https://bugs.mojang.com/browse/MCPE-79359have an undesired side effect when the simulation distance is set at 6 or greater and makes no mob can spawn beyond a radius of 44 blocks. This is the intended behavior on sim 4 but its present on all of them.
To test:
- Create a flat word
- Repeat command block with: execute @e[type=creeper] ~~~ setblock ~ ~-1 ~ concrete 0
- From the above block -> chain command block with: kill @e[type=creeper]
- Repeat command block: kill @e[type=!creeper]
- Afk and check that nothing spawns beyond r44
This issue have a severe impact on mob farms: the area of a circle with r54 is 9161 and with 44 is 6082, minus the area of a circle with 24=1809, thats a loss of 42%
The solution of this ticket
MCPE-79359have an undesired side effect when the simulation distance is set at 6 or greater and makes no mob can spawn beyond a radius of 44 blocks. This is the intended behavior on sim 4 but its present on all of them.
To test:
- Create a flat word
- Repeat command block with: execute @e[type=creeper] ~~~ setblock ~ ~-1 ~ concrete 0
- From the above block -> chain command block with: kill @e[type=creeper]
- Repeat command block: kill @e[type=!creeper]
- Afk and check that nothing spawns beyond r44
This issue have a severe impact on mob farms: the area of a circle with r54 is 9161 and with 44 is 6082, minus the area of a circle with 24=1809, thats a loss of 42%
The solution of this ticket
MCPE-79359have an undesired side effect when the simulation distance is set at 6 or greater and makes no mob can spawn beyond a radius of 44 blocks. This is the intended behavior on sim 4 but its present on all of them.
To test:
- Create a flat word with sim 6 or greater
- Repeat command block with: execute @e[type=creeper] ~~~ setblock ~ ~-1 ~ concrete 0
- From the above block -> chain command block with: kill @e[type=creeper]
- Repeat command block: kill @e[type=!creeper]
- Afk and check that nothing spawns beyond r44
This issue have a severe impact on mob farms: the area of a circle with r54 is 9161 and with 44 is 6082, minus the area of a circle with 24=1809, thats a loss of 42%
The solution of this ticket
MCPE-79359have an undesired side effect when the simulation distance is set at 6 or greater and makes no mob can spawn beyond a radius of 44 blocks. This is the intended behavior on sim 4 but its present on all of them.
To test:
- Create a flat world with sim 6 or greater
- Repeat command block with: execute @e[type=creeper] ~~~ setblock ~ ~-1 ~ concrete 0
- From the above block -> chain command block with: kill @e[type=creeper]
- Repeat command block: kill @e[type=!creeper]
- Afk and check that nothing spawns beyond r44
This issue have a severe impact on mob farms: the area of a circle with r54 is 9161 and with 44 is 6082, minus the area of a circle with 24=1809, thats a loss of 42%
The
solution of this ticketMCPE-79359have an undesired side effect when the simulation distance is set at 6 or greater and makes no mob can spawn beyond a radius of 44 blocks. This is the intended behavior on sim 4 but its present on all of them.
To test:
- Create a flat world with sim 6 or greater
- Repeat command block with: execute @e[type=creeper] ~~~ setblock ~ ~-1 ~ concrete 0
- From the above block -> chain command block with: kill @e[type=creeper]
- Repeat command block: kill @e[type=!creeper]
- Afk and check that nothing spawns beyond r44
This issue ha
vea severe impact on mob farms: the area of a circle with r54 is 9161 and with 44 is 6082, minus the area of a circle with 24=1809, thats a loss of 42%
The fix to
MCPE-79359makes no mobs spawn beyond a radius of 44 blocks. According to the 1.16.20 changelog this is not supposed to happen when the simulation distance is set at 6 or greater. R44 is intended behavior only on sim 4 but it occurs at all simulation distances.To test:
- Create a flat world with sim 6 or greater
- Repeat command block with: execute @e[type=creeper] ~~~ setblock ~ ~-1 ~ concrete 0
- From the above block -> chain command block with: kill @e[type=creeper]
- Repeat command block: kill @e[type=!creeper]
- Afk and check that nothing spawns beyond r44
This issue has a severe impact on mob farms: the area of a circle with r54 is 9161 and with 44 is 6082, minus the area of a circle with 24 = 1809, that's a loss of 42%
The fix to
MCPE-79359makes no mobs spawn beyond a radius of 44 blocks. According to the 1.16.20 changelog and Mojang representatives this is not supposed to happen when the simulation distance is set at 6 or greater. R44 is intended behavior only on sim 4 but it occurs at all simulation distances.To test:
- Create a flat world with sim 6 or greater
- Repeat command block with: execute @e[type=creeper] ~~~ setblock ~ ~-1 ~ concrete 0
- From the above block -> chain command block with: kill @e[type=creeper]
- Repeat command block: kill @e[type=!creeper]
- Afk and check that nothing spawns beyond r44
This issue has a severe impact on mob farms: the area of a circle with r54 is 9161 and with 44 is 6082, minus the area of a circle with 24 = 1809, that's a loss of 42%
The fix to
MCPE-79359makes no mobs spawn beyond a radius of 44 blocks. According to the 1.16.20 changelog and tweets from Mojang representatives this is not supposed to happen when the simulation distance is set at 6 or greater. R44 is intended behavior only on sim 4 but it occurs at all simulation distances.To test:
- Create a flat world with sim 6 or greater
- Repeat command block with: execute @e[type=creeper] ~~~ setblock ~ ~-1 ~ concrete 0
- From the above block -> chain command block with: kill @e[type=creeper]
- Repeat command block: kill @e[type=!creeper]
- Afk and check that nothing spawns beyond r44
This issue has a severe impact on mob farms: the area of a circle with r54 is 9161 and with 44 is 6082, minus the area of a circle with 24 = 1809, that's a loss of 42%
relates to
relates to
relates to
relates to
relates to
is duplicated by
This issue has changed in some ways since originally reported. Here is a summary.
Main problem:
Mob spawning and despawning rules were changed 1.16.0 to fix MCPE-21856 and bring Bedrock closer to parity with Java. The changes had unintended effects:
- higher overal mob density in the nether compared to Java Edition
- high frequency of mobs respawning very close to the player after the player kills nearby mobs
- due to ^^, increased impact of pre-existing bugs that affect spawning and player experience (
MCPE-133687,MCPE-46540,MCPE-35222)
How the problem has changed:
- In 1.16.100 the spawn range was expanded for simulation distances higher than 4 (
MCPE-95568). This change eliminated the problem with spawn density and frequency for simulation distances higher than 4. (see below for why the problem still affects sim 4) - Related bugs have been fixed (
MCPE-133687,MCPE-46540,MCPE-35222). It is now possible to spawn-proof as expected against magma cubes and slimes, and ghast sounds are not so irritating. - Fix attempt in 1.17.20 Previews was reverted because it made spawn density too low on simulations distances higher than 4 (
MCPE-132746).
Why the problem occurs only on simulation distance 4:
Mob spawn density is controlled by checking a 9 chunk * 9 chunk area around a spawn attempt for mobs of the same population grouping. On simulation distance 4, at least 80% of this area is always outside of the spawning and despawning range, and therefore normally does not contain any mobs. As a result, mobs tend to spawn much closer to each other and much closer to the player on simulation distance 4 compared to higher simulation distances. Based on my tests, mob density within 44 blocks of the player tends to be 50-100% higher on sim 4. (For more detail on these numbers see my comments on MCPE-132746.)
The amount of mob spawns in the Nether is insane.
It's completely unblanced:
Ghasts spawning half in blocks and hald out and one after another
Dozens of the new Pigmen in huge groups
Magma Cubes in groups of three or four
and as for skeletons - there are just way too many of them to cope with!
Not even gone near a fortress yet!
Thanks you. I created a new ticket for this MCPE-95568
I believe this is working as intended. Here is what the 1.16.100.57 changelog says:
- Mob spawn range now scales with simulation distance (
MCPE-95568)
As I read it, all this statement means is that simulation distances higher than 4 will have a wider spawn radius than what simulation 4 has. It doesn't necessarily mean that every incremental increase in simulation distance will have a corresponding incremental increase in spawn radius. Moreover, I'm not sure where you're getting the expectation of r128 spawning.
Aside from issues of interpretation, it's not clear to me what the negative impact on gameplay is here. Mobs only render within 60 blocks of the player, so we're talking about mobs you cannot see. I presume, then, that the concern is just to be able to run farms that can fit more population caps at one time. But r~96 already allows 5 independent cap chunks (chunks with 4 chunks between them), which means more monsters (80) than the Java cap allows (70, afaik).
Thank you for your report!
We're tracking this issue in MCPE-95568, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Fixed. Please check the Fix Version/s field in that ticket to see in which version this behavior was or will be fixed.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
The constant MobSpawnRules::MAX_DEFAULT_SPAWN_DISTANCE and MobSpawnRules::MAX_SPAWN_DISTANCE are now 44, which is why it affects all sim distances not just sim 4.
Because MAX_SPAWN_DISTANCE is set, behavior packs cannot increase the spawn sphere above 44.
I agree that this breaks one of the main purposes of having a simulation distance setting. There should be a relationship between simulation distance and maximum spawn radius and despawn radius.
Saw the patch notes and immediately new this would be an issue. Our server runs at 6 chunk tick distance. This is going to seriously knee cap some of our farms.
The reference to r44 only applying on sim4 has been removed from the changelog today.
A workaround if you want to bring back the 54 max spawn distance by patching the Linux 1.16.20.03 dedicated server while this gets fixed:
This sucks. 1.16.2 broke my mob farm which is 92 blocks away from me up in the air to try to prevent mobs from spawning. I use sim 14.
Below is my suggestion on how to fix this issue:
This would be equivalent to the implemention of Despawn mechanics. Where sim4 has hard-coded limitations, but the rest of the simulation distances have data-driven behaviors.
Please note - this bug breaks almost all player location bases mob/entity spawning farms. This bug affects BDS, Realms, and Local Worlds.
Isn’t the spawn radius supposed to match despawn radius? Not always be 54 blocks above sim 4?
@user-189af the despawn radius is 44 blocks only on sim4. At higher sim distances it is the lesser of simulation edge chunks horizontally or 128 blocks spherical.
Not the despawn radius. I was told that this is an intended change for the spawn radius to only be 54 instead of up to 128 on discord and its only supposed to go up to 54 block on discord. It seems off though as i did take a look at the spawning and depsawning seeing up to r128 spawning before 1.16.2. Is it only supposed to go up to r54?
@user-189af the spawn radius was only ever 54, it had been 54 on every sim distance for as long as I've been playing (so since 1.12 at least). There was never anything said about increasing it, to my knowledge. It was decreased to 44 for every sim distance in 1.16.2. This ticket was made because the original 1.16.2 changelog and other statements from Mojang said the decrease from 54 to 44 would only apply to sim4.
Not sure what discord you're referring to, but clearly someone was confused.
I've been told by mutiple discord members it's supposed to be 44 blocks. Meaning this issue is working as intended, right?
Only Mojang employees can speak for Mojang’s intentions. Look at the tweet linked in the description. The changelog agreed with the tweet when it was first published, but then was changed 2 days later, after this report was confirmed. Until Mojang resolves this report, we can’t say for sure if they intend to go by what the tweet and original changelog said, or If they intend to keep r44 as it is now.
@user-189af they have told you what is not true multiple times, ask them to get informed.
Affects 1.16.40 Hotfix.