Pistons, droppers, dispensers, observers, & redstone lamps become stuck in an on or off-state & act like solid/opaque blocks until world-reload

I just tested, and this bug is actually the SAME thing as MCPE-17354! :O (Also, affects 0.15.10.)

This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).

Thanks for closing my duplicate issue! 😃 Please update the description/title to reflect the fact that this bug also affects droppers & dispensers as well!

Also it only affects specific pistons and every time the bug happens, it will apply on the specific pistons ONLY. Kind of weird.

Reloading the world also fix the bug. Or, just simply break the corresponding redstone compoment and replace it back.

Affects 0.17.0.1. Also confirmed to affect redstone lamps. I'm guessing it probably affects note blocks, too, since they are also a redstone component block, but I haven't actually found a case of the bug happening with those yet as I haven't tested for them.

Attached a World save with a piston that becomes 'stuck'.

Open the world and toggle the lever, the top piston remains unresponsive, unless it is broken or replaced, or the obsidian is broken near to it.

While it looks like the same bug, this is actually at least two bugs squashed into a single ticket.

I have just made a fix that fixes: Pressure plate, tripwire, redstone lamp, detector rail, buttons and probably dispensers and droppers as well. What separates these from some others in this ticket is that these would not get fixed by reloading the world. In fact, what was causing this issue was the actual saving of the world. Reloading wouldn't fix it since the saved state is broken.

Pistons however is a completely different chapter.

Observers also.

The bug with pistons still happens in 1.1.2, with more than 20 at the same time

true,I put slime block on sticky piston

Cannot reproduce as of 1.2.5.15

I am having this same sort of problem with pistons on Windows 10 v1.2.5. It also seems to affect redstone torches too.

Torch in its default state:

Button was pushed and torch signal should be inverted, but it is not:

@unknown, could you provide a world download and/or some screenshots showing the surrounding circuitry? Is the issue with that particular redstone torch still occurring or did it start working again after a world reload? Does breaking and placing it fix the problem? Do you know an easy way to reproduce this behavior? Also, did you recently crash the game while playing on that world? Because that could be related to the redstone torch (and other redstone components) getting stuck in a certain state.

It seems when I load into my world it has about a 50% chance that the torch is stuck in that state. It seems to randomly change from a working state to the bugged state and vice versa just by reloading the world. I can also force it to work by breaking & replacing the affected blocks/components. But the next time I load the world there is that chance that it will not be working. It does not seem to be required to crash the game to make the redstone fail, but in case it is relevant, the crash I experience most often is when I play in fullscreen mode and then I switch applications, the game usually crashes when I switch back to Minecraft. So I just try to remember to play in windowed mode 🙂

It is probably best that I just include a copy of my world. The link to download it is here

The coordinates for the affected area are in the screenshots below.

The circuit is housed in an elevator I built for Elytra flight, it only goes up.

I have put some signs up on the affected blocks.

In the same circuit I have another block that sometimes seems to have an issue. However, it doesn't seem to happen as often as it does with the torch. The red concrete block that the cursor is over in this screenshot has the issue, although it might be more likely that it is the piston on the other side of it that may be at fault. In order to fix the issue I simply break and replace the block on each level of the elevator. This block may be difficult to test for bugs because I don't seem to be able to reproduce this specific issue very often.

Confirm Justin Reschke's downloaded world exhibits the problem described for the torch and red concrete blocks.
Tested in Windows 10 1.2.5.52.

In a first set of tests, I did a fresh import of the world save file each time. All 10 of these tests exhibited the problem of the redstone torch not turning off. I reimported the world a number of times during later testing and it continued to exhibit the problem. Then, suddenly, on one import everything worked. For me, the imported world seems to have the problem 90% or more of the time.

In a subsequent set of tests, I started with a freshly imported copy of the world. Then I saved and reloaded the world and tested the button. In a majority of these tests (> 80%), the reloaded world also exhibited the problem.

I did a final test against another freshly imported copy, I broke the torch and replaced it. This allowed the activation signal to propagate up the tower. By watching the pistons' behavior, I was able to determine that the problem with the red concrete blocks next to the pistons was still present, and if I fixed the problem for one of these it did not heal the other pistons.

I notice that the torch and its attachment block (which is also the button's attachment block) lie on opposite sides of the Z = -224 chunk boundary plane. The same plane separates the repeaters and the red concrete blocks that power the failing pistons. The direction of activation flow across the boundary is opposite for these two pairs of components. However, the signal that propagates the activation from one level to another also crosses this chunk boundary, and it's impossible to test whether that path is also broken because any method you use to insert a probe signal might heal the problem the same way breaking and replacing the redstone torch does.

The coordinate Z = -224 is also used as the boundary for the ticking area named SlimeFarm. However, removing the ticking area did not seem to make any difference, either immediately or after saving and reloading the world, so this is likely a coincidence.

I tested this in 1.2.10.2 on Windows 10 using the "Stuck Piston.mcworld" file. The piston is indeed stuck in the saved file, but I couldn't get it to get stuck again after saving and reloading about 10 times. However, I did notice that after you flip the toggle lever a couple of times, the top piston is no longer synchronized with the other two in terms of when it extends. This indicates a completely different problem with timing, which might be a different bug.

Unfortunately, the original reporter's world which I had tested before is no longer available at the link he provided, so I couldn't test that.

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

Is this still an issue in the latest version?

If so, could you please include a copy of the world that is affected?

This ticket will automatically reopen when you reply.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki

I am no longer seeing the issue. I re-tested the same world in the latest version 1.2.13 and the redstone worked as it should even after re-loading the world many times.

Resolving the ticket as fixed based on the comments above.