mojira.dev
MC-50647

Slime mob spawners spawn slimes only in slime chunks

How to reproduce

  1. Create a superflat world with the seed: 7606204815140416435

  2. First, execute these commands: /gamerule doMobSpawning false and /kill @e[type=!minecraft:player] (untill all entities are dead)

  3. Teleport to 102 5 223 using /tp @s 102 5 223

  4. Execute the command 'Spawner 1', afterwards execute command 'Spawner 2'

  5. Observe the two spawners, only 'Spawner 1' will spawn slimes

    Spawner 1: /setblock 98 6 229 spawner{SpawnData:{id:slime},SpawnCount:2,MaxNearbyEntities:100,Delay:300,MaxSpawnDelay:500,RequiredPlayerRange:16} replace
    Spawner 2: /setblock 64 6 229 spawner{SpawnData:{id:slime},SpawnCount:2,MaxNearbyEntities:100,Delay:300,MaxSpawnDelay:500,RequiredPlayerRange:16} replace

Video proof: http://usetapes.com/v/TQQ1qEYHiC

Comments 22

/setblock ~ ~1 ~ minecraft:mob_spawner 0 destroy {EntityId:Slime,SpawnRange:5b}

Actually works fine, when added SpawnRange.

@Wojciech Drzymała : According to http://minecraft.gamepedia.com/Chunk_format SpawnRange is a short, not a byte ?!

Is it possible that slime chunks affect this? I made a void map to make sure nothing else interefered with mob spawner mechanics and could not get any spawns:

http://usetapes.com/v/fghpJAKf2e

Yes! It definitely depends on slime chunks! Used my world’s seed and http://chunkbase.com/apps/slime-finder, created a spawner in a slime chunk and boom, slimes started spawning like mad.

Aha. Probably a bug, a mob spawner should override the other spawning dependancies.

12 more comments

Can confirm in 20w48a.

Can confirm in 1.18.2 and 22w13a.

Confirmed in 1.19.2

Confirmed for 1.19.4 pre-release 1

Confirmed for 1.19.4 pre-release 3

Piotr Petrus (ridddle)

rkullenius

Confirmed

Platform

Normal

Mob spawning

chunk, slime, spawner

Minecraft 1.7.5, Minecraft 14w18b, Minecraft 1.8.9, Minecraft 15w50a, Minecraft 1.10.2, ..., 20w48a, 1.18.2, 22w13a, 1.19.2, 1.19.4 Pre-release 1

23w40a

Retrieved