When moving blocks with pistons they change their behaviors while being moved.
In some - not all - cases it would make sense and remove some bugs if the moving block took some of the properties of the block inside it.
Here is an incomplete list of the properties that could be considered.
⚠️ Please note that each of these should be well thought about and discussed, as there is also great potential to introduce new bugs.
Behavior | Related Issues | Comment |
|---|---|---|
Light opacity | Can cause flickering and a waste of performance due to unnecessary light updates in flying machines | |
Solid top | Could fix Rails popping out on finishing moving, returning solid for the moving block seems odd though, because when it starts moving there is certainly no solid top on the target side | |
Solid/Transparent block | Would break a well known and used redstone behavior | |
Visual Transparency | ||
Slipperiness | Basically just matters for ice, but would make sense | |
OnFallenUpon Behavior | MC-89043 (not the same cause) | e.g. slimeblocks should bounce players up while moving |
Blast resistance | Sometimes used to easily break blocks, kind of a cool quirk | |
Redstone power output | Frequently used redstone behaviour | |
Emitted light | ||
3rd person camera behavior | ||
Sculk sensor vibration blocking | ||
Block material/note block instrument | ||
Tinted glass for beacon beam color | beacons cannot quickly change colors with fast pistons |
❓ What else could be considered?
Another option would be to start using the holding block's behaviors once the block moved half the way, but it seems odd and might not be supported by the underlying structure to have changing behaviors without changing the block state like that.
:info: These issues are generally not vitally important, however I think they are worth considering for potential systematic changes regarding moving blocks.
Related issues
is duplicated by
MC-1922
Redstone-lamp
MC-3667
Light-emitting blocks don't emit light while being moved by a piston, causing flickering
MC-24548
Glowstone does not produce light when pushed by a piston
MC-54411
Player takes damage when jumping on moving slimeblocks
MC-54736
Slime Block fall damage
MC-65165
Fall damage not negated by slime blocks pushed by pistons
MC-78385
Slime blocks still giving fall damage
MC-107132
slime blocks on active pistons cause fall damage and weird stomp noises when bouncing on them.
MC-112649
Bouncing on a piston slime block setup accumulates fall damage
MC-139400
Lantern light level drops to 0 while being moved with a piston
MC-147777
Beacon beam turns white when a block above is moved by a piston.
MC-149538
Light emitting blocks causes light bug when moved in the new light engine
MC-158003
Glass texture shows through other glass blocks when moving
MC-172456
Ancient debris explodes while being moved by a piston
MC-172832
Netherite block and ancient debris isn't blast resistance when pushed/pulled
MC-188035
You can jump normally on moving honeyblocks
MC-191256
Pistons with Slime Blocks still bounce players inconsistently.
MC-200917
Blocks lose their property when an entity
MC-209468
An explosion of ancient debris.
MC-213587
Wool doesn’t incur vibrations when being pushed by a piston
MC-215425
Shroomlight light disappears while the block is in movement
MC-216111
21w07a Netherite block explodes
MC-217139
Ancient debris blocks exploding
MC-222219
tnt destroy every piston movable blocks (netherite blocks)
MC-228913
Sculk sensor react when a piston hidden by a wool block push this wool block
MC-233929
Piston moving glass does not make camera pass through
MC-261397
Explosion resistant blocks break when pushed by pistons and surrounding blocks are no longer protected by blast resistant blocks
MC-263743
Rain does not appear underneath moving_piston block
MC-267525
Inconsistent observer behavior when moved
relates to
Attachments
Comments
migrated
migrated
Relates to MC-93631.
FaRo1
This also includes moving a redstone block from next to one redstone dust to being next to another redstone dust (which are connected), right?
Panda4994
Yes.
I'm not sure if it should be like that, but that's true for many of the things listed here. In some cases issues can be avoided by passing the properties of the block it holds through, in other cases it is probably for the best to let moving block have their own properties.
migrated
Might want to add "redstone power output" to that list because of fabian's reply back in juli. 🙂
migrated
I know this is an older thread, but in 1.16.1 Ancient debris currently loses blast resistance when moving.
Mask3D_WOLF
Wool does not incur vibrations when pushed. See MC-213587
Mask3D_WOLF
Can confirm in 21w05b
FaRo1
"Community consensus" means less than "Confirmed". It's for bugs that are reported often, but no mod or helper was yet able to reproduce it. I'm not sure what you understand under that term, but it definitely doesn't mean "please leave this bug because many people like to abuse it". That is not a supported usecase.
ampolive
Can confirm in 1.17.1.
theGlotzerify
can confirm in 1.18.1
migrated
Add the line
Block material/note block instrument |
migrated
I would have to say some issues listed here are really "hijacked" by other issues. Though some issues are indeed potentially used in a lot of redstone contraptions, but there are others that make complete sense to redstone users if fixed.
Just like MC-250307 (Block material/note block instrument), this behavior restricts the possibilty of note block based block sorter, that half of its functionality is blocked due to the incorrect redstone signal triggered by moving piston block.
This behavior could have been easily fixed by ignoring the instrument update from moving piston block in note block's implementation, just along with some other note block updates introduced in 1.19 (and thus made possible to a efficient clay-based mud farm), but after placing it in this general issue, it is really "hijacked" by other issues that contains side effect and thus prevented from being fixed forever if no such "community consensus" could be reached.
ncolyer11
yea na this would break basically everything
muzikbike
Do the following images demonstrate the transparent rendering issue mentioned in this ticket, or is that a different issue entirely?
[media][media]
[media]
[media]
FaRo1
Yes, that's it. The duplicate report linked here has a video attached. Maybe a better wording would be "rendering of connected faces of transparent blocks of the same type".
Panda4994