Please let us know when we can expect a fix here. I have tried in multiple new worlds, from multiple clients. I have yet to see a single slime anywhere.
I did build multi level platform 'farm' spaces from level 10 in multiple known slime chunks. No slimes ever spawned. My wife found ONE slime in a swamp biome while in creative mode. Switching to a non-creative mode copy, no slimes ever appeared again in that same swamp. I've tried switching to peaceful mode and back to normal and saw no changes. I've tried leaving the vicinity (1000+ blocks) of the area I'm looking for slimes in, and coming back. No slimes. I've had to resort to just cheating, which sucks.
I don't know if it makes any difference, but I have tried the following:
Android with local world and with a realm.
Windows 10 PC with a local world and a realm.
XBox One with a local world and a realm.
In the above cases, the realm was always the same realm, and world on that realm. The local worlds were all independent newly created local worlds (not copies of other worlds).
I found the same issue when attempting to clone across several thousand blocks. Obviously setting the render distance to max isn't going to help me actually get the blocks from one place to the other in such a large distance.
An actual work-around is to use /tickingarea add for either the destination or source (or both). Then you can use /clone (and I assume any other affected commands as well). If you no longer want the area to be kept ticking after cloning, just remove the area once complete.
I found the same issue when attempting to clone across several thousand blocks. Obviously setting the render distance to max isn't going to help me actually get the blocks from one place to the other in such a large distance.
An actual work-around is to use /tickingarea add for either the destination or source (or both). Then you can use /clone (and I assume any other affected commands as well). If you no longer want the area to be kept ticking after cloning, just remove the area once complete.
Confirmed this is still an issue on 1.2.9 of the Amazon Store version.
I have tried two different controllers on two different Fire tablets. The right stick, A B X Y buttons, shoulder bumpers, and triggers do NOT work. The left stick works except for down click.
Tablets:
7" 2015 (5th Gen)
HD 10, 7th Gen, 2017
Note: both of the controllers work just fine on non-Amazon phone/tablets. They also work fine in other games running on the Fire tablets.
I am affected by this issue with no slimes.
Please let us know when we can expect a fix here. I have tried in multiple new worlds, from multiple clients. I have yet to see a single slime anywhere.
Thanks for the feedback Auldrick.
I did build multi level platform 'farm' spaces from level 10 in multiple known slime chunks. No slimes ever spawned. My wife found ONE slime in a swamp biome while in creative mode. Switching to a non-creative mode copy, no slimes ever appeared again in that same swamp. I've tried switching to peaceful mode and back to normal and saw no changes. I've tried leaving the vicinity (1000+ blocks) of the area I'm looking for slimes in, and coming back. No slimes. I've had to resort to just cheating, which sucks.
I don't know if it makes any difference, but I have tried the following:
Android with local world and with a realm.
Windows 10 PC with a local world and a realm.
XBox One with a local world and a realm.
In the above cases, the realm was always the same realm, and world on that realm. The local worlds were all independent newly created local worlds (not copies of other worlds).
I found the same issue when attempting to clone across several thousand blocks. Obviously setting the render distance to max isn't going to help me actually get the blocks from one place to the other in such a large distance.
An actual work-around is to use /tickingarea add for either the destination or source (or both). Then you can use /clone (and I assume any other affected commands as well). If you no longer want the area to be kept ticking after cloning, just remove the area once complete.
I found the same issue when attempting to clone across several thousand blocks. Obviously setting the render distance to max isn't going to help me actually get the blocks from one place to the other in such a large distance.
An actual work-around is to use /tickingarea add for either the destination or source (or both). Then you can use /clone (and I assume any other affected commands as well). If you no longer want the area to be kept ticking after cloning, just remove the area once complete.
Confirmed this is still an issue on 1.2.9 of the Amazon Store version.
I have tried two different controllers on two different Fire tablets. The right stick, A B X Y buttons, shoulder bumpers, and triggers do NOT work. The left stick works except for down click.
Tablets:
Note: both of the controllers work just fine on non-Amazon phone/tablets. They also work fine in other games running on the Fire tablets.
Also - there appears to be a long history of this not working (if it ever did).
MCPE-12319MCPE-22227MCPE-27732MCPE-11769MCPE-10541(!!!! from September of 2015)MCPE-23530