Affects Version/s: Minecraft 1.12.2, Minecraft 17w50a, Minecraft 18w20b, Minecraft 1.13-pre1, Minecraft 1.13-pre2, Minecraft 1.13-pre3, Minecraft 1.13-pre4, Minecraft 1.13-pre6, Minecraft 1.13-pre7, Minecraft 1.13-pre8, Minecraft 1.13, Minecraft 1.13.1, Minecraft 1.13.2, Minecraft 18w46a, Minecraft 18w48a, Minecraft 18w48b, Minecraft 18w49a, Minecraft 18w50a, Minecraft 19w02a, Minecraft 19w03c, Minecraft 19w04a, Minecraft 19w04b, Minecraft 19w05a, Minecraft 19w06a, Minecraft 19w07a, Minecraft 19w08b, Minecraft 1.14, 1.14.4, 19w36a, 19w37a, 1.15 Pre-release 1, 1.15.1, 1.15.2 Pre-Release 1, 1.15.2, 20w08a, 1.16 Pre-release 2, 1.16, 1.16.2, 1.16.3 Release Candidate 1, 1.16.3, 1.16.4 Pre-release 2, 1.16.4, 21w03a, 1.16.5, 21w05a, 21w05b, 21w07a, 21w13a, 21w15a, 1.17
Fix Version/s: None
Category:Block states, Redstone
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.
|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|
|Slipperiness||Basically just matters for ice, but would make sense|
|OnFallenUpon Behavior||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|
|Sculk sensor vibration blocking|
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.
These issues are generally not vitally important, however I think they are worth considering for potential systematic changes regarding moving blocks.