Killing falling_block entity: texture disappears while falling but the block is still there
The bug
When you have a repeating command block (command: kill @e[type=falling_block]) and you let an anvil (sand/gravel/dragon egg) fall on the ground it doesn't fall, only the texture disappears. So it is still there as a ghost block (you can't walk through). When you update the anvil by placing a block where the anvil was before it appears, floating in the air.
Code analysis
Code analysis by Marcono1234 can be found in this comment.
Linked Issues
is duplicated by11
MC-47892Killing FallingSand really fast, you dont see the blockDuplicateMC-59562Minecraft FallingSand /kill BugDuplicateMC-76969Dragon Egg Converting to Block on RelogDuplicateMC-93834Floating gravelDuplicateMC-123724A ghost block made of sandDuplicateMC-173002Falling blocks that are removed before they can remove the block that spawned them create ghost air blocksDuplicateMC-175011Weird falling_block behaviour by killing falling_block entities too fastDuplicateMC-181057Floating gravity blocksDuplicateMC-184012Killing a falling block causes numerous bugsDuplicateMC-207548floating gravity blocksDuplicateMC-238200Falling blocks don't fall when /kill @e[type=falling_block] is executed at the same timeDuplicate
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
Created Issue:
/kill @e[type=!Player] anvil texture diappears while falling but anvil is still there
When you have a commandblock (command: kill @e[type=!Player]) attached to a fast commandblock clock, and you let a anvil fall on the ground it doesn't fall, only the texture disappears. So it is still there (you can't walk through). When you update the anvil by placing a block where the anvil was before it appears, floating in the air.
Environment
Java 8 Update 5; Windows 8.1 Pro; GPU: NVIDIA; CPU: Intel
Attachments1
/kill @e[type=!Player] anvil texture diappears while falling but anvil is still there (applies to all FallingSand entities)
relates to
is duplicated by
When you have a commandblock (command: kill @e [type=!Player] ) attached to a fast commandblock clock, and you let a anvil fall on the ground it doesn't fall, only the texture disappears. So it is still there (you can't walk through). When you update the anvil by placing a block where the anvil was before it appears, floating in the air.
Code analysis by Marcono1234 can be found in this comment .
is duplicated by
is duplicated by
relates to
When you have a commandblock (command: kill @e[type=
!Player])attached to a fast commandblock clock,and you let a anvil fall on the ground it doesn't fall, only the texture disappears. So it is still there (you can't walk through). When you update the anvil by placing a block where the anvil was before it appears, floating in the air.
Code analysis by Marcono1234 can be found in this comment.
When you have a repeating command block (command: kill @e[type=falling_block]) and you let an anvil (sand/gravel/dragon egg) fall on the ground it doesn't fall, only the texture disappears. So it is still there (you can't walk through). When you update the anvil by placing a block where the anvil was before it appears, floating in the air.
Code analysis by Marcono1234 can be found in this comment.
/kill@e[type=!Player] anviltexture diappears while falling butanvilis still there(applies to all FallingSand entities)Killing falling_block entity: texture disappears while falling but the block is still there
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
When you have a repeating command block (command:
kill @e[type=falling_block]) and you let an anvil (sand/gravel/dragon egg) fall on the ground it doesn't fall, only the texture disappears. So it is still there (you can't walk through). When you update the anvil by placing a block where the anvil was before it appears, floating in the air.
Code analysis by Marcono1234 can be found in this comment.
When you have a repeating command block (command: kill @e[type=falling_block]) and you let an anvil (sand/gravel/dragon egg) fall on the ground it doesn't fall, only the texture disappears. So it is still there (you can't walk through). When you update the anvil by placing a block where the anvil was before it appears, floating in the air.
Code analysis by Marcono1234 can be found in this comment.
Java 8 Update 5; Windows 8.1 Pro; GPU: NVIDIA; CPU: Intel
relates to
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
is duplicated by
When you have a repeating command block (command: kill @e[type=falling_block]) and you let an anvil (sand/gravel/dragon egg) fall on the ground it doesn't fall, only the texture disappears. So it is still there (you can't walk through). When you update the anvil by placing a block where the anvil was before it appears, floating in the air.
Code analysis by Marcono1234 can be found in this comment.
The bug
When you have a repeating command block (command: kill @e[type=falling_block]) and you let an anvil (sand/gravel/dragon egg) fall on the ground it doesn't fall, only the texture disappears. So it is still there (you can't walk through). When you update the anvil by placing a block where the anvil was before it appears, floating in the air.
Code analysis
Code analysis by Marcono1234 can be found in this comment.
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
is duplicated by
is duplicated by
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
The bug
When you have a repeating command block (command: kill @e[type=falling_block]) and you let an anvil (sand/gravel/dragon egg) fall on the ground it doesn't fall, only the texture disappears. So it is still there as a ghost block (you can't walk through). When you update the anvil by placing a block where the anvil was before it appears, floating in the air.
Code analysis
Code analysis by Marcono1234 can be found in this comment.
![[Helper] Misode](../../../data/avatars/users/93314.png){kind=small}
is duplicated by
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
is duplicated by
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
Can confirm in 1.17.
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
Low![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
is duplicated by
Dupe of MC-56037.
Dupe of MC-56037.
Dupe of MC-56037.
This bug does occur in the most recent minecraft version, but it is a duplicate of MC-56037.
Confirmed in 16w15b. Dupe of MC-56037.
Thank you for your report!
We're actually already tracking this issue in MC-56037, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Duplicate of MC-56037, please provide any new information as a comment to that report.
Duplicate of MC-56037, provide a screenshot so I can make sure its a duplicate.
Duplicate of MC-56037.
Duplicate of MC-56037.
Thank you for your report!
We're tracking this issue in MC-56037, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 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.
cannot confirm in 1.19.4 and 23w12a, i think the reason is because this issue related to MC-56037 and that bug has been fixed in 22w03a
Confirmed for 14w21b
Also happens with all FallingSand entities like sand, red sand, gravel and dragon egg
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.
Confirmed for 1.8.2 pre-4. The entity will disappear immediately, and you can't walk through where it was. The impassible area is where the entity was when it died, not where it would have landed. Reloading the world fixes the bug, and causes the block to appear. It will not update, and will remain floating.
Also, if you update the invisible block, it will appear for a moment, then disappear again.
This bug (or a very similar one) will also occur if the fallingsand is teleported away.
Confirmed in 16w15b. Any blocks placed in the block where the invisible sand block is will disappear from your inventory and will make the sand appear. They will reappear in your inventory when you reload the world.
Please link to this comment in the description
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The method net.minecraft.block.BlockFalling.checkFallable(World, BlockPos) only spawns the FallingSand entity but does not replace the block (this was maybe done to prevent FallingSand duplication?). The method net.minecraft.entity.item.EntityFallingBlock.onUpdate() then removes the block if the FallingSand entity has a Time of 0. It looks like the problem is that the server does not call the method before the FallingSand entity is killed. However as the client receives the packets delayed, it creates a FallingSand entity but runs the onUpdate() method before receiving the packet to kill the FallingSand entity. This way the server did not remove the block, however the client did.
Edit: Expected behavior described in
MC-72248.Relates to
MC-72248Can confirm for MC 1.12.1.
Confirmed for 1.13.1.
Guys I know how to fix it. Place buggy blocks again (just place anything they will back) and use /fill for this cuboid of bug blocks. Helped for me
Can confirm in 20w48a.
Can confirm in 21w03a.
Can confirm in 21w05b.
Can confirm in 21w06a.
Can confirm in 21w07a. Video attached.
I cannot reproduce the texture disappearance in 1.17. The block texture doesn't disappear in Avoma's video either. Have I misunderstood this issue?
@Marcono1234 Seems this is related to: MC-151488
This must have been fixed at some point. It happens in 1.18 but doesn't in 1.19, so somewhere in between.
I'm on 23w04a and cannot reproduce, the blocks are killed and disappear.
This has been fixed along with
MC-72248.