Minecraft:Piston/Technical components

Template:Split Pistons and sticky pistons have 2 technical blocks that cannot be obtained. These include the piston head and moving piston blocks.

Piston head

The piston head (Template:In) or (sticky) piston arm collision (Template:In) is a technical block that appears as the front part of an extended piston. It is not available in the Creative inventory and does not drop anything when removed.

Normally, piston heads are created automatically when a piston extends. However, they can also be placed manually using the Template:Cmd command. Alternatively a Minecraft:debug stickTemplate:Only can be used to change the facing direction of a piston head that's currently attached to a piston base. Piston heads that do not have a valid support block behind them will be removed when receiving a shape update from behind Template:In, or when receiving a Minecraft:block update from any direction Template:In.

In rare cases, a client-side, duplicate piston head can appear when placing a piston next to a power source Template:In, due to client-server desync issues.<ref>Template:Bug</ref> These client-side piston heads cannot be broken directly but can be removed by placing another block in the same location.

Template:IN, normal and sticky piston heads are distinguished by a block state. Template:IN, they use separate block IDs. The normal and sticky piston heads can be obtained as items Template:In with the commands /give @s pistonarmcollision and /give @s stickypistonarmcollision. They face down when placed.

Template:IN, piston head blocks do not actually have a texture, as the piston arm texture is part of the piston Minecraft:block entity, and piston heads that aren't connected to a piston base have neither collisions nor an Minecraft:interaction box.

Natural generation

Heads of sticky pistons powered with redstone generate in Minecraft:jungle pyramid and Minecraft:ancient city.

Block states

Template:Edition: Template:Bst Template:Bst Template:Bst

Template:Edition:
Piston Head: Template:Bst

Sticky Piston Head: Template:Bst

Moving piston

The moving piston (Template:In) or moving block (Template:In), also known as block 36 due to its pre-flattening block ID, is an unobtainable technical block that holds a Minecraft:block entity (unless it was placed with a Minecraft:command) which contains the block the Minecraft:piston is currently moving. Since moving blocks vary in how much of each grid cell they occupy, they can't be stored as normal Minecraft:blocks and are instead stored as block entity data. Multiple moving piston blocks may be used during the extension/retraction process, depending on how many blocks the piston is moving. At the end of the piston stroke, the moving piston blocks are replaced with either the carried block, the piston head (during extensions), or the piston itself (during retractions); but if it is placed with the use of commands it remains indefinitely.Template:Only

When placed by commands, the game does not assign a block entity to the moving piston block,Template:Verify therefore its properties are different than usual: it's invisible, has no collisions, and cannot be broken without the use of Minecraft:TNT, commands, or a structure generating over it (such as the end platform). Although it is non-solid, fluids cannot pass through it. It also prevents players from building at its location. Minecraft:Mobs can see through it, but cannot walk through it. The game treats the block as a Minecraft:stone block when it comes to the player's footstep sounds. It is similar to Minecraft:invisible bedrock in properties with the exception that the player can walk through the moving piston but not invisible bedrock.

Block states

Template:JE: Template:Bst Template:Bst

Block data

The moving piston has a block entity associated with it that holds additional data about the block.

Template:JE: Template:See also

<section begin="block data" />

• Template:Nbt Block entity data
  • Template:Nbt inherit/blockentity
  • Template:Nbt: The moving block represented by this block entity.
    • Template:Nbt inherit/block state
  • Template:Nbt: 1 or 0 (true/false) – true if the piston is extending instead of withdrawing.
  • Template:Nbt: Direction that the piston pushes (0=down, 1=up, 2=north, 3=south, 4=west, 5=east).
  • Template:Nbt: How far the block has been moved. Starts at 0.0, and increments by 0.5 each tick, including the tick on which moving the piston is created. If the value is 1.0 or higher at the start of a tick of the block entity (before incrementing), then the block transforms into the stored blockState. Negative values can be used to increase the time until transformation.
  • Template:Nbt: 1 or 0 (true/false) – true if the block represents the piston head itself, false if it represents a block being pushed.

<section end="block data" />

Template:BE:

See Minecraft:Bedrock Edition level format/Block entity format.

Data values

ID

Template:JE: Template:ID table Template:ID table Template:ID table

Template:BE:

History

Trivia

• Mobs can spawn inside the piston head block.
• Template:IN, the piston head is invisible and non-solid when placed with commands. The moving piston disappears shortly after being placed with commands in this edition.
• The moving_piston is transparent and does not emit light.
  • If a light-emitting block is moved, the player can see it turn dark briefly. If an opaque block is moved, the player may see light passing through it.

Navigation

Minecraft:ja:ピストン/テクニカルブロック Minecraft:ko:피스톤/기술적 구성 요소 Minecraft:pt:Pistão/Componentes técnicos