Slime spawners do not function outside areas that spawn slimes naturally
If a monster spawner is set to spawn slimes, it will fail unless located in a swamp biome or slime chunk. I expected for locational spawn requirements to be overridden by the spawners when checking spawning conditions.
Shown is a group of monster spawners in a flat world. A single cage was placed in a slime chunk, and is the only one of the three to spawn slimes.
Linked Issues
Attachments1
Comments13
History25
Added duplicates link: MC-50647Slime mob spawners spawn slimes only in slime chunksFixed
Removed duplicates link: MC-50647Slime mob spawners spawn slimes only in slime chunksFixed
Added relates to link: MC-50647Slime mob spawners spawn slimes only in slime chunksFixed
Changed description:
If a monster spawner is set to spawn slimes, it will fail unless located in a swamp biome or slime chunk. I expected for
Tested in creative mode using the 'flat' and 'infinite' worlds types, with both difficulty options.
0Shown is a group of monster spawners in a flat world. A single cage was placed in a slime chunk- this is the only one of the three to spawn slimes.
If a monster spawner is set to spawn slimes, it will fail unless located in a swamp biome or slime chunk. I expected for
Tested in creative mode using the 'flat' and 'infinite' worlds types, with both difficulty options.
0Shown is a group of monster spawners in a flat world. A single cage was placed in a slime chunk- this is the only one of the three to spawn slimes.
Changed description:
If a monster spawner is set to spawn slimes, it will fail unless located in a swamp biome or slime chunk. I expected for
Tested in creative mode using the 'flat' and 'infinite' worlds types, with both difficulty options.
0Shown is a group of monster spawners in a flat world. A single cage was placed in a slime chunk- this is the only one of the three to spawn slimes.
If a monster spawner is set to spawn slimes, it will fail unless located in a swamp biome or slime chunk. I expected for
Tested in creative mode using the 'flat' and 'infinite' worlds types, with both difficulty options.
0Shown is a group of monster spawners in a flat world. A single cage was placed in a slime chunk- this is the only one of the three to spawn slimes.
Added affects versions: 0.11.0 Beta 14 0.11.0 0.11.1
Added affects versions: 0.12.1
Added labels: awaiting_confirmation
Added affects versions: 0.12.2
Added affects versions: 0.13.0
Added affects versions: 0.14.0
Changed description:
If a monster spawner is set to spawn slimes, it will fail unless located in a swamp biome or slime chunk. I expected for
0Shown is a group of monster spawners in a flat world. A single cage was placed in a slime chunk- this is the only one of the three to spawn slimes.
If a monster spawner is set to spawn slimes, it will fail unless located in a swamp biome or slime chunk. I expected for
Added affects versions: 0.14.1
Added affects versions: 0.14.3
Added affects versions: 0.15.0 Beta build 2
Added affects versions: 0.15.1 Beta 1
Removed labels: awaiting_confirmation
Confirmation Status: Unconfirmed → Confirmed
Added affects versions: 0.15.7
Added relates to link: MCPE-16277Squids not spawning when spawn egg used in monster spawnerWorks As Intended
Added affects versions: 0.16.0
Resolution: Unresolved → Fixed
Added affects versions: 1.0.0

Duplicate of
MCPE-8248. Because of same reasons spawners not spawn them on peaceful like spawn eggs. They works ok on Normal Difficulty setting.Intended.
@Mustafa Alperen SEKİ, I was not referring to the spawning of baby slimes (see
MCPE-7996), rather, the issue of the spawner's failure to override location-related requirements.Does this bug still appear in 0.12.1? If so please respond.
Confirmed to effect 0.12.1 on iPhone 6 Plus (iOS 9.0).
I'm fairly sure this is an intended feature, the spawner needs to be placed inside a slime chunk <level 39.
Does this bug still appear in 0.12.2? If so please respond.
Comfirm on iPad 4
iOS 9.1. Affects version 0.13.0 and since 0.11.0 for my device.
Affects 0.14.3
Reported to VSO: 30756
may need to conduct further testing but appears to affect 0.15.10
I can't reproduce in 1.0.0 please comment if it still happens for you.
This is still an issue on the java edition. I don't know why it has not been fixed there yet.