mojira.dev
REALMS-11290

end_dragon_fight_ticking_area prevents mob spawning in realm

Steps to reproduce

  1. Create a world.

  2. Go to the end.

  3. Spawn 200 mobs, like sheep, or fish in an aquarium.

  4. Go back to the overworld.

  5. Explore various undeveloped areas.

Expected result

Mobs spawn.

Observed

Mobs do not spawn.


After we updated to 1.19.71 all Endermen disappeared on the main End island I'm terraforming. Ive gone in caves with zero light no mobs, the nether has no mobs, not even fish are spawning. I double checked that Mob spawning is on and the difficulty is set to hard. The only mobs that are spawning are from spawners. All villagers and animals we had before the update are still here.

Linked issues

Attachments

Comments 4

Could you attach a copy of the world to this ticket? If the world is too large to attach, you can upload it to a file-sharing site like OneDrive or Dropbox and then share the download link.

https://www.dropbox.com/s/8nn7w70f30xugdw/zombie%20-%20Copy.mcworld?dl=0

 

Here you go. I opened the copy and mobs are spawning. But they are still not spawning on the realm.

Thanks for the world. I can confirm that this issue is proximately caused by the large number of mobs you have collected in the area around the end fountain in the end dimension, including 224 tropical fish. Bedrock Edition has a global cap of 200 spawnable mobs. When this many mobs are ticked, environmental spawning does not occur.

The underlying cause is that a recent update added an automatic ticking area to the end dimension in BDS and Realms. The ticking area is called "end_dragon_fight_ticking_area" and is 21 x 21 chunks in size, stretching from -160, -160 to +175, +175.

When you load the world on a Realm this ticking area keeps those 224 fish and the other mobs in that area actively loaded, and that prevents mobs spawning anywhere else in the world. The ticking area does not get created when the world is loaded locally, so you cannot reproduce the issue in a local copy. For this reason I am transferring this report to the REALMS project and renaming it to reflect the underlying issue.

Hi

Does this issue still occur after updating to 1.20.32?

This ticket will automatically reopen when you reply.

migrated

(Unassigned)

Confirmed

Bedrock

Retrieved