MC-130961A ghost block is created when an enderman places a moving piston head ("Technical Block 36")
A ghost block will be created when an enderman puts down a moving piston head block.
Steps to Reproduce:
- Summon an enderman in an enclosed space
- Modify what block it holds:
execute as @e[type=minecraft:enderman] run data merge entity @s {carriedBlockState:{Name:"minecraft:moving_piston"}} - Wait for it to place the block
(If it's taking too long, tick sprint the game) - Try and place a block where the enderman set down the moving piston head
Expected & Observed Results:
→ A ghost block will be present where the enderman placed it. Despite the block appearing to be air, the player will not be able to interact with the block postion.
→ The moving piston head would either not be allowed as something an enderman can hold, something it can't put down, or it would just be destroyed when placed.
Notes:
- In previous versions, the piston_extension block has been used in Enderman anti-griefing command block designs, because they could previously not place them and would also not have any visual appearance.
- Thee ghost block can be destroyed with TNT or /setblock
![[Mod] Jiingy](../../../data/avatars/users/91802.png){kind=small}
Created Issue:
Endermen can place "Moving Piston" block (previously Piston Extension / Technical Block 36)
In previous versions, the piston_extension block has used in Enderman anti-griefing command block designs.
Running a command such as;
entitydata @e[type=enderman] {carried:"minecraft:piston_extension"}would prevent an Enderman being able to pick up or move other blocks. The "Piston Extension" block was ideal because it had no associated item (nothing to drop on death) and could not be placed by the Enderman.
Testing in 1.13-pre1 with this command;
execute as @e[type=minecraft:enderman] run data merge entity @s {carriedBlockState:{Name:"minecraft:moving_piston"}has similar function in regards to block held and drops on death, but the "Moving Piston" block can now, unfortunately, be placed in the world by the Enderman leaving an transparent, invisible block that prevents the player from placing other blocks and can only be broken with TNT or replaced with the setblock command.
Environment
Windows 10, Java 1.8.0_25 (64bit)
In previous versions, the piston_extension block has been used in Enderman anti-griefing command block designs.
Running a command such as;
entitydata @e[type=enderman] {carried:"minecraft:piston_extension"}would prevent an Enderman being able to pick up or move other blocks. The "Piston Extension" block was ideal because it had no associated item (nothing to drop on death) and could not be placed by the Enderman.
Testing in 1.13-pre1 with this command;
execute as @e[type=minecraft:enderman] run data merge entity @s {carriedBlockState:{Name:"minecraft:moving_piston"}has similar function in regards to block held and drops on death, but the "Moving Piston" block can now, unfortunately, be placed in the world by the Enderman leaving an transparent, invisible block that prevents the player from placing other blocks and can only be broken with TNT or replaced with the setblock command.
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
In previous versions, the piston_extension block has been used in Enderman anti-griefing command block designs.
Running a command such as;
entitydata @e[type=enderman] {carried:"minecraft:piston_extension"}would prevent an Enderman being able to pick up or move other blocks. The "Piston Extension" block was ideal because it had no associated item (nothing to drop on death) and could not be placed by the Enderman.
Testing in 1.13-pre1 with this command;
execute as @e[type=minecraft:enderman] run data merge entity @s {carriedBlockState:{Name:"minecraft:moving_piston"}}has similar function in regards to block held and drops on death, but the "Moving Piston" block can now, unfortunately, be placed in the world by the Enderman leaving an transparent, invisible block that prevents the player from placing other blocks and can only be broken with TNT or replaced with the setblock command.
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Helper] Jack McKalling](../../../data/avatars/users/92859.png){kind=small}
Windows 10, Java 1.8.0_25 (64bit)
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
![[Mod] Chandler](../../../data/assets/gravatar/triwonder81.png){kind=small}
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
Endermen can place "Moving Piston" block (previously Piston Extension /Technical Block 36)A ghost block is created when an enderman places a piston head ("Technical Block 36")
In previous versions, the piston_extension block has been used inEndermananti-griefing command block designs.Running a command such as;
entitydata @e[type=enderman] {carried:"minecraft:piston_extension"}would prevent an Enderman being able to pick up or move other blocks. The "Piston Extension" block was ideal because it had no associated item (nothing to drop on death) and could not be placed by the Enderman.
Testing in 1.13-pre1 with this command;
execute as @e[type=minecraft:enderman] run data merge entity @s {carriedBlockState:{Name:"minecraft:moving_piston"}}has similar function in regards to block held and drops on death, but the "Moving Piston" block can now, unfortunately, be placed in the world by the Enderman leaving an transparent, invisible block that prevents the player from placing other blocks and can only be broken with TNT or replaced with the setblock command.
A ghost block will be created when an enderman puts down a moving piston head block.
Steps to Reproduce:
- Summon an enderman in an enclosed space
- Modify what block it holds:
execute as @e[type=minecraft:enderman] run data merge entity @s {carriedBlockState:{Name:"minecraft:moving_piston"}}- Wait for it to place the block
(If it's taking too long, tick sprint the game)- Try and place a block where the enderman set down the moving piston head
Expected & Observed Results:
Notes:
- In previous versions, the piston_extension block has been used in Enderman anti-griefing command block designs, because they could previously not place them and would also not have any visual appearance.
- Thee ghost block can be destroyed with TNT or /setblock
A ghost block is created when an enderman places a moving piston head ("Technical Block 36")
A ghost block will be created when an enderman puts down a moving piston head block.
Steps to Reproduce:
- Summon an enderman in an enclosed space
- Modify what block it holds:
execute as @e[type=minecraft:enderman] run data merge entity @s {carriedBlockState:{Name:"minecraft:moving_piston"}}- Wait for it to place the block
(If it's taking too long, tick sprint the game)- Try and place a block where the enderman set down the moving piston head
Expected & Observed Results:
-A ghost block will be present where the enderman placed it. Despite the block appearing to be air, the player will not be able to interact with the block postion.
-The moving piston head would either not be allowed as something an enderman can hold, something it can't put down, or it would just be destroyed when placed.Notes:
- In previous versions, the piston_extension block has been used in Enderman anti-griefing command block designs, because they could previously not place them and would also not have any visual appearance.
- Thee ghost block can be destroyed with TNT or /setblock
A ghost block will be created when an enderman puts down a moving piston head block.
Steps to Reproduce:
- Summon an enderman in an enclosed space
- Modify what block it holds:
execute as @e[type=minecraft:enderman] run data merge entity @s {carriedBlockState:{Name:"minecraft:moving_piston"}}- Wait for it to place the block
(If it's taking too long, tick sprint the game)- Try and place a block where the enderman set down the moving piston head
Expected & Observed Results:
Notes:
- In previous versions, the piston_extension block has been used in Enderman anti-griefing command block designs, because they could previously not place them and would also not have any visual appearance.
- Thee ghost block can be destroyed with TNT or /setblock
Maybe my issue is different from the OP, but in case it isn't, this could be related to MC-130961
I believe 1.13 allows you with datapacks to empty the list of blocks that endermen can pick up. This is a far superior fix than running a looped command block. Even if this is a proper bug, I wanted to share the (official) workaround.
Now that is something I didn't realise! Thanks for the heads-up
This is still an issue in Minecraft 1.15.2
FYI. This is still an issue in Java Edition 1.16.5
This is still an issue in 1.19. (We have to destroy our End Island on our realm because thousands of Endermen are spawning and not despawning.)
Also related but separate bug, this is still occurring even though the carriedBlockState command block was broken.
Affects 24w09a, I'd like to request ownership of this issue.