MCPE-16093MCPE Crashes frequently when a minecart that is activating a detector rail and that dector rail are pushed by pistons at the same time
Whenever any minecart is on a detector rail (powering the rail) and some piston contraption causes both the minecart and the detector rail to be pushed (works fine on pull, crashes only on push) then MCPE is likely to crash. The crash does not happen every time, and with different builds, it happens more or less frequently (suggesting this bug has something to do with redstone tick order of operations).
To reproduce
- float a piston (sticky or not, doesn't matter) above the ground pushing a slime block horizontally
- attach any solid block above the slime block (so the piston will push this block because it is stuck to the slime block)
- attach any solid block on which a rail can be placed beside the slime block, in line with the piston (so the piston will push this block too)
- place a detector rail on the previously placed block (the orientation of the rail relative to the piston push direction seems to matter. If the rail points perpendicular to the direction the piston pushes, the game crashes more frequently.)
- place any minecart on the detector rail, activating it
- activate the piston by any means
- MCPE has a high probability that it will crash to menu
Note: The above build is not the most general case, but does crash with high frequency. Slime blocks are not required to reproduce this crash. You can also stack two pistons, use redstone to trigger them at the same time, place one block in front of the bottom piston, place the detector rail and minecart on that block, and activate the group of pistons. This is illustrated in the second screenshot showing the pistons and the rail pointing the same direction as the push.
Created Issue:
Crash when powered activator rail on slime block moved by piston breaks
When you place an activator rail on slimeblocks, place a minecart on the rail and then place a piston next to the slimeblock to move the slime block the rail is on the game crashes
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 10
- 0.15.1
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
Crash when powered activator rail on slime block moved by piston breaks + duplication glich
photo_2016-07-06_22-17-36.jpg
Crash when powered activator rail on slime block moved by piston breaks+ duplication glich
Crash whenpowered activator rail on slime block moved by piston breaksCrash when a detector rail on slime block moved by piston breaks
Three problems. First, I don't think your picture uses an activator rail. My picture does and it is clearly different. Two, you have not explained how that rail is powered. Three, the sticky piston won't move with the slime blocks on the grass blocks.
Crash when a detector rail on slime block moved by piston breaksMCPE Crashes everytime a minecart that is activating a detector rail are pushed by pistons at the same time
When
you place an activator rail on slimeblocks, place a minecart onthe rail andthen place a piston next to the slimeblock to move the slime block the rail is on the gamecrashesWhenever any minecart is on a detector rail (powering the rail) and some piston contraption causes both the minecart and the detector rail to be pushed (works fine on pull, crashes only on push) then MCPE will crash.
To reproduce
- float a piston (sticky or not, doesn't matter) above the ground pushing a slime block horizontally
- attach any solid block above the slime block (so the piston will push this block because it is stuck to the slime block)
- attach any solid block on which a rail can be placed beside the slime block, in line with the piston (so the piston will push this block too)
- place a detector rail on the previously placed block (the orientation of the rail relative to the piston push direction is irrelevant)
- place any minecart on the detector rail, activating it
- activate the piston by any means
- MPCE will crash to menu.
Note: The above build is not the most general case. Slime blocks are not required to reproduce this crash. You can also stack two pistons, use redstone to trigger them at the same time and then replace the slime block with any other solid block.
MCPE Crasheseverytimea minecart that is activating a detector rail are pushed by pistons at the same timeMCPE Crashes frequently when a minecart that is activating a detector rail and that dector rail are pushed by pistons at the same time
Whenever any minecart is on a detector rail (powering the rail) and some piston contraption causes both the minecart and the detector rail to be pushed (works fine on pull, crashes only on push) then MCPE
will crash.To reproduce
- float a piston (sticky or not, doesn't matter) above the ground pushing a slime block horizontally
- attach any solid block above the slime block (so the piston will push this block because it is stuck to the slime block)
- attach any solid block on which a rail can be placed beside the slime block, in line with the piston (so the piston will push this block too)
- place a detector rail on the previously placed block (the orientation of the rail relative to the piston push direction
is irrelevant)- place any minecart on the detector rail, activating it
- activate the piston by any means
- MPCE will crash to menu.
Note: The above build is not the most general case. Slime blocks are not required to reproduce this crash. You can also stack two pistons, use redstone to trigger them at the same time and
then replace the slime block with any other solid block.Whenever any minecart is on a detector rail (powering the rail) and some piston contraption causes both the minecart and the detector rail to be pushed (works fine on pull, crashes only on push) then MCPE is likely to crash. The crash does not happen every time, and with different builds, it happens more or less frequently (suggesting this bug has something to do with redstone tick order of operations).
To reproduce
- float a piston (sticky or not, doesn't matter) above the ground pushing a slime block horizontally
- attach any solid block above the slime block (so the piston will push this block because it is stuck to the slime block)
- attach any solid block on which a rail can be placed beside the slime block, in line with the piston (so the piston will push this block too)
- place a detector rail on the previously placed block (the orientation of the rail relative to the piston push direction seems to matter. If the rail points perpendicular to the direction the piston pushes, the game crashes more frequently.)
- place any minecart on the detector rail, activating it
- activate the piston by any means
- MPCE will crash to menu.
Note: The above build is not the most general case. Slime blocks are not required to reproduce this crash. You can also stack two pistons, use redstone to trigger them at the same time and place one block in front of the bottom piston, place the detector rail and minecart on that block and activate the group of pistons.
Whenever any minecart is on a detector rail (powering the rail) and some piston contraption causes both the minecart and the detector rail to be pushed (works fine on pull, crashes only on push) then MCPE is likely to crash. The crash does not happen every time, and with different builds, it happens more or less frequently (suggesting this bug has something to do with redstone tick order of operations).
To reproduce
- float a piston (sticky or not, doesn't matter) above the ground pushing a slime block horizontally
- attach any solid block above the slime block (so the piston will push this block because it is stuck to the slime block)
- attach any solid block on which a rail can be placed beside the slime block, in line with the piston (so the piston will push this block too)
- place a detector rail on the previously placed block (the orientation of the rail relative to the piston push direction seems to matter. If the rail points perpendicular to the direction the piston pushes, the game crashes more frequently.)
- place any minecart on the detector rail, activating it
- activate the piston by any means
- MPCE will crash to menu
.Note: The above build is not the most general case. Slime blocks are not required to reproduce this crash. You can also stack two pistons, use redstone to trigger them at the same time and place one block in front of the bottom piston, place the detector rail and minecart on that block and activate the group of pistons.
Whenever any minecart is on a detector rail (powering the rail) and some piston contraption causes both the minecart and the detector rail to be pushed (works fine on pull, crashes only on push) then MCPE is likely to crash. The crash does not happen every time, and with different builds, it happens more or less frequently (suggesting this bug has something to do with redstone tick order of operations).
To reproduce
- float a piston (sticky or not, doesn't matter) above the ground pushing a slime block horizontally
- attach any solid block above the slime block (so the piston will push this block because it is stuck to the slime block)
- attach any solid block on which a rail can be placed beside the slime block, in line with the piston (so the piston will push this block too)
- place a detector rail on the previously placed block (the orientation of the rail relative to the piston push direction seems to matter. If the rail points perpendicular to the direction the piston pushes, the game crashes more frequently.)
- place any minecart on the detector rail, activating it
- activate the piston by any means
- MPCE has a high probability that it will crash to menu
Note: The above build is not the most general case, but does crash with high frequency. Slime blocks are not required to reproduce this crash. You can also stack two pistons, use redstone to trigger them at the same time and place one block in front of the bottom piston, place the detector rail and minecart on that block and activate the group of pistons. This is illustrated in the second screenshot.
Whenever any minecart is on a detector rail (powering the rail) and some piston contraption causes both the minecart and the detector rail to be pushed (works fine on pull, crashes only on push) then MCPE is likely to crash. The crash does not happen every time, and with different builds, it happens more or less frequently (suggesting this bug has something to do with redstone tick order of operations).
To reproduce
- float a piston (sticky or not, doesn't matter) above the ground pushing a slime block horizontally
- attach any solid block above the slime block (so the piston will push this block because it is stuck to the slime block)
- attach any solid block on which a rail can be placed beside the slime block, in line with the piston (so the piston will push this block too)
- place a detector rail on the previously placed block (the orientation of the rail relative to the piston push direction seems to matter. If the rail points perpendicular to the direction the piston pushes, the game crashes more frequently.)
- place any minecart on the detector rail, activating it
- activate the piston by any means
- MPCE has a high probability that it will crash to menu
Note: The above build is not the most general case, but does crash with high frequency. Slime blocks are not required to reproduce this crash. You can also stack two pistons, use redstone to trigger them at the same time
andplace one block in front of the bottom piston, place the detector rail and minecart on that block and activate the group of pistons. This is illustrated in the second screenshot.Whenever any minecart is on a detector rail (powering the rail) and some piston contraption causes both the minecart and the detector rail to be pushed (works fine on pull, crashes only on push) then MCPE is likely to crash. The crash does not happen every time, and with different builds, it happens more or less frequently (suggesting this bug has something to do with redstone tick order of operations).
To reproduce
- float a piston (sticky or not, doesn't matter) above the ground pushing a slime block horizontally
- attach any solid block above the slime block (so the piston will push this block because it is stuck to the slime block)
- attach any solid block on which a rail can be placed beside the slime block, in line with the piston (so the piston will push this block too)
- place a detector rail on the previously placed block (the orientation of the rail relative to the piston push direction seems to matter. If the rail points perpendicular to the direction the piston pushes, the game crashes more frequently.)
- place any minecart on the detector rail, activating it
- activate the piston by any means
- MPCE has a high probability that it will crash to menu
Note: The above build is not the most general case, but does crash with high frequency. Slime blocks are not required to reproduce this crash. You can also stack two pistons, use redstone to trigger them at the same time, place one block in front of the bottom piston, place the detector rail and minecart on that block, and activate the group of pistons. This is illustrated in the second screenshot showing the pistons and the rail pointing the same direction as the push.
Whenever any minecart is on a detector rail (powering the rail) and some piston contraption causes both the minecart and the detector rail to be pushed (works fine on pull, crashes only on push) then MCPE is likely to crash. The crash does not happen every time, and with different builds, it happens more or less frequently (suggesting this bug has something to do with redstone tick order of operations).
To reproduce
- float a piston (sticky or not, doesn't matter) above the ground pushing a slime block horizontally
- attach any solid block above the slime block (so the piston will push this block because it is stuck to the slime block)
- attach any solid block on which a rail can be placed beside the slime block, in line with the piston (so the piston will push this block too)
- place a detector rail on the previously placed block (the orientation of the rail relative to the piston push direction seems to matter. If the rail points perpendicular to the direction the piston pushes, the game crashes more frequently.)
- place any minecart on the detector rail, activating it
- activate the piston by any means
- M
PCE has a high probability that it will crash to menuNote: The above build is not the most general case, but does crash with high frequency. Slime blocks are not required to reproduce this crash. You can also stack two pistons, use redstone to trigger them at the same time, place one block in front of the bottom piston, place the detector rail and minecart on that block, and activate the group of pistons. This is illustrated in the second screenshot showing the pistons and the rail pointing the same direction as the push.
Whenever any minecart is on a detector rail (powering the rail) and some piston contraption causes both the minecart and the detector rail to be pushed (works fine on pull, crashes only on push) then MCPE is likely to crash. The crash does not happen every time, and with different builds, it happens more or less frequently (suggesting this bug has something to do with redstone tick order of operations).
To reproduce
- float a piston (sticky or not, doesn't matter) above the ground pushing a slime block horizontally
- attach any solid block above the slime block (so the piston will push this block because it is stuck to the slime block)
- attach any solid block on which a rail can be placed beside the slime block, in line with the piston (so the piston will push this block too)
- place a detector rail on the previously placed block (the orientation of the rail relative to the piston push direction seems to matter. If the rail points perpendicular to the direction the piston pushes, the game crashes more frequently.)
- place any minecart on the detector rail, activating it
- activate the piston by any means
- MCPE has a high probability that it will crash to menu
Note: The above build is not the most general case, but does crash with high frequency. Slime blocks are not required to reproduce this crash. You can also stack two pistons, use redstone to trigger them at the same time, place one block in front of the bottom piston, place the detector rail and minecart on that block, and activate the group of pistons. This is illustrated in the second screenshot showing the pistons and the rail pointing the same direction as the push.
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
Amphy2k Try the configurations shown in MCPE-16093 without the minecart (which causes the crash).
Please post a screenshot of what you build before the crash or describe all the steps to build what you are describing. I was not able to reproduce your crash on my Samsung Galaxy S6 (SM-G920W8), Android 5.1.1 running MCPE 0.15.1.
I tried, in a new creative flat world, both sticky and regular pistons pushing from various different directions with normal minecarts on unactivated activator rails. None of my configurations crashed the game. I may have missed something, or this may just affect Win10, but we need more specific info to reproduce.
Yea sure, i actually tried to create this machine https://www.youtube.com/watch?v=nYszbiYXMvM
Actually tried to simplify it, i'll attach a new screenshot
Pushed the minecart off a bit just to show it
Hilarious, found an duplication bug also.
Maybe you should test the behaviour yourself..
Because normal rail does drop but also stays, and drops totally when retracting,
other rails instantly drop duplicated, some not when retracting,
detector rails crash when minecart is on them and moved
There's already a ticket on the rail dup by piston push.
Still confused here. I can't get the build in the screenshots to crash the game on:
Removed unnessesary screenshots.
Well, the bug only appears for me when the minecart is on the track.
I'll try different rotations now, maybe its only south or something like that
Same thing. But i realized that the minecart has to be pushed too, build it exactly like in the screenshot
Confirmed on Samsung Galaxy S6 (SM-G920W8), Android 5.1.1 but you've got the build description all wrong. I'm updating the ticket now. Next time, be VERY specific about the build so we do not waste time trying to reproduce it.
Sorry, i did only test with slime blocks.
It crashes game when button is pressed.
iPhone 6s+ ios 10 beta 7
Reconfirmed on Samsung Galaxy S6 (SM-G920W8), Android 6.0.1 MCPE 0.15.90.2.
Appears to be fixed in 0.15.90.8.