mojira.dev
MCPE-239545

Mobs aren’t loaded with /tickingarea command

When mobs are loaded with the /tickingarea command they still spawn outside of the loaded area.

Expected result: mobs spawn outside of simulation distance even if there loaded.

Actual result: mobs shouldn’t spawn outside of simulation distance when there loaded with /tickingarea command.

Attachments

Comments 4

Thank you for helping us improve Minecraft! We saved your files:

[media][media][media]

It is not clear what you think the problem is, and your statements seem contradictory.
Note though that new mobs will only spawn near players, not inside the tickingarea unless a player is also there.
Existing mobs inside the tickingarea will remain.

Your expected result (how the game should behave) says that "mobs spawn outside of simulation distance...".
Your "Actual result" (how the game currently behaves) seems to be more what you think should happen.
Do you have these labels reversed? Even so this seems to not match the Summary you provided.

It is also clearer if you include steps to reproduce the issue as described in the instructions.

Looking at the images, there are 16 slimes in boats (I assume these are naturally spawned). As a result those slimes will fill the cave hostile mob population control cap, which will prevent more cave hostile mob spawn within a 9x9 chunk square surrounding the slimes. However, cave hostile mobs will still be able to spawn beyond the 9x9 chunk square around the slimes, as the general mob cap hasn’t been filled. You can disable the general mob cap with having 200 mobs in the ticking area (or several hundred to a thousand chickens, as I disabled mob spawning by accident via that many chickens, although it also slowed the game’s simulation to half speed).

Overall, the behavior in the report is intentional, and the reporter needs 200 or more mobs in the ticking area to disable general mob spawning, or needs to have 16 cave hostile mobs within a 9x9 chunk square surrounding the chunks where you want to prevent spawns).

Since the reporter has not responed and I believe Memttm has clarified what the reporter was trying to say, I am resolving this report as Invalid. This is a technical gameplay issue and not a bug in the game.

If you believe there is a genuine bug that is not explained by Memttm’s comment, then you may make a new report. However, it will need to be more clear and specific than this report, with specific Steps to Reproduce the issue.

Deacon Chase Thigpen

(Unassigned)

Unconfirmed

Multiple

Switch 2

26.23 Hotfix

Retrieved