-
Bug
-
Resolution: Unresolved
-
None
-
Minecraft 17w50a, Minecraft 18w01a, Minecraft 18w02a, Minecraft 18w07c, Minecraft 1.13-pre2, 1.15.2, 1.16.2, 1.16.4, 20w46a, 20w51a, 21w03a, 1.16.5, 21w05b, 21w07a, 1.17 Pre-release 1, 1.17.1, 1.19.2, 1.21.1, 24w36a, 1.21.3
-
Confirmed
-
Redstone
-
Normal
-
Platform
Usually when a powered rail, detector rail or activator rail gets destroyed it sends out block updates to the blocks diagonally below it.
In 17w50a, when you have a powered/detector/activator rail and you push it away with a piston, then it does not send out block updates diagonally below it.
This can cause some blocks to get into invalid states.
In Rail before.png you see a contraption. If you flick the lever, then you get Rail after.png . In this picture the powered rail on the lower block is in an invalid state because it´s on even though it is not powered by anything. That rail should have been updated when the upper powered rail was pushed away, but it wasn´t.
(Also this is not a duplicate of MC-96224, because the bug I´m describing here was newly introduced in the 1.13 snapshots and didn´t exist before, while MC-96224 is older, and secondly this bug is about block updates missing when a rail starts being pushed, while MC-96224 is about block updates missing when a rail finishes being pushed).
——
This affects the following situations:
- powered rails do not update their powered state
- stairs do not update the shape
- fences/walls/glass panes/iron bars do not update connections
- support requiring blocks do not drop
- gravity affected blocks do not fall
- activated detector rails do not unpower redstone dust
- redstone stays attached to wall
- is duplicated by
-
MC-123448 floating sand with piston and fence
- Resolved
-
MC-123449 pistons pulling moving blocks do not properly update surrounding blocks
- Resolved
-
MC-123451 bed does not delete when retrieving blocks under it with piston
- Resolved
-
MC-123452 stair remain in rotated state when spam pushed with piston
- Resolved
-
MC-123922 stair block does not update after retracted with piston
- Resolved
-
MC-125831 Redstone dust rendering on sides of blocks when the redstone has been disconnected
- Resolved
-
MC-131332 Redstone staying on walls
- Resolved
-
MC-137137 Blocks powered from detector rails remain powered when rail is moved
- Resolved
-
MC-168724 Floting Sand
- Resolved
-
MC-197927 Piston being able to hold up an unsupported falling block
- Resolved
-
MC-198422 Gravity blocks not falling when pushed by pistons
- Resolved
-
MC-203724 Floating sand placing while two pistons pushing at once
- Resolved
-
MC-234794 Floating Gravity Blocks
- Resolved
- relates to
-
MC-96224 Activated detector rails moved by pistons do not update redstone correctly
- Open
-
MC-138455 Sticky pistons failing to pull slime/honey blocks do not update blocks
- Open
-
MC-276157 Floating rails can be created with a certain setup
- Open
-
MC-122785 Powered rails and activator rails do not transmit power downwards or upwards when placed next to a power source
- Resolved
-
MC-124808 Blocks don't pop off when their support blocks are moved by pistons
- Resolved
-
MC-11193 The order in which powerable blocks (e.g. redstone dust blocks) along a wire are powered or de-powered is not clearly defined and causes a non-deterministic behavior for redstone contraptions
- Open
-
MC-174864 Rails update other rails before checking if they are in a valid location when moved by pistons
- Open
-
MC-122270 Pushing blocks with connections doesn't update them
- Resolved