mojira.dev
MC-136051

Mob spawning ignores light level, biomes and height

Hostile mobs spawn on the surface despite light levels over 7.

 

Testing methodology:  Create a new superflat world.  To avoid slime spawns, I set dirt height to 64, though the effect happens at the default setting of 2. 

Observation: Despite being day, hostile mobs spawn on the surface.  This also happens inside well lit closed areas as well (see attachment).

Linked issues

MC-136053 Mobs are incorrectly spawned (ignore the light level, biome and so on) Resolved MC-136054 Slime can spawn in Y=40+,even not need in swamp. Resolved MC-136056 Monsters spawning during day Resolved MC-136057 Mobs spawning in the day Resolved MC-136058 Hostile mobs spawning in daytime like its night time Resolved

Attachments

Comments 18

also slimes do not check height when spawning. Can spawn on any hight.

Entering game on peace mode and daylight, mob seems still spawning.

[media]

May also ignore biome, slime will spawn in any biome. (I am not sure whether or not only spawns on slime chunks), but slime will spawn on the surface even if it's not in the swamp.

[media]

I think biomes are still counted properly when spawning. Slimes spawn probably only on slime chunks.
Husks/strays spawn only in desert/cold biome as well.

8 more comments

I know it's fixed. Before being fixed, biomes seem not to be ignored.

I am still seeing the issue in 1.13.1

@unknown Are you sure? Mobs aren't spawning in daylight for me anymore at least.

This issue is happening for me in 1.14-pre3. It is in the desert and it seemed like mostly it was just skeletons. I could watch them spawn in and out. They were not burning and getting close enough would trigger aggro. After watching a bit more I also saw spiders and creepers and even an enderman. It seemed somehow isolated to that specific area and seemed to persist after restarting the game. It's a hardcore game, but presumably that's not a reason for it.

Just to amend this I found another bug report specific to 1.14-pre3 that wasn't well written but pointed out the "Erase Cached Data" option for worlds that had been upgraded (in my case from 1.14-pre2). Using that option completely fixed my issue.

There's a new ticket for this issue in the 1.14 pre-releases: MC-148504

capfan

migrated

Confirmed

Minecraft 18w33a

Minecraft 1.13.1-pre1

Retrieved