MC-129017Commands and structure blocks cannot properly create a moving piston block (no block entity created)
The bug
As the title says, when attempting to create a moving_piston block, the block entity is not created.
How to reproduce
- Type
setblock ~ ~ ~ minecraft:moving_piston
→ Now the command can be run without NBT data
→ See it also suggests adding NBT data by suggesting the { character - Finish the command:
setblock ~ ~ ~ minecraft:moving_piston{blockState:{Name:"minecraft:piston_head",Properties:{facing:"south",short:"false",type:"normal"}},facing:3,progress:0.0f,source:1b,extending:1b}→ It says the block has been placed, but there's nothing visible
- Type
/data get block ~ ~ ~
→ It says the target block is not a block entity, and using the previous command in the same spot says it could not set the block. Note: using that same command on a moving block created by a piston does return the block entity
Affected methods
- setblock
- fill
- clone
- structure loading
Code analysis
Using MCP 1.12 names:
The tab-complete suggestion for NBT data occurs due to net.minecraft.block.Block.hasTileEntity() method returning true for the net.minecraft.block.BlockPistonMoving block. However, the block entity itself is not created because net.minecraft.block.BlockPistonMoving.createNewTileEntity() returns null.
Linked Issues
- Unresolved
user-f2760- 12
- 7
- Confirmed
Normal- Platform
- Commands
14w21b - 23w43b
14w21b 1.10.2 1.12.2 18w02a 18w16a 18w19b 1.13 18w30b 1.13.1-pre1 1.13.1 1.13.2 18w43a 18w45a 18w46a 18w47b 18w48a 18w48b 18w49a 19w04b 19w07a 19w12b 19w13b 19w14a 19w14b 1.14.3 1.15.2 20w12a 1.16 1.16.2 21w05a 21w13a 21w20a 1.17.1 1.18.1 1.18.2 22w12a 1.19.2 1.19.3 1.19.4-pre3 1.19.4 1.20.1 1.20.2 23w43b
Created Issue:
Commands and structure blocks can not properly create a moving piston block (no block entity created)
As the title says, when attempting to create a moving_piston block, the block entity is not created.
Steps to reproduce:
- Type
setblock ~ ~ ~ minecraft:moving_piston- See it suggests NBT data ({)
- Finish the command:
setblock ~ ~ ~ minecraft:moving_piston{blockState:{Name:"minecraft:piston_head",Properties:{facing:"south",short:"false",type:"normal"}},facing:3,progress:0.0f,source:1b,extending:1b}- It says the block has been placed, but there's nothing visible.
- Type
/data get block ~ ~ ~- It says no block entity was found. Note: using that same command on a moving block created by a piston does return the block entity
Affected methods:
- setblock
- fill
- clone
- structure loading
clones
![[Mod] Skylinerw](../../../data/assets/gravatar/skylinerw.png){kind=small}
The bug
As the title says, when attempting to create a moving_piston block, the block entity is not created.
Steps to reproduce:
- Type
setblock ~ ~ ~ minecraft:moving_piston- See it suggests NBT data ({)
- Finish the command:
setblock ~ ~ ~ minecraft:moving_piston{blockState:{Name:"minecraft:piston_head",Properties:{facing:"south",short:"false",type:"normal"}},facing:3,progress:0.0f,source:1b,extending:1b}- It says the block has been placed, but there's nothing visible.
- Type
/data get block ~ ~ ~- It says no block entity was found. Note: using that same command on a moving block created by a piston does return the block entity
Affected methods:
- setblock
- fill
- clone
- structure loading
Code analysis
Using MCP 1.12 names:
The tab-complete suggestion for NBT data occurs due to net.minecraft.block.Block.hasTileEntity() method returning true for the net.minecraft.block.BlockPistonMoving block. However, the block entity itself is not created because net.minecraft.block.BlockPistonMoving.createNewTileEntity() returns null.
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
The bug
As the title says, when attempting to create a moving_piston block, the block entity is not created.
Steps to reproduce:
- Type
setblock ~ ~ ~ minecraft:moving_piston- See it suggests NBT data ({)
- Finish the command:
setblock ~ ~ ~ minecraft:moving_piston{blockState:{Name:"minecraft:piston_head",Properties:{facing:"south",short:"false",type:"normal"}},facing:3,progress:0.0f,source:1b,extending:1b}- It says the block has been placed, but there's nothing visible.
- Type
/data get block ~ ~ ~- It says no block entity was found. Note: using that same command on a moving block created by a piston does return the block entity
Affected methods:
- setblock
- fill
- clone
- structure loading
Code analysis
Using MCP 1.12 names:
The tab-complete suggestion for NBT data occurs due to net.minecraft.block.Block.hasTileEntity() method returning true for the net.minecraft.block.BlockPistonMoving block. However, the block entity itself is not created because net.minecraft.block.BlockPistonMoving.createNewTileEntity() returns null.
The bug
As the title says, when attempting to create a moving_piston block, the block entity is not created.
How to reproduce
- Type
setblock ~ ~ ~ minecraft:moving_piston→ See it suggests NBT data ({)
- Finish the command:
setblock ~ ~ ~ minecraft:moving_piston{blockState:{Name:"minecraft:piston_head",Properties:{facing:"south",short:"false",type:"normal"}},facing:3,progress:0.0f,source:1b,extending:1b}→ It says the block has been placed, but there's nothing visible
- Type
/data get block ~ ~ ~→ It says no block entity was found. Note: using that same command on a moving block created by a piston does return the block entity
Affected methods:
- setblock
- fill
- clone
- structure loading
Code analysis
Using MCP 1.12 names:
The tab-complete suggestion for NBT data occurs due to net.minecraft.block.Block.hasTileEntity() method returning true for the net.minecraft.block.BlockPistonMoving block. However, the block entity itself is not created because net.minecraft.block.BlockPistonMoving.createNewTileEntity() returns null.
Commands and structure blocks cannot properly create a moving piston block (no block entity created)
The bug
As the title says, when attempting to create a moving_piston block, the block entity is not created.
How to reproduce
- Type
setblock ~ ~ ~ minecraft:moving_piston→ See it suggests NBT data ({)
- Finish the command:
setblock ~ ~ ~ minecraft:moving_piston{blockState:{Name:"minecraft:piston_head",Properties:{facing:"south",short:"false",type:"normal"}},facing:3,progress:0.0f,source:1b,extending:1b}→ It says the block has been placed, but there's nothing visible
- Type
/data get block ~ ~ ~→ It says no block entity was found. Note: using that same command on a moving block created by a piston does return the block entity
Affected methods
:
- setblock
- fill
- clone
- structure loading
Code analysis
Using MCP 1.12 names:
The tab-complete suggestion for NBT data occurs due to net.minecraft.block.Block.hasTileEntity() method returning true for the net.minecraft.block.BlockPistonMoving block. However, the block entity itself is not created because net.minecraft.block.BlockPistonMoving.createNewTileEntity() returns null.
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
The bug
As the title says, when attempting to create a moving_piston block, the block entity is not created.
How to reproduce
- Type
setblock ~ ~ ~ minecraft:moving_piston→ See it suggests NBT data ({)
- Finish the command:
setblock ~ ~ ~ minecraft:moving_piston{blockState:{Name:"minecraft:piston_head",Properties:{facing:"south",short:"false",type:"normal"}},facing:3,progress:0.0f,source:1b,extending:1b}→ It says the block has been placed, but there's nothing visible
- Type
/data get block ~ ~ ~→ It says
no block entity was found. Note: using that same command on a moving block created by a piston does return the block entityAffected methods
- setblock
- fill
- clone
- structure loading
Code analysis
Using MCP 1.12 names:
The tab-complete suggestion for NBT data occurs due to net.minecraft.block.Block.hasTileEntity() method returning true for the net.minecraft.block.BlockPistonMoving block. However, the block entity itself is not created because net.minecraft.block.BlockPistonMoving.createNewTileEntity() returns null.
The bug
As the title says, when attempting to create a moving_piston block, the block entity is not created.
How to reproduce
- Type
setblock ~ ~ ~ minecraft:moving_piston→ See it suggests NBT data ({)
- Finish the command:
setblock ~ ~ ~ minecraft:moving_piston{blockState:{Name:"minecraft:piston_head",Properties:{facing:"south",short:"false",type:"normal"}},facing:3,progress:0.0f,source:1b,extending:1b}→ It says the block has been placed, but there's nothing visible
- Type
/data get block ~ ~ ~→ It says the target block is not a block entity, and using the previous command in the same spot says it could not set the block. Note: using that same command on a moving block created by a piston does return the block entity
Affected methods
- setblock
- fill
- clone
- structure loading
Code analysis
Using MCP 1.12 names:
The tab-complete suggestion for NBT data occurs due to net.minecraft.block.Block.hasTileEntity() method returning true for the net.minecraft.block.BlockPistonMoving block. However, the block entity itself is not created because net.minecraft.block.BlockPistonMoving.createNewTileEntity() returns null.
The bug
As the title says, when attempting to create a moving_piston block, the block entity is not created.
How to reproduce
- Type
setblock ~ ~ ~ minecraft:moving_piston→ See it suggests NBT data ({)
- Finish the command:
setblock ~ ~ ~ minecraft:moving_piston{blockState:{Name:"minecraft:piston_head",Properties:{facing:"south",short:"false",type:"normal"}},facing:3,progress:0.0f,source:1b,extending:1b}→ It says the block has been placed, but there's nothing visible
- Type
/data get block ~ ~ ~→ It says the target block is not a block entity, and using the previous command in the same spot says it could not set the block. Note: using that same command on a moving block created by a piston does return the block entity
Affected methods
- setblock
- fill
- clone
- structure loading
Code analysis
Using MCP 1.12 names:
The tab-complete suggestion for NBT data occurs due to net.minecraft.block.Block.hasTileEntity() method returning true for the net.minecraft.block.BlockPistonMoving block. However, the block entity itself is not created because net.minecraft.block.BlockPistonMoving.createNewTileEntity() returns null.
The bug
As the title says, when attempting to create a moving_piston block, the block entity is not created.
How to reproduce
- Type
setblock ~ ~ ~ minecraft:moving_piston→
See it suggests NBT data ({)Now the command can be run without NBT data- Finish the command:
setblock ~ ~ ~ minecraft:moving_piston{blockState:{Name:"minecraft:piston_head",Properties:{facing:"south",short:"false",type:"normal"}},facing:3,progress:0.0f,source:1b,extending:1b}→ It says the block has been placed, but there's nothing visible
- Type
/data get block ~ ~ ~→ It says the target block is not a block entity, and using the previous command in the same spot says it could not set the block. Note: using that same command on a moving block created by a piston does return the block entity
Affected methods
- setblock
- fill
- clone
- structure loading
Code analysis
Using MCP 1.12 names:
The tab-complete suggestion for NBT data occurs due to net.minecraft.block.Block.hasTileEntity() method returning true for the net.minecraft.block.BlockPistonMoving block. However, the block entity itself is not created because net.minecraft.block.BlockPistonMoving.createNewTileEntity() returns null.
The bug
As the title says, when attempting to create a moving_piston block, the block entity is not created.
How to reproduce
- Type
setblock ~ ~ ~ minecraft:moving_piston→
See it suggestsNBT data({)Now the command can be run without NBT data- Finish the command:
setblock ~ ~ ~ minecraft:moving_piston{blockState:{Name:"minecraft:piston_head",Properties:{facing:"south",short:"false",type:"normal"}},facing:3,progress:0.0f,source:1b,extending:1b}→ It says the block has been placed, but there's nothing visible
- Type
/data get block ~ ~ ~→ It says the target block is not a block entity, and using the previous command in the same spot says it could not set the block. Note: using that same command on a moving block created by a piston does return the block entity
Affected methods
- setblock
- fill
- clone
- structure loading
Code analysis
Using MCP 1.12 names:
The tab-complete suggestion for NBT data occurs due to net.minecraft.block.Block.hasTileEntity() method returning true for the net.minecraft.block.BlockPistonMoving block. However, the block entity itself is not created because net.minecraft.block.BlockPistonMoving.createNewTileEntity() returns null.
The bug
As the title says, when attempting to create a moving_piston block, the block entity is not created.
How to reproduce
- Type
setblock ~ ~ ~ minecraft:moving_piston→ Now the command can be run without NBT data
→ See it also suggests adding NBT data by suggesting the { character- Finish the command:
setblock ~ ~ ~ minecraft:moving_piston{blockState:{Name:"minecraft:piston_head",Properties:{facing:"south",short:"false",type:"normal"}},facing:3,progress:0.0f,source:1b,extending:1b}→ It says the block has been placed, but there's nothing visible
- Type
/data get block ~ ~ ~→ It says the target block is not a block entity, and using the previous command in the same spot says it could not set the block. Note: using that same command on a moving block created by a piston does return the block entity
Affected methods
- setblock
- fill
- clone
- structure loading
Code analysis
Using MCP 1.12 names:
The tab-complete suggestion for NBT data occurs due to net.minecraft.block.Block.hasTileEntity() method returning true for the net.minecraft.block.BlockPistonMoving block. However, the block entity itself is not created because net.minecraft.block.BlockPistonMoving.createNewTileEntity() returns null.
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
Normal![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Does MC-129017 describe your issue?
May relate to MC-129017
I suggest resolving this as duplicate of MC-129017.
Actually a duplicate of MC-129017.
Thank you for your report!
We're resolving and linking this ticket forward as a duplicate of MC-129017, as that ticket contains more detailed information and/or has already been triaged by Mojang.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Confirmed for 1.13.1-pre1
Confirmed for 1.16.1; if Asteraoth doesn't oppose, I'd like to be the reporter again.
Can confirm in 21w20a
Can confirm in 1.18.2 if the following command is valid:
/setblock ~ ~ ~ minecraft:moving_piston{blockState:[{Name:"minecraft:red_stained_glass"}],progress:1.0}