MaladjustedPlatypus
Assigned
Reported
MCPE-30514
Certain Piston-to-Piston Interactions Result in a Crash
Fixed
MCPE-28520
Observer Piston Head Loop
Works As Intended
MCPE-28260
Piston Crash Bug (Reproducible)
Fixed
MCPE-25027
Cannot place redstone components on observers.
Fixed
MCPE-23498
TNT and Creeper Explosions Do Not Drop Blocks if the Default Gamemode is Creative
Fixed
MCPE-22158
Dispenser/Dropper Bug When Item Slots Full
Fixed
MCPE-20640
Rails do not immediately take block power into account when attaching to other rails
Fixed
Comments
Source? ^
Affects 1.6.0
Affects 1.6.0
As far as I'm aware this bug is no longer present in the latest stable release.
Can we get some explanation as to why this was marked "works as intended"? In the Discord Helen herself said that it was a bug and that rock (another dev) confirmed it as such.
That would be a separate bug, redstone powering blocks it should not be powering.
This is still occurring as of 1.2.10
Odd... Perhaps the fix was reverted from the beta? That exact test case was fixed in it (the beta).
Uploaded example screenshot. A single solid block under is enough.
This fix has broken parity with Java. Before, mobs could and should have spawned on top slabs as it was a solid flush spawning surface for them. Now, mobs no longer spawn on top slabs. A proper fix would be mobs not spawning on bottom slabs, but spawning on top slabs.
I'm noticing that this bug is not reliable. After some time the ones that always crashed no longer do and some that did not crash do.
Edit: Okay it is reliable, but has an interesting property. If you build ONE of these at a time and trigger then as you build them, you can reliably trigger the crash. However, if you build the setup, then trigger some normal non-crashing setups near it (to update the region, so to speak) the setup does not crash.
Confirmed to be fully fixed using my previous test cases.
As the 'Minecraft 12_6_2017 4_15_38 PM.png' image shows, this is fixed for certain orientations, but not all.
It can delete anything (bedrock included) and in some cases transmute pistons into various stone types
Interestingly enough the randomness itself does not seem to be intended, at least not permanently. The devs themselves have mentioned that the random order is only to prevent players growing accustomed to a broken system until they can establish a proper order method.
Is the looping an internal confirmation or did a dev mention it somewhere?
Re-tested. Does not seem to be affecting 1.2.5 Beta Build 3
In the end dimension, endermen are spawning in high light levels and in non-solid blocks (carpet over string, over a block, they spawn trough the carpets). Affects 1.2.5.15
Affects 1.2.5.15 (1.2.5 Beta Build 3).
In a situation such as this where "parity" brings obvious negative consequences, why not alter Java to match Bedrock behavior instead? Allow Java raids to start during the victory celebration. Parity should seek to bring together the best elements from both codebases, not the worst.