Minecraft:Piston - Revision history

SyncBot: Sync: updated from Minecraft

2026-07-09T11:11:20Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:11, 9 July 2026
Line 53:		Line 53:
	{{IN\|je}}, a piston that is de-powered during the extension process aborts its extension and starts to retract (assuming it can detect the signal change). Any block which was being pushed by that piston continues to move as if the piston was still pushing it.		{{IN\|je}}, a piston that is de-powered during the extension process aborts its extension and starts to retract (assuming it can detect the signal change). Any block which was being pushed by that piston continues to move as if the piston was still pushing it.

	A piston that pushes a [[Minecraft:slime block]] bounces any entity that it displaces in the direction the piston is facing. Entities on top of a moving [[Minecraft:honey block]], or any other moving block,{{only\|bedrock\|short=1}} will also move with it. In addition, when a slime block or a honey block is moved by a piston, any movable block adjacent (not diagonally) to it also moves. See [[#~~Slime blocks and honey~~ blocks\|§ ~~Slime blocks and honey~~ blocks]] for more details.		A piston that pushes a [[Minecraft:slime block]] bounces any entity that it displaces in the direction the piston is facing. Entities on top of a moving [[Minecraft:honey block]], or any other moving block,{{only\|bedrock\|short=1}} will also move with it. In addition, when a slime block or a honey block is moved by a piston, any movable block adjacent (not diagonally) to it also moves. See [[#Sticky blocks\|§ Sticky blocks]] for more details.

	{{IN\|be}}, blocks that require a support (such as levers) can be placed on the back or sides of a piston without being destroyed when that piston extends. {{IN\|je}}, on the other hand, the majority of blocks that require a support are only safe to place on the back of pistons.		{{IN\|be}}, blocks that require a support (such as levers) can be placed on the back or sides of a piston without being destroyed when that piston extends. {{IN\|je}}, on the other hand, the majority of blocks that require a support are only safe to place on the back of pistons.
Line 68:		Line 68:
	-->		-->

	=== Start delay ===		=== Powering pistons ===
			[[File:Stacked pistons powered by one redstone line.png\|alt=\|thumb\|200px\|Pistons powered by one line of redstone.]]

			Pistons can be activated from any side, excluding from the head.

			{{IN\|BE}}, redstone dust gets automatically redirected toward pistons if placed next to them (except for the head's side).

			==== Start delay ====
	A piston won't extend or retract immediately when it is activated: this phenomenon is known as "start delay".		A piston won't extend or retract immediately when it is activated: this phenomenon is known as "start delay".

Line 88:		Line 95:

	{{IN\|be}}, the start delay is fixed at {{convert\|2\|game tick\|second}}, meaning that the piston starts to extend or retract 2 game ticks after it is activated. Pistons can only activate on the input/consumer redstone tick ([[Minecraft:C-tick]]).		{{IN\|be}}, the start delay is fixed at {{convert\|2\|game tick\|second}}, meaning that the piston starts to extend or retract 2 game ticks after it is activated. Pistons can only activate on the input/consumer redstone tick ([[Minecraft:C-tick]]).

	~~=== Powering pistons ===~~
	~~[[File:Stacked pistons powered by one redstone line.png\|alt=\|thumb\|200px\|Pistons powered by one line of redstone.]]~~

	~~Pistons can be activated from any side, excluding from the head.~~

	~~{{IN\|BE}}, redstone dust gets automatically redirected toward pistons if placed next to them (except for the head's side).~~

	==== Quasi-Connectivity ====		==== Quasi-Connectivity ====
Line 107:		Line 107:
	Quasi-connectivity can be used to make a [[Minecraft:Tutorial:Block update detector\|BUD switch]], taking advantage of the fact that a piston powered through QC doesn't always get immediately [[Minecraft:block update\|updated]].		Quasi-connectivity can be used to make a [[Minecraft:Tutorial:Block update detector\|BUD switch]], taking advantage of the fact that a piston powered through QC doesn't always get immediately [[Minecraft:block update\|updated]].

	=== Soft inversion ===		==== Soft inversion ====
	{{see also\|Tutorial:Soft inversion}}		{{see also\|Tutorial:Soft inversion}}
	{{exclusive\|bedrock\|section=1}}		{{exclusive\|bedrock\|section=1}}
Line 116:		Line 116:
	When a piston that has a [[Minecraft:redstone torch]] attached to it is powered, the redstone torch turns off, and when said piston is depowered, the redstone torch turns back on: this property is called ''[[Minecraft:soft inversion]]''.<ref>{{bug\|MCPE-17909\|\|\|WF}}</ref><ref>"Explaining soft inversion: the Minecraft Bedrock Redstone bug that won't get fixed" – https://www.youtube.com/watch?v=zUgKXTsLOA0</ref> Since soft inversion works even if the piston is being powered indirectly through a block, it can be used to toggle the state of a redstone torch from farther away compared to other powering methods. It's still possible to take advantage of soft inversion even if the piston cannot extend or retract.		When a piston that has a [[Minecraft:redstone torch]] attached to it is powered, the redstone torch turns off, and when said piston is depowered, the redstone torch turns back on: this property is called ''[[Minecraft:soft inversion]]''.<ref>{{bug\|MCPE-17909\|\|\|WF}}</ref><ref>"Explaining soft inversion: the Minecraft Bedrock Redstone bug that won't get fixed" – https://www.youtube.com/watch?v=zUgKXTsLOA0</ref> Since soft inversion works even if the piston is being powered indirectly through a block, it can be used to toggle the state of a redstone torch from farther away compared to other powering methods. It's still possible to take advantage of soft inversion even if the piston cannot extend or retract.

	=== ~~Slime and honey~~ blocks ===		=== Sticky blocks ===
	{{Schematic		{{Schematic
	\|caption=Piston A ~~may extend~~ because the slime block ~~ignores~~ the adjacent obsidian. Piston B ~~may not extend~~ because the ~~diamond~~ block ~~is prevented from moving by the obsidian, as such~~ the slime block ~~also refuses to move~~.		\|caption=Piston A extends because the slime block can't stick to the adjacent obsidian. Piston B fails because the obsidian blocks the block attached to the slime block.
	\|clear=right		\|clear=right
	\|pi-e+A\|SL\|\|\|pi-e+B\|SL\|\|-		\|le-$e!\|pi-e!+A\|pe-e\|SL\|le-$e!\|pi-e+B\|SL\|\|-
	\|\|obsidian\|\|\|\|MB\|obsidian		\|\|\|obsidian\|obsidian\|\|\|MB\|obsidian
	}}		}}
			[[Minecraft:slime block\|Slime]] and [[Minecraft:honey block\|honey]] blocks are sticky: when either block is moved by a piston, adjacent (non-diagonal) blocks stick to and move with it.{{note\|Despite their name, [[Minecraft:sticky pistons]] do not fall under this definition.}} For example, a slime block sitting on the ground attempts to move the ground block underneath itself, which in turn has to push additional ground blocks in the direction of motion just as if they were being pushed directly by a piston. The same occurs when a sticky block is moved by another adjacent sticky block of the same kind. For example, a 2×2×2 cube of honey blocks may be pushed as a single unit by a piston acting on any of the blocks in the cube. Any block that cannot be moved or can be broken by a piston does not stick to sticky blocks. However, if an adjacent block could be moved but is prevented from being moved by the presence of an immovable block, the sticky block is prevented from moving as well, and the piston does not extend.

	~~When a [[Minecraft:slime block]] is pushed or pulled by a piston, adjacent~~ blocks ~~also move with the slime block, due~~ to ~~its stickiness. These blocks may in turn push~~ other ~~blocks, not just the blocks in the line in front of the piston~~. ~~For example, a slime block sitting on the ground attempts~~ to ~~move the ground block underneath itself, which in turn has to push additional ground blocks in the direction of motion just as if they were being pushed directly by a piston. The same occurs when a~~ slime block is moved by another adjacent slime block. For example, a 2×2×2 cube of slime blocks may be pushed or pulled as a single unit by a piston acting on any of the blocks in the cube. A slime block adjacent to a block that cannot be moved by pistons or a block that can be broken by piston ignores that block. However, if an adjacent block could be moved, but is prevented to by the presence of an unmovable block, the slime block is prevented from moving as well and ~~the piston does not extend.~~		Slime and honey blocks do not stick to each other. This allows redstone contraptions to use alternating slime and honey blocks side by side without interfering with each other.

	~~Slime~~ blocks~~' stickiness is unilateral, as such they can't be pulled~~ by a non-[[Minecraft:sticky piston]] and they are not moved if an adjacent (non-slime) block is moved by a piston. The maximum of 12 blocks moved by a piston still applies. For example, a 2×2×3 structure of slime blocks may be pushed by a piston as long as no other ~~movable block is adjacent to it. A piston cannot move itself via a "hook" constructed of slime blocks, but [[Minecraft:flying machines]] can be created with multiple pistons~~.

	[[Minecraft:~~Honey block~~]]~~s work like slime blocks when it comes to moving other blocks~~, ~~however slime~~ and ~~honey~~ blocks ~~do not stick to each other~~. ~~This allows~~, ~~by alternating~~ slime ~~and honey~~ blocks, to ~~have redstone contraptions which make use~~ of ~~these~~ sticky blocks ~~stay side by side without interfering~~ with ~~one another~~.		Slime and honey blocks' stickiness is unilateral. They can't be pulled by a non-[[Minecraft:sticky piston]], and they are not moved if an adjacent (non-sticky) block is moved by a piston. The maximum of 12 blocks moved by a piston still applies. For example, a 2×2×3 structure of slime blocks may be pushed by a piston as long as no other movable block is adjacent to it. A piston cannot move itself via a "hook" constructed of sticky blocks, but [[Minecraft:flying machines]] can be created with multiple pistons.

	[[Minecraft:Glazed terracotta]] and the [[Minecraft:heavy core]]{{only\|bedrock\|short=1}} do not stick to adjacent slime or honey blocks, even though they can be pushed by pistons.		[[Minecraft:Glazed terracotta]] and the [[Minecraft:heavy core]]{{only\|bedrock\|short=1}} do not stick to adjacent slime or honey blocks, even though they can be pushed by pistons.

SyncBot: Sync: updated from Minecraft

2026-07-08T11:14:30Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:14, 8 July 2026
Line 7:		Line 7:
	\| image2caption = {{BE}}		\| image2caption = {{BE}}
	\| invimage = Piston		\| invimage = Piston
			\| waterloggable = {{jebe\|No\|Yes}}
	\| transparent = {{jebe\|No\|Yes}}		\| transparent = {{jebe\|No\|Yes}}
	\| light = No		\| light = No
Line 89:		Line 90:

	=== Powering pistons ===		=== Powering pistons ===
	[[File:Stacked pistons powered by one redstone line.png\|alt=\|thumb\|Pistons powered by one line of redstone.]]		[[File:Stacked pistons powered by one redstone line.png\|alt=\|thumb\|200px\|Pistons powered by one line of redstone.]]

	Pistons can be activated from any side, excluding from the head.		Pistons can be activated from any side, excluding from the head.

SyncBot: Sync: updated from Minecraft

2026-07-05T11:11:04Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:11, 5 July 2026
Line 50:		Line 50:
	When a piston loses power, its head retracts. Like the extension, the retraction starts after a [[#Start delay\|start delay]] and takes {{convert\|2\|game tick\|second}} to finish.		When a piston loses power, its head retracts. Like the extension, the retraction starts after a [[#Start delay\|start delay]] and takes {{convert\|2\|game tick\|second}} to finish.

	A piston that pushes a [[Minecraft:slime block]] bounces any entity that it displaces in the direction the piston is facing. Entities on top of a moving [[Minecraft:honey block]], or any other moving block,{{only\|bedrock\|short=1}} will also move with it. In addition, when a slime block or a honey block is moved by a piston, any movable block adjacent (not diagonally) to it also moves. See ~~the "~~[[#Slime blocks and honey blocks\|Slime blocks and honey blocks]]~~" section of this page~~ for more details.		{{IN\|je}}, a piston that is de-powered during the extension process aborts its extension and starts to retract (assuming it can detect the signal change). Any block which was being pushed by that piston continues to move as if the piston was still pushing it.

			A piston that pushes a [[Minecraft:slime block]] bounces any entity that it displaces in the direction the piston is facing. Entities on top of a moving [[Minecraft:honey block]], or any other moving block,{{only\|bedrock\|short=1}} will also move with it. In addition, when a slime block or a honey block is moved by a piston, any movable block adjacent (not diagonally) to it also moves. See [[#Slime blocks and honey blocks\|§ Slime blocks and honey blocks]] for more details.

	{{IN\|be}}, blocks that require a support (such as levers) can be placed on the back or sides of a piston without being destroyed when that piston extends. {{IN\|je}}, on the other hand, the majority of blocks that require a support are only safe to place on the back of pistons.		{{IN\|be}}, blocks that require a support (such as levers) can be placed on the back or sides of a piston without being destroyed when that piston extends. {{IN\|je}}, on the other hand, the majority of blocks that require a support are only safe to place on the back of pistons.

	{{IN\|be}}~~, despite not being a conductive block~~, comparators can read the fullness of containers through pistons.		{{IN\|be}}, comparators can read the fullness of containers through pistons, despite them not being [[Minecraft:conductive]].
	<!--=== Basic behavior ===		<!--=== Basic behavior ===
	* Extension: Pushes up to 12 blocks in front of the head.		* Extension: Pushes up to 12 blocks in front of the head.
Line 73:		Line 75:
	! Java		! Java
	\| 0 or 1 game tick		\| 0 or 1 game tick
	\| 0 ticks if powered ~~by a~~ scheduled/random tick or block event; 1 tick if powered ~~by player action,~~ entity, or block entity phase.		\| 0 ticks if powered during the scheduled tick, random tick or block event phase; 1 tick if powered during the entity or block entity phase, or during player input handling.
	\|-		\|-
	! Bedrock		! Bedrock
Line 91:		Line 93:
	Pistons can be activated from any side, excluding from the head.		Pistons can be activated from any side, excluding from the head.

	~~{{IN\|JE}}, pistons can be powered from one block above compared to most redstone components. this is called [[Minecraft:Tutorial:Quasi-connectivity\|quasi-connectivity]] (see below).~~
	{{IN\|BE}}, redstone dust gets automatically redirected toward pistons if placed next to them (except for the head's side).		{{IN\|BE}}, redstone dust gets automatically redirected toward pistons if placed next to them (except for the head's side).

	=== Quasi-Connectivity ~~(QC)~~ ===		==== Quasi-Connectivity ====
	{{see also\|Tutorial:Quasi-connectivity}}		{{see also\|Tutorial:Quasi-connectivity}}
	{{exclusive\|java\|section=1}}		{{exclusive\|java\|section=1}}
	{{Schematic\|caption='''~~Quasi~~-~~Connectivity~~'''		{{Schematic\|caption='''A lamp that's being powered normally on top of a piston that's being powered through quasi-connectivity. '''
	\|SB\|rt-$w!\|RL-!\|\|-		\|SB\|rt-$w!\|RL-!\|\|-
	\|\|\|pi-e!\|pe-e		\|\|\|pi-e!\|pe-e
	}}		}}
	Pistons powered from one block above compared to most redstone components: this property is called [[Minecraft:quasi-connectivity]] ~~and can be used to make a [[Minecraft:Tutorial:Block update detector\|BUD switch]], taking advantage of the fact that a piston powered through quasi-connectivity doesn't always get updated~~. With quasi-connectivity, a piston facing up can also be powered from the head's direction, which is otherwise impossible. Due to quasi-connectivity, a piston facing up that has a [[Minecraft:block of redstone]] on top of itself can extend but not retract: this happens because after the piston extends, it keeps receiving power from the redstone block.		Pistons can be powered from one block above compared to most redstone components: this property is called [[Minecraft:quasi-connectivity]] (QC). With quasi-connectivity, a piston facing up can also be powered from the head's direction, which is otherwise impossible. Due to quasi-connectivity, a piston facing up that has a [[Minecraft:block of redstone]] on top of itself can extend but not retract: this happens because after the piston extends, it keeps receiving power from the redstone block.
	<!-~~-A piston facing up with~~ a [[Minecraft:~~block of redstone~~]] ~~on top will extend (because it is~~ powered ~~via~~ QC~~), but~~ '~~''will not retract''', the redstone block continues to power it after extension. To retract, you must remove the redstone~~ block or update ~~the piston~~.~~-->~~
			Quasi-connectivity can be used to make a [[Minecraft:Tutorial:Block update detector\|BUD switch]], taking advantage of the fact that a piston powered through QC doesn't always get immediately [[Minecraft:block update\|updated]].

	=== Soft inversion ===		=== Soft inversion ===
	{{see also\|Tutorial:Soft inversion}}		{{see also\|Tutorial:Soft inversion}}
	{{exclusive\|bedrock\|section=1}}		{{exclusive\|bedrock\|section=1}}
	{{Schematic\|caption='''~~Soft inversion~~'''		{{Schematic\|caption='''Flicking the lever caused the piston to extend and the redstone torch to turn off.'''
	\|\|\|pe-n\|\|\|-		\|\|\|pe-n\|\|\|-
	\|le-$e!\|SB\|pi-n!\|rt-$w\|RL\|-		\|le-$e!\|SB\|pi-n!\|rt-$w\|RL\|-
Line 232:		Line 234:
	\|{{HistoryLine\|\|June 7, 2011\|link={{tweet\|jeb\|78167135435759617}}\|[[Minecraft:Jeb]] tweets an image of pistons in development.		\|{{HistoryLine\|\|June 7, 2011\|link={{tweet\|jeb\|78167135435759617}}\|[[Minecraft:Jeb]] tweets an image of pistons in development.
	\|[[File:Piston (U) pJE20110607.png\|32px]] The piston texture as screen-captured while in development had iron bands running over the head. The bands were removed for the release, leaving only iron brackets around the corners and edges.}}		\|[[File:Piston (U) pJE20110607.png\|32px]] The piston texture as screen-captured while in development had iron bands running over the head. The bands were removed for the release, leaving only iron brackets around the corners and edges.}}
			\|{{HistoryLine\|\|June 14, 2011\|link={{YouTube link\|uZJr86d2IUo}}\|A video showing pistons being worked on is posted on the official Minecraft YouTube channel.}}
	}}		}}

Line 243:		Line 246:
	\|{{HistoryLine\|java}}		\|{{HistoryLine\|java}}
	\|{{HistoryLine\|\|1.2.4\|dev=release\|Spruce, birch, and jungle [[Minecraft:planks]] can now be used to craft pistons.}}		\|{{HistoryLine\|\|1.2.4\|dev=release\|Spruce, birch, and jungle [[Minecraft:planks]] can now be used to craft pistons.}}
	\|{{HistoryLine\|\|1.3.1\|dev=12w26a\|Pistons now schedule extensions and retractions rather than executing them as soon as they are ~~updated~~.}}		\|{{HistoryLine\|\|1.3.1\|dev=12w26a\|Pistons now schedule extensions and retractions rather than executing them as soon as they realize they are (un)powered.}}
	\|{{HistoryLine\|\|1.5\|dev=13w10a\|Pistons changing their {{code\|extended}} state from {{code\|false}} to {{code\|true}} is now the ''last'' step of (the start of) the extension process, rather then the first. This change affects some redstone contraptions.}}		\|{{HistoryLine\|\|1.5\|dev=13w10a\|Pistons changing their {{code\|extended}} state from {{code\|false}} to {{code\|true}} is now the ''last'' step of (the start of) the extension process, rather then the first. This change affects some redstone contraptions.}}
	\|{{HistoryLine\|\|1.7.2\|dev=1.7.1\|Acacia and dark oak [[Minecraft:planks]] can now be used to craft pistons.}}		\|{{HistoryLine\|\|1.7.2\|dev=1.7.1\|Acacia and dark oak [[Minecraft:planks]] can now be used to craft pistons.}}
Line 345:		Line 348:
	\|date=January 3, 2019}}		\|date=January 3, 2019}}
	</ref>		</ref>
	* When toggled between on and off rapidly with a gravity affected block (such as sand) above it, a piston can eventually break the block, which can be picked up as a resource. However, gravel broken this way never drops flint.		* Carpets can be placed on top of [[Minecraft:moving piston\|moving blocks]].
	* Carpet can be placed on ~~the~~ [[Minecraft:moving piston\|moving ~~piston block~~]]~~, and does not break after moving piston block converts to a non-air block~~.

	== Gallery ==		== Gallery ==

SyncBot: Sync: updated from Minecraft

2026-07-04T11:09:04Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:09, 4 July 2026
Line 359:		Line 359:
	<gallery>		<gallery>
	Pistonscreen.png\|First screenshot of pistons		Pistonscreen.png\|First screenshot of pistons
			Pistons.png\|Another screenshot of in-development pistons
	Piston Light.png\|Light shining through an extended piston		Piston Light.png\|Light shining through an extended piston
	Pocket Edition Pistons.jpg\|Redstone connecting to pistons in ''Bedrock Edition''		Pocket Edition Pistons.jpg\|Redstone connecting to pistons in ''Bedrock Edition''

SyncBot: Sync: updated from Minecraft

2026-05-28T11:08:43Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:08, 28 May 2026
Line 123:		Line 123:
	When a [[Minecraft:slime block]] is pushed or pulled by a piston, adjacent blocks also move with the slime block, due to its stickiness. These blocks may in turn push other blocks, not just the blocks in the line in front of the piston. For example, a slime block sitting on the ground attempts to move the ground block underneath itself, which in turn has to push additional ground blocks in the direction of motion just as if they were being pushed directly by a piston. The same occurs when a slime block is moved by another adjacent slime block. For example, a 2×2×2 cube of slime blocks may be pushed or pulled as a single unit by a piston acting on any of the blocks in the cube. A slime block adjacent to a block that cannot be moved by pistons or a block that can be broken by piston ignores that block. However, if an adjacent block could be moved, but is prevented to by the presence of an unmovable block, the slime block is prevented from moving as well and the piston does not extend.		When a [[Minecraft:slime block]] is pushed or pulled by a piston, adjacent blocks also move with the slime block, due to its stickiness. These blocks may in turn push other blocks, not just the blocks in the line in front of the piston. For example, a slime block sitting on the ground attempts to move the ground block underneath itself, which in turn has to push additional ground blocks in the direction of motion just as if they were being pushed directly by a piston. The same occurs when a slime block is moved by another adjacent slime block. For example, a 2×2×2 cube of slime blocks may be pushed or pulled as a single unit by a piston acting on any of the blocks in the cube. A slime block adjacent to a block that cannot be moved by pistons or a block that can be broken by piston ignores that block. However, if an adjacent block could be moved, but is prevented to by the presence of an unmovable block, the slime block is prevented from moving as well and the piston does not extend.

	Slime blocks' stickiness is unilateral, as such they can't be pulled by a non-[[Minecraft:sticky piston]] and they are not moved if an adjacent (non-slime) block is moved by a piston. The maximum of 12 blocks moved by a piston still applies. For example, a 2×2×3 structure of slime blocks may be pushed by a piston as long as no other movable block is adjacent to it. A piston cannot move itself via a "hook" constructed of slime blocks, but [[Minecraft:flying machines]]s can be created with multiple pistons.		Slime blocks' stickiness is unilateral, as such they can't be pulled by a non-[[Minecraft:sticky piston]] and they are not moved if an adjacent (non-slime) block is moved by a piston. The maximum of 12 blocks moved by a piston still applies. For example, a 2×2×3 structure of slime blocks may be pushed by a piston as long as no other movable block is adjacent to it. A piston cannot move itself via a "hook" constructed of slime blocks, but [[Minecraft:flying machines]] can be created with multiple pistons.

	[[Minecraft:Honey block]]s work like slime blocks when it comes to moving other blocks, however slime and honey blocks do not stick to each other. This allows, by alternating slime and honey blocks, to have redstone contraptions which make use of these sticky blocks stay side by side without interfering with one another.		[[Minecraft:Honey block]]s work like slime blocks when it comes to moving other blocks, however slime and honey blocks do not stick to each other. This allows, by alternating slime and honey blocks, to have redstone contraptions which make use of these sticky blocks stay side by side without interfering with one another.

SyncBot: Sync: updated from Minecraft

2026-05-27T11:13:34Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:13, 27 May 2026
Line 53:		Line 53:

	{{IN\|be}}, blocks that require a support (such as levers) can be placed on the back or sides of a piston without being destroyed when that piston extends. {{IN\|je}}, on the other hand, the majority of blocks that require a support are only safe to place on the back of pistons.		{{IN\|be}}, blocks that require a support (such as levers) can be placed on the back or sides of a piston without being destroyed when that piston extends. {{IN\|je}}, on the other hand, the majority of blocks that require a support are only safe to place on the back of pistons.

			{{IN\|be}}, despite not being a conductive block, comparators can read the fullness of containers through pistons.
	<!--=== Basic behavior ===		<!--=== Basic behavior ===
	* Extension: Pushes up to 12 blocks in front of the head.		* Extension: Pushes up to 12 blocks in front of the head.
Line 111:		Line 113:
	When a piston that has a [[Minecraft:redstone torch]] attached to it is powered, the redstone torch turns off, and when said piston is depowered, the redstone torch turns back on: this property is called ''[[Minecraft:soft inversion]]''.<ref>{{bug\|MCPE-17909\|\|\|WF}}</ref><ref>"Explaining soft inversion: the Minecraft Bedrock Redstone bug that won't get fixed" – https://www.youtube.com/watch?v=zUgKXTsLOA0</ref> Since soft inversion works even if the piston is being powered indirectly through a block, it can be used to toggle the state of a redstone torch from farther away compared to other powering methods. It's still possible to take advantage of soft inversion even if the piston cannot extend or retract.		When a piston that has a [[Minecraft:redstone torch]] attached to it is powered, the redstone torch turns off, and when said piston is depowered, the redstone torch turns back on: this property is called ''[[Minecraft:soft inversion]]''.<ref>{{bug\|MCPE-17909\|\|\|WF}}</ref><ref>"Explaining soft inversion: the Minecraft Bedrock Redstone bug that won't get fixed" – https://www.youtube.com/watch?v=zUgKXTsLOA0</ref> Since soft inversion works even if the piston is being powered indirectly through a block, it can be used to toggle the state of a redstone torch from farther away compared to other powering methods. It's still possible to take advantage of soft inversion even if the piston cannot extend or retract.

	~~=== Interaction with comparators ===~~
	~~{{exclusive\|bedrock\|section=1}}~~
	~~Despite not being a conductive block, comparators can read the fullness of containers through pistons.~~

	~~=== Limitations ===~~
	~~<!-- [[Minecraft:Push reaction]] redirects here. -->~~
	~~Pistons cannot push:~~
	* Blocks listed as such in the table below.
	* Blocks into the [[Minecraft:void]] or above the [[Minecraft:build limit]].
	* More than 12 blocks at once.
	* {{IN\|je}}, blocks beyond the [[Minecraft:world border]].

	~~If the requirements for a block to be pushed are not met, the piston will not extend.~~

	~~{{:Piston/Table}}~~
	=== Slime and honey blocks ===		=== Slime and honey blocks ===
	{{Schematic		{{Schematic
Line 136:		Line 123:
	When a [[Minecraft:slime block]] is pushed or pulled by a piston, adjacent blocks also move with the slime block, due to its stickiness. These blocks may in turn push other blocks, not just the blocks in the line in front of the piston. For example, a slime block sitting on the ground attempts to move the ground block underneath itself, which in turn has to push additional ground blocks in the direction of motion just as if they were being pushed directly by a piston. The same occurs when a slime block is moved by another adjacent slime block. For example, a 2×2×2 cube of slime blocks may be pushed or pulled as a single unit by a piston acting on any of the blocks in the cube. A slime block adjacent to a block that cannot be moved by pistons or a block that can be broken by piston ignores that block. However, if an adjacent block could be moved, but is prevented to by the presence of an unmovable block, the slime block is prevented from moving as well and the piston does not extend.		When a [[Minecraft:slime block]] is pushed or pulled by a piston, adjacent blocks also move with the slime block, due to its stickiness. These blocks may in turn push other blocks, not just the blocks in the line in front of the piston. For example, a slime block sitting on the ground attempts to move the ground block underneath itself, which in turn has to push additional ground blocks in the direction of motion just as if they were being pushed directly by a piston. The same occurs when a slime block is moved by another adjacent slime block. For example, a 2×2×2 cube of slime blocks may be pushed or pulled as a single unit by a piston acting on any of the blocks in the cube. A slime block adjacent to a block that cannot be moved by pistons or a block that can be broken by piston ignores that block. However, if an adjacent block could be moved, but is prevented to by the presence of an unmovable block, the slime block is prevented from moving as well and the piston does not extend.

	Slime blocks' stickiness is unilateral, as such they can't be pulled by a non-[[Minecraft:sticky piston]] and they are not moved if an adjacent (non-slime) block is moved by a piston. The maximum of 12 blocks moved by a piston still applies. For example, a 2×2×3 structure of slime blocks may be pushed by a piston as long as no other movable block is adjacent to it. A piston cannot move itself via a "hook" constructed of slime blocks, but ~~self-propelled contraptions can be created with multiple pistons. For more informations, see the article~~ [[Minecraft:~~Tutorial:Flying~~ machines]].		Slime blocks' stickiness is unilateral, as such they can't be pulled by a non-[[Minecraft:sticky piston]] and they are not moved if an adjacent (non-slime) block is moved by a piston. The maximum of 12 blocks moved by a piston still applies. For example, a 2×2×3 structure of slime blocks may be pushed by a piston as long as no other movable block is adjacent to it. A piston cannot move itself via a "hook" constructed of slime blocks, but [[Minecraft:flying machines]]s can be created with multiple pistons.

	[[Minecraft:Honey block]]s work like slime blocks when it comes to moving other blocks, however honey ~~blocks and slime~~ blocks do not stick to each other. This allows, by alternating slime ~~blocks~~ and honey blocks, to have redstone contraptions which make use of these sticky blocks stay side by side without interfering with one another.		[[Minecraft:Honey block]]s work like slime blocks when it comes to moving other blocks, however slime and honey blocks do not stick to each other. This allows, by alternating slime and honey blocks, to have redstone contraptions which make use of these sticky blocks stay side by side without interfering with one another.

	[[Minecraft:Glazed terracotta]] and the [[Minecraft:heavy core]]{{only\|bedrock\|short=1}} ~~have an interesting property: they ''~~do not'' stick to adjacent slime ~~blocks~~ or honey blocks, even though they can be pushed by pistons.		[[Minecraft:Glazed terracotta]] and the [[Minecraft:heavy core]]{{only\|bedrock\|short=1}} do not stick to adjacent slime or honey blocks, even though they can be pushed by pistons.

	=== Sculk detection ===		=== Sculk detection ===
	Pistons emit vibrations detectable by [[Minecraft:sculk sensor]]s. A [[Minecraft:calibrated sculk sensor]] tuned to signal strength '''10''' detects piston retraction; strength '''11''' detects extension; strength '''12''' detects a block broken by a piston.		Pistons emit vibrations detectable by [[Minecraft:sculk sensor]]s. A [[Minecraft:calibrated sculk sensor]] tuned to signal strength '''10''' detects piston retraction; strength '''11''' detects extension; strength '''12''' detects a block broken by a piston.

			== Limitations ==
			<!-- [[Minecraft:Push reaction]] redirects here. -->
			Pistons cannot push:
			* Blocks listed as such in the table below.
			* Blocks into the [[Minecraft:void]] or above the [[Minecraft:build limit]].
			* More than 12 blocks at once.
			* {{IN\|je}}, blocks beyond the [[Minecraft:world border]].

			If the requirements for a block to be pushed are not met, the piston will not extend.

			{{:Piston/Table}}

	== Technical components ==		== Technical components ==

SyncBot: Sync: updated from Minecraft

2026-05-24T11:13:18Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:13, 24 May 2026
Line 347:		Line 347:
	</ref>		</ref>
	* When toggled between on and off rapidly with a gravity affected block (such as sand) above it, a piston can eventually break the block, which can be picked up as a resource. However, gravel broken this way never drops flint.		* When toggled between on and off rapidly with a gravity affected block (such as sand) above it, a piston can eventually break the block, which can be picked up as a resource. However, gravel broken this way never drops flint.
	* Carpet can be placed on the piston ~~extension~~ block, and ~~remains even if it is replaced with~~ a ~~solid~~ block ~~using {{cmd\|setblock}}~~.		* Carpet can be placed on the [[Minecraft:moving piston\|moving piston block]], and does not break after moving piston block converts to a non-air block.

	== Gallery ==		== Gallery ==

SyncBot: Sync: updated from Minecraft

2026-05-22T11:11:36Z

Sync: updated from Minecraft

Show changes

SyncBot: Sync: updated from Minecraft

2026-05-16T11:20:12Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:20, 16 May 2026
Line 1:		Line 1:
	{{for\|the sticky version\|Sticky Piston}}		{{for\|the sticky version\|Sticky Piston}}
			{{Earth hatnote\|type=block}}
	{{Infobox block		{{Infobox block
	\| image = Piston.gif		\| image = Piston.gif

SyncBot: Sync: updated from Minecraft

2026-05-09T11:13:35Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:11, 5 July 2026
Line 50:		Line 50:
	When a piston loses power, its head retracts. Like the extension, the retraction starts after a [[#Start delay\|start delay]] and takes {{convert\|2\|game tick\|second}} to finish.		When a piston loses power, its head retracts. Like the extension, the retraction starts after a [[#Start delay\|start delay]] and takes {{convert\|2\|game tick\|second}} to finish.

	A piston that pushes a [[Minecraft:slime block]] bounces any entity that it displaces in the direction the piston is facing. Entities on top of a moving [[Minecraft:honey block]], or any other moving block,{{only\|bedrock\|short=1}} will also move with it. In addition, when a slime block or a honey block is moved by a piston, any movable block adjacent (not diagonally) to it also moves. See ~~the "~~[[#Slime blocks and honey blocks\|Slime blocks and honey blocks]]~~" section of this page~~ for more details.		{{IN\|je}}, a piston that is de-powered during the extension process aborts its extension and starts to retract (assuming it can detect the signal change). Any block which was being pushed by that piston continues to move as if the piston was still pushing it.

			A piston that pushes a [[Minecraft:slime block]] bounces any entity that it displaces in the direction the piston is facing. Entities on top of a moving [[Minecraft:honey block]], or any other moving block,{{only\|bedrock\|short=1}} will also move with it. In addition, when a slime block or a honey block is moved by a piston, any movable block adjacent (not diagonally) to it also moves. See [[#Slime blocks and honey blocks\|§ Slime blocks and honey blocks]] for more details.

	{{IN\|be}}, blocks that require a support (such as levers) can be placed on the back or sides of a piston without being destroyed when that piston extends. {{IN\|je}}, on the other hand, the majority of blocks that require a support are only safe to place on the back of pistons.		{{IN\|be}}, blocks that require a support (such as levers) can be placed on the back or sides of a piston without being destroyed when that piston extends. {{IN\|je}}, on the other hand, the majority of blocks that require a support are only safe to place on the back of pistons.

	{{IN\|be}}~~, despite not being a conductive block~~, comparators can read the fullness of containers through pistons.		{{IN\|be}}, comparators can read the fullness of containers through pistons, despite them not being [[Minecraft:conductive]].
	<!--=== Basic behavior ===		<!--=== Basic behavior ===
	* Extension: Pushes up to 12 blocks in front of the head.		* Extension: Pushes up to 12 blocks in front of the head.
Line 73:		Line 75:
	! Java		! Java
	\| 0 or 1 game tick		\| 0 or 1 game tick
	\| 0 ticks if powered ~~by a~~ scheduled/random tick or block event; 1 tick if powered ~~by player action,~~ entity, or block entity phase.		\| 0 ticks if powered during the scheduled tick, random tick or block event phase; 1 tick if powered during the entity or block entity phase, or during player input handling.
	\|-		\|-
	! Bedrock		! Bedrock
Line 91:		Line 93:
	Pistons can be activated from any side, excluding from the head.		Pistons can be activated from any side, excluding from the head.

	~~{{IN\|JE}}, pistons can be powered from one block above compared to most redstone components. this is called [[Minecraft:Tutorial:Quasi-connectivity\|quasi-connectivity]] (see below).~~
	{{IN\|BE}}, redstone dust gets automatically redirected toward pistons if placed next to them (except for the head's side).		{{IN\|BE}}, redstone dust gets automatically redirected toward pistons if placed next to them (except for the head's side).

	=== Quasi-Connectivity ~~(QC)~~ ===		==== Quasi-Connectivity ====
	{{see also\|Tutorial:Quasi-connectivity}}		{{see also\|Tutorial:Quasi-connectivity}}
	{{exclusive\|java\|section=1}}		{{exclusive\|java\|section=1}}
	{{Schematic\|caption='''~~Quasi~~-~~Connectivity~~'''		{{Schematic\|caption='''A lamp that's being powered normally on top of a piston that's being powered through quasi-connectivity. '''
	\|SB\|rt-$w!\|RL-!\|\|-		\|SB\|rt-$w!\|RL-!\|\|-
	\|\|\|pi-e!\|pe-e		\|\|\|pi-e!\|pe-e
	}}		}}
	Pistons powered from one block above compared to most redstone components: this property is called [[Minecraft:quasi-connectivity]] ~~and can be used to make a [[Minecraft:Tutorial:Block update detector\|BUD switch]], taking advantage of the fact that a piston powered through quasi-connectivity doesn't always get updated~~. With quasi-connectivity, a piston facing up can also be powered from the head's direction, which is otherwise impossible. Due to quasi-connectivity, a piston facing up that has a [[Minecraft:block of redstone]] on top of itself can extend but not retract: this happens because after the piston extends, it keeps receiving power from the redstone block.		Pistons can be powered from one block above compared to most redstone components: this property is called [[Minecraft:quasi-connectivity]] (QC). With quasi-connectivity, a piston facing up can also be powered from the head's direction, which is otherwise impossible. Due to quasi-connectivity, a piston facing up that has a [[Minecraft:block of redstone]] on top of itself can extend but not retract: this happens because after the piston extends, it keeps receiving power from the redstone block.
	<!-~~-A piston facing up with~~ a [[Minecraft:~~block of redstone~~]] ~~on top will extend (because it is~~ powered ~~via~~ QC~~), but~~ '~~''will not retract''', the redstone block continues to power it after extension. To retract, you must remove the redstone~~ block or update ~~the piston~~.~~-->~~
			Quasi-connectivity can be used to make a [[Minecraft:Tutorial:Block update detector\|BUD switch]], taking advantage of the fact that a piston powered through QC doesn't always get immediately [[Minecraft:block update\|updated]].

	=== Soft inversion ===		=== Soft inversion ===
	{{see also\|Tutorial:Soft inversion}}		{{see also\|Tutorial:Soft inversion}}
	{{exclusive\|bedrock\|section=1}}		{{exclusive\|bedrock\|section=1}}
	{{Schematic\|caption='''~~Soft inversion~~'''		{{Schematic\|caption='''Flicking the lever caused the piston to extend and the redstone torch to turn off.'''
	\|\|\|pe-n\|\|\|-		\|\|\|pe-n\|\|\|-
	\|le-$e!\|SB\|pi-n!\|rt-$w\|RL\|-		\|le-$e!\|SB\|pi-n!\|rt-$w\|RL\|-
Line 232:		Line 234:
	\|{{HistoryLine\|\|June 7, 2011\|link={{tweet\|jeb\|78167135435759617}}\|[[Minecraft:Jeb]] tweets an image of pistons in development.		\|{{HistoryLine\|\|June 7, 2011\|link={{tweet\|jeb\|78167135435759617}}\|[[Minecraft:Jeb]] tweets an image of pistons in development.
	\|[[File:Piston (U) pJE20110607.png\|32px]] The piston texture as screen-captured while in development had iron bands running over the head. The bands were removed for the release, leaving only iron brackets around the corners and edges.}}		\|[[File:Piston (U) pJE20110607.png\|32px]] The piston texture as screen-captured while in development had iron bands running over the head. The bands were removed for the release, leaving only iron brackets around the corners and edges.}}
			\|{{HistoryLine\|\|June 14, 2011\|link={{YouTube link\|uZJr86d2IUo}}\|A video showing pistons being worked on is posted on the official Minecraft YouTube channel.}}
	}}		}}

Line 243:		Line 246:
	\|{{HistoryLine\|java}}		\|{{HistoryLine\|java}}
	\|{{HistoryLine\|\|1.2.4\|dev=release\|Spruce, birch, and jungle [[Minecraft:planks]] can now be used to craft pistons.}}		\|{{HistoryLine\|\|1.2.4\|dev=release\|Spruce, birch, and jungle [[Minecraft:planks]] can now be used to craft pistons.}}
	\|{{HistoryLine\|\|1.3.1\|dev=12w26a\|Pistons now schedule extensions and retractions rather than executing them as soon as they are ~~updated~~.}}		\|{{HistoryLine\|\|1.3.1\|dev=12w26a\|Pistons now schedule extensions and retractions rather than executing them as soon as they realize they are (un)powered.}}
	\|{{HistoryLine\|\|1.5\|dev=13w10a\|Pistons changing their {{code\|extended}} state from {{code\|false}} to {{code\|true}} is now the ''last'' step of (the start of) the extension process, rather then the first. This change affects some redstone contraptions.}}		\|{{HistoryLine\|\|1.5\|dev=13w10a\|Pistons changing their {{code\|extended}} state from {{code\|false}} to {{code\|true}} is now the ''last'' step of (the start of) the extension process, rather then the first. This change affects some redstone contraptions.}}
	\|{{HistoryLine\|\|1.7.2\|dev=1.7.1\|Acacia and dark oak [[Minecraft:planks]] can now be used to craft pistons.}}		\|{{HistoryLine\|\|1.7.2\|dev=1.7.1\|Acacia and dark oak [[Minecraft:planks]] can now be used to craft pistons.}}
Line 345:		Line 348:
	\|date=January 3, 2019}}		\|date=January 3, 2019}}
	</ref>		</ref>
	* When toggled between on and off rapidly with a gravity affected block (such as sand) above it, a piston can eventually break the block, which can be picked up as a resource. However, gravel broken this way never drops flint.		* Carpets can be placed on top of [[Minecraft:moving piston\|moving blocks]].
	* Carpet can be placed on ~~the~~ [[Minecraft:moving piston\|moving ~~piston block~~]]~~, and does not break after moving piston block converts to a non-air block~~.

	== Gallery ==		== Gallery ==

← Older revision		Revision as of 11:09, 4 July 2026
Line 359:		Line 359:
	<gallery>		<gallery>
	Pistonscreen.png\|First screenshot of pistons		Pistonscreen.png\|First screenshot of pistons
			Pistons.png\|Another screenshot of in-development pistons
	Piston Light.png\|Light shining through an extended piston		Piston Light.png\|Light shining through an extended piston
	Pocket Edition Pistons.jpg\|Redstone connecting to pistons in ''Bedrock Edition''		Pocket Edition Pistons.jpg\|Redstone connecting to pistons in ''Bedrock Edition''

← Older revision		Revision as of 11:13, 9 May 2026
Line 199:		Line 199:
	\|Headless pistons do not break upon receiving a [[Minecraft:block update]] anymore.}}		\|Headless pistons do not break upon receiving a [[Minecraft:block update]] anymore.}}
	\|{{HistoryLine\|java}}		\|{{HistoryLine\|java}}
	\|{{HistoryLine\|\|1.2.4\|dev=release\|~~[[Minecraft:~~Spruce ~~planks]]~~, ~~[[Minecraft:~~birch ~~planks]]~~, and [[Minecraft:~~jungle~~ planks]] can now be used to craft pistons.}}		\|{{HistoryLine\|\|1.2.4\|dev=release\|Spruce, birch, and jungle [[Minecraft:planks]] can now be used to craft pistons.}}
	\|{{HistoryLine\|\|1.3.1\|dev=12w26a\|Pistons now schedule extensions and retractions rather than executing them as soon as they are updated.}}		\|{{HistoryLine\|\|1.3.1\|dev=12w26a\|Pistons now schedule extensions and retractions rather than executing them as soon as they are updated.}}
	\|{{HistoryLine\|\|1.5\|dev=13w10a\|Pistons changing their {{code\|extended}} state from {{code\|false}} to {{code\|true}} is now the ''last'' step of (the start of) the extension process, rather then the first. This change affects some redstone contraptions.}}		\|{{HistoryLine\|\|1.5\|dev=13w10a\|Pistons changing their {{code\|extended}} state from {{code\|false}} to {{code\|true}} is now the ''last'' step of (the start of) the extension process, rather then the first. This change affects some redstone contraptions.}}
	\|{{HistoryLine\|\|1.7.2\|dev=1.7.1\|~~[[Minecraft:~~Acacia ~~planks]]~~ and [[Minecraft:~~dark oak~~ planks]] can now be used to craft pistons.}}		\|{{HistoryLine\|\|1.7.2\|dev=1.7.1\|Acacia and dark oak [[Minecraft:planks]] can now be used to craft pistons.}}
	\|{{HistoryLine\|\|1.8\|dev=14w17a\|[[File:Piston (U) JE2.png\|32px]] [[File:Piston (D) JE2.png\|32px]] [[File:Headless Piston (U) JE2.png\|32px]] [[File:Headless Piston (D) JE2.png\|32px]] The models for pistons when facing up and down have been changed.}}		\|{{HistoryLine\|\|1.8\|dev=14w17a\|[[File:Piston (U) JE2.png\|32px]] [[File:Piston (D) JE2.png\|32px]] [[File:Headless Piston (U) JE2.png\|32px]] [[File:Headless Piston (D) JE2.png\|32px]] The models for pistons when facing up and down have been changed.}}
	\|{{HistoryLine\|\|\|dev=14w18a\|[[Minecraft:Slime block]]s now push and pull blocks adjacent when connected to sticky pistons.		\|{{HistoryLine\|\|\|dev=14w18a\|[[Minecraft:Slime block]]s now push and pull blocks adjacent when connected to sticky pistons.
Line 227:		Line 227:
	\|[[Minecraft:Pickaxe]]s are now the tool for breaking pistons.		\|[[Minecraft:Pickaxe]]s are now the tool for breaking pistons.
	\|Pistons no longer pop off redstone components placed on the back when retracting.		\|Pistons no longer pop off redstone components placed on the back when retracting.
	\|~~[[Minecraft:~~Crimson ~~planks]]~~ and [[Minecraft:~~warped~~ planks]] can now be used to craft pistons.}}		\|Crimson and warped [[Minecraft:planks]] can now be used to craft pistons.}}
	\|{{HistoryLine\|\|1.17\|dev=20w45a\|Particles now appear if a block is broken by a piston.}}		\|{{HistoryLine\|\|1.17\|dev=20w45a\|Particles now appear if a block is broken by a piston.}}
	\|{{HistoryLine\|\|1.19\|dev=22w11a\|[[Minecraft:Mangrove planks]] can now be used to craft pistons.}}		\|{{HistoryLine\|\|1.19\|dev=22w11a\|[[Minecraft:Mangrove planks]] can now be used to craft pistons.}}