Mobs max spawn radius is now 44 blocks at all sim distance

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.

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.

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.

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:

printf '\x36' | dd of=bedrock_server-1.16.20.03 bs=1 seek=$((0x000000000E4060E4 + 0)) conv=notrunc
printf '\x36' | dd of=bedrock_server-1.16.20.03 bs=1 seek=$((0x000000000C714E3E + 3)) conv=notrunc
printf '\x36' | dd of=bedrock_server-1.16.20.03 bs=1 seek=$((0x000000000C714E45 + 3)) conv=notrunc
printf '\x36' | dd of=bedrock_server-1.16.20.03 bs=1 seek=$((0x000000000C714F27 + 3)) conv=notrunc
printf '\x36' | dd of=bedrock_server-1.16.20.03 bs=1 seek=$((0x000000000C714F2E + 3)) conv=notrunc

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:

printf '\x36' | dd of=bedrock_server-1.16.20.03 bs=1 seek=$((0x000000000E4060E4 + 0)) conv=notrunc
printf '\x36' | dd of=bedrock_server-1.16.20.03 bs=1 seek=$((0x000000000C714E3E + 3)) conv=notrunc
printf '\x36' | dd of=bedrock_server-1.16.20.03 bs=1 seek=$((0x000000000C714E45 + 3)) conv=notrunc
printf '\x36' | dd of=bedrock_server-1.16.20.03 bs=1 seek=$((0x000000000C714F27 + 3)) conv=notrunc
printf '\x36' | dd of=bedrock_server-1.16.20.03 bs=1 seek=$((0x000000000C714F2E + 3)) conv=notrunc

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.

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:

1. Set MobSpawnRules::MAX_DEFAULT_SPAWN_DISTANCE to be 54.

2. Set MobSpawnRules::MAX_SPAWN_DISTANCE to be 128. (This allows behavior packs on servers running sim5 and above to increase the spawn sphere above the vanilla default, up to 128.)

3. In Spawner::_isSpawnPositionOk, check for sim distance and adjust the max spawn distance to 44 if on sim 4.

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.

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?

Isn’t the spawn radius supposed to match despawn radius? Not always be 54 blocks above sim 4?

@@unknown 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.

@@unknown 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?

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?

@@unknown 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.

@@unknown 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?

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.

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.

@@unknown they have told you what is not true multiple times, ask them to get informed.

@@unknown they have told you what is not true multiple times, ask them to get informed.

Affects 1.16.40 Hotfix.

Affects 1.16.40 Hotfix.