I use a third party software to detect where slime chunks are on a given seed and when i put in my seed and found the chunk and clear it away to make a farm no slimes would spawn. the software i use only has up to 1.7.4 but i have read that no updates have affected seed generation and slime chunks, could this be a bug with the pre release of 1.8?
Linked issues
is duplicated by 8
Attachments
Comments 36
Please god, don't tell me that bug isn't corrected, I need a working slimefarm quickly, the swamplands are empty at night except if its a full moon, I'm doomed. BTW : I use MC1.8 PR 3 at the moment, will check if a slimefarm work or not quickly its my project for tonight since I need slimeballs for all my sticky pistons for my projects.
In 1.8 they spawn ultra-rare now in slime chunks. My slimefarm, which I built for 1.8 worked finde in 1.7 and now is SUPER slow.
Cannot reproduce, my slime farm in a slime chunk is working exactly as well in 1.8 (final) as it did in 1.7.10.
I did design it with the new 1.8 slime behavior in mind; any farm that depends on slimes never despawning if the player is within 128 blocks or that depends on slimes not swimming is going to be broken.
I seem to be having trouble with slime spawns.
I'm using MineAtlas to find slime chunks, and while it worked for me before, currently the chunk I'm using (chunk -10,15, X~=150 Z~=250).
I cleared that chunk down to level 10 and did try my best to light up the caves around, but still nothing spawned there.
Still, it's possible something else is interefering with the spawns, like mobs in other caves...
Okay, something is definitely off.
I tested it by hollowing a slime chunk in the middle of an ocean, standing 40 blocks away (out of spawn block zone) and then repeatedly killing other mobs via commands. No slimes spawned.
The world has been generated in 1.12, but it was MCEdit'ed later. I dunno if it's relevant.
Confirmed in 1.13.2 and 19w09a. I used superflat to confirm that slimes will only spawn when other hostile mobs can't.
Cannot Reproduce, but I will leave this open since this has been reported a couple of times already.