Piston monostable circuits no longer work. I do not care if this is technically working as intended or not, it needs to be reverted back. There are so many redstone builds that no longer work because of this issue.
Attachments
Comments




The piston timings seem to have changed. This seems to be happening because extension happens sooner (compared to the red stone update). Related issue: MCPE-27040 seems to be happening because retraction happens sooner (compared to red stone update).

The piston timings seem to have changed. This seems to be happening because extension happens sooner (compared to the red stone update). Related issue: MCPE-27040 seems to be happening because retraction happens sooner (compared to red stone update).

The piston timings seem to have changed. This seems to be happening because extension happens sooner (compared to the red stone update). Related issue: MCPE-27040 seems to be happening because retraction happens sooner (compared to red stone update).

The piston timings seem to have changed. This seems to be happening because extension happens sooner (compared to the red stone update). Related issue: MCPE-27040 seems to be happening because retraction happens sooner (compared to red stone update).

Is it possible redstone timings could be sped up? And I'm talking just the redstone, not the pistons. I'm actually kinda glad to hear pistons are now faster. But now, it seems they're a bit too fast.

Is it possible redstone timings could be sped up? And I'm talking just the redstone, not the pistons. I'm actually kinda glad to hear pistons are now faster. But now, it seems they're a bit too fast.

Is it possible redstone timings could be sped up? And I'm talking just the redstone, not the pistons. I'm actually kinda glad to hear pistons are now faster. But now, it seems they're a bit too fast.

Is it possible redstone timings could be sped up? And I'm talking just the redstone, not the pistons. I'm actually kinda glad to hear pistons are now faster. But now, it seems they're a bit too fast.

If I recall, it seemed that MCPE Piston Timings were always a bit slower than the JAVA version of the game. It may require timing adjustments. Haven't played in my redstone world for a bit so I probably should go check the doors and traps.

If I recall, it seemed that MCPE Piston Timings were always a bit slower than the JAVA version of the game. It may require timing adjustments. Haven't played in my redstone world for a bit so I probably should go check the doors and traps.

If I recall, it seemed that MCPE Piston Timings were always a bit slower than the JAVA version of the game. It may require timing adjustments. Haven't played in my redstone world for a bit so I probably should go check the doors and traps.

If I recall, it seemed that MCPE Piston Timings were always a bit slower than the JAVA version of the game. It may require timing adjustments. Haven't played in my redstone world for a bit so I probably should go check the doors and traps.

From https://minecraft.net/en-us/article/you-made-better-together-better-ever:
Pistons in Bedrock have different timing from other versions of the game and this can mess with redstone machines imported from the legacy Console Edition. Somebodyβs going to be changing something no matter which timing we decided to go with in this case, so we opted to go with the choice that felt right to us and causes the least amount of players to have to redo their creations. TL;DR- redstone machines that rely on piston timing and are in worlds imported from Xbox legacy Console Edition will likely need reworking.
They mention Console specifically, so I'm not sure what changes, if any, apply to MCPE though.

From https://minecraft.net/en-us/article/you-made-better-together-better-ever:
Pistons in Bedrock have different timing from other versions of the game and this can mess with redstone machines imported from the legacy Console Edition. Somebodyβs going to be changing something no matter which timing we decided to go with in this case, so we opted to go with the choice that felt right to us and causes the least amount of players to have to redo their creations. TL;DR- redstone machines that rely on piston timing and are in worlds imported from Xbox legacy Console Edition will likely need reworking.
They mention Console specifically, so I'm not sure what changes, if any, apply to MCPE though.

From https://minecraft.net/en-us/article/you-made-better-together-better-ever:
Pistons in Bedrock have different timing from other versions of the game and this can mess with redstone machines imported from the legacy Console Edition. Somebodyβs going to be changing something no matter which timing we decided to go with in this case, so we opted to go with the choice that felt right to us and causes the least amount of players to have to redo their creations. TL;DR- redstone machines that rely on piston timing and are in worlds imported from Xbox legacy Console Edition will likely need reworking.
They mention Console specifically, so I'm not sure what changes, if any, apply to MCPE though.

From https://minecraft.net/en-us/article/you-made-better-together-better-ever:
Pistons in Bedrock have different timing from other versions of the game and this can mess with redstone machines imported from the legacy Console Edition. Somebodyβs going to be changing something no matter which timing we decided to go with in this case, so we opted to go with the choice that felt right to us and causes the least amount of players to have to redo their creations. TL;DR- redstone machines that rely on piston timing and are in worlds imported from Xbox legacy Console Edition will likely need reworking.
They mention Console specifically, so I'm not sure what changes, if any, apply to MCPE though.

Fixed as of 1.2.2.

Fixed as of 1.2.2.

Fixed as of 1.2.2.

Fixed as of 1.2.2.
Thank you for your report!
However, this issue is a Duplicate of MCPE-16641.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
π Issue Guidelines β π¬ Community Support β π§ Customer Support β π Game Wiki
Thank you for your report!
However, this issue is a Duplicate of MCPE-16641.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
π Issue Guidelines β π¬ Community Support β π§ Customer Support β π Game Wiki
Thank you for your report!
However, this issue is a Duplicate of MCPE-16641.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
π Issue Guidelines β π¬ Community Support β π§ Customer Support β π Game Wiki
Thank you for your report!
However, this issue is a Duplicate of MCPE-16641.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
π Issue Guidelines β π¬ Community Support β π§ Customer Support β π Game Wiki

This isn't a duplicate of MCPE-16641. The mechanism here does not try to power the piston from the front, instead what powers the piston is the block to the side (which is weakly powered by the redstone dust on top of it). This mechanism works correctly in build 1.2.2.3.

This isn't a duplicate of MCPE-16641. The mechanism here does not try to power the piston from the front, instead what powers the piston is the block to the side (which is weakly powered by the redstone dust on top of it). This mechanism works correctly in build 1.2.2.3.

This isn't a duplicate of MCPE-16641. The mechanism here does not try to power the piston from the front, instead what powers the piston is the block to the side (which is weakly powered by the redstone dust on top of it). This mechanism works correctly in build 1.2.2.3.

This isn't a duplicate of MCPE-16641. The mechanism here does not try to power the piston from the front, instead what powers the piston is the block to the side (which is weakly powered by the redstone dust on top of it). This mechanism works correctly in build 1.2.2.3.

I can confirm it is working in 1.2.2.3

I can confirm it is working in 1.2.2.3

I can confirm it is working in 1.2.2.3

I can confirm it is working in 1.2.2.3