Falling sand creates invisible blocks
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
/summon minecraft:falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:stone"}}
- Take note as to whether or not falling sand creates invisible blocks.
Observed Behavior:
Falling sand creates invisible blocks.
Expected Behavior:
Falling sand would not be able to create invisible blocks.
Code Analysis:
Code analysis by Marcono1234 can be found in this comment.
Linked Issues
is duplicated by17
MC-55106FallingSand creates an invisible glitch blockDuplicateMC-74271FallingSand with Spawner (when it spawn on the ground) don't work at 1.8+DuplicateMC-75096Command Blocks dissapear when fallingsand entitys are summoned at the same cordinatesDuplicateMC-101553FallingSand entity creates ghost blocksDuplicateMC-110627Falling Sand Causes Glitchy BarriersDuplicateMC-114403Summoning a falling skull in a skull with cause both skulls to disappearDuplicateMC-128993summoned falling blocks could form a invisible border that slows down player's movement speed and make the sight shakeDuplicateMC-131250Replacing block with falling block creates ghost blockDuplicateMC-136460Ghost Block... NOW WITH COMMAND BLOCKS!DuplicateMC-139687Ghost blocks still exist when summoning falling block entitiesDuplicateMC-152737Summoned falling_block entities will incorrectly delete client-side blocksDuplicateMC-169421The Ghost Block is back in another formDuplicateMC-193496Block gets semi deleted when spawning falling block inside itDuplicateMC-201177FallingBlocks delete blocks of the same blockstate when 'inside' each other and leave an invisible barrierDuplicateMC-238047Walking on falling block entities in the same block as it's blockstate causes glitchy movementDuplicateMC-243092Summon a "falling block" within a block of same type causes the block to stop rendering or just disappear.DuplicateMC-245601You can create a ghost block when summoning a falling blockDuplicate
- Fixed
![[Mod] Avoma](../../../data/avatars/users/86198.png)
[Mod] Avoma
Ivo Hageluken- 28
- 21
- Confirmed
Normal- Commands
1.8 - 1.18.1
1.8 1.8.1 1.8.2-pre4 1.8.8 15w37a 15w47c 1.9-pre4 1.9 1.9.4 16w21b 1.10.2 16w43a 1.12 1.12.1 1.12.2 18w16a 1.13.1 1.13.2 18w48a 18w48b 18w49a 18w50a 1.14.1 1.14.2-pre2 1.14.2-pre3 1.14.2-pre4 1.14.4 19w39a 1.15.1 20w13a 20w17a 1.16.1 1.16.3 1.16.4 20w46a 20w51a 21w03a 1.16.5 21w05b 21w06a 21w07a 21w08b 21w10a 21w11a 21w13a 21w14a 21w15a 21w16a 21w17a 21w19a 21w20a 1.17-pre1 1.17-pre3 1.17-pre4 1.17-pre5 1.17-rc1 1.17-rc2 1.17 1.17.1-pre1 1.17.1-pre2 1.17.1-pre3 1.17.1-rc1 1.17.1 21w37a 21w38a 21w39a 21w40a 21w41a 21w42a 21w43a 1.18-pre1 1.18-pre7 1.18-rc3 1.18 1.18.1- 22w05a
Created Issue:
Falling sand creates invisible blocks
- Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon FallingSand ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],TileID:XX}where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Environment
Server/Client side when summoning falling sand in a block with a velocity upwards
cannot confirm (used stone as I used a resoursepack, but it works fine for all blocks I used)
if you didn't use a grass block (tested it) then provide the block you used
note: because of the motion it shoots up, then falls down again
2014-09-22_17.15.29.png
is duplicated by
is duplicated by
is duplicated by
Server/Client side when summoning falling sand in a block with a velocity upwards
relates to
- Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon FallingSand ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],TileID:XX}where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
- Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon FallingSand ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],TileID:XX}where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
- Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon FallingSand ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],TileID:XX}where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
- Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon FallingSand ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],TileID:XX}where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
- Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon FallingSand ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],Block:"minecraft:grass"}where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
- Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon FallingSand ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],Block:"minecraft:grass"}where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
- Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon FallingSand ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],Block:"minecraft:XX"}where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
- Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summonFallingSand~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],Block:"minecraft:XX"}where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
- Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],Block:"minecraft:XX"}where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
is duplicated by
is duplicated by
relates to
relates to
is duplicated by
Labels/Tags: "invinsible" <> "invisible"
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
is duplicated by
is duplicated by
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
- Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon falling_block ~ ~-1 ~{Time:1,Motion:[0.0,1.0,0.0],Block:"minecraft:XX"}where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
- Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:XX"}}
where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
is duplicated by
is duplicated by
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
![[Mod] NeunEinser](../../../data/avatars/users/39263.png){kind=small}
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
relates to
![[Mod] Chandler](../../../data/assets/gravatar/triwonder81.png){kind=small}
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
- Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:XX"}}
where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
The Bug:
Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
/summon falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:stone"}}→
Notice how this block becomes invisible and the falling sand does work.
Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:XX"}}
where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
The Bug:
Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
/summon falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:stone"}}→
Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible.
- Try this:
/summon falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:XX"}}
where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
/summon falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:stone"}}→
Information:
Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible. Try this: /summon falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:XX"}} where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment.
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
![[Mod] LateLag](../../../data/avatars/users/92884.png){kind=small}
is duplicated by
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
/summon minecraft:falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:stone"}}→
Information:
Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible. Try this: /summon falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:XX"}} where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment.
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
/summon minecraft:falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:stone"}}→
Information:
Spawn in a falling sand entity at a block location, and make the falling sand TileID the same as the one of were you spawn it. So lets say there is a grass block at 0 0 0 I spawn in a falling sand (GRASS) at 0 0 0 , the block will become invisible. Try this: /summon falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:XX"}} where XX is the ID of the block under you. This block becomes invisible and the falling sand does work.
Code analysis by Marcono1234 in this comment.
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
/summon minecraft:falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:stone"}}
- →
Code Analysis:
Code analysis by Marcono1234 can be found in this comment.
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
/summon minecraft:falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:stone"}}
- →
Code Analysis:
Code analysis by Marcono1234 can be found in
this comment.The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
/summon minecraft:falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:stone"}}
- →
Code Analysis:
Code analysis by Marcono1234 can be found in this comment.
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
/summon minecraft:falling_block ~ ~-1 ~ {Time:1,Motion:[0.0,1.0,0.0],BlockState:{Name:"minecraft:stone"}}
- →
Code Analysis:
Code analysis by Marcono1234 can be found in this comment.
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
- →
Code Analysis:
Code analysis by Marcono1234 can be found in this comment.
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
- →
Code Analysis:
Code analysis by Marcono1234 can be found in
this comment.The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
- →
Code Analysis:
Code analysis by Marcono1234 can be found in this comment.
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
- →
Code Analysis:Code analysis by Marcono1234 can be found in
this comment.The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
- →
Expected Behavior:
The expected behavior would be that falling sand cannot create invisible blocks.
Code Analysis:
Code analysis by Marcono1234 can be found in this comment.
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
- →
Expected Behavior:
The expected behavior would be that falling sand cannot create invisible blocks.
Code Analysis:
Code analysis by Marcono1234 can be found in
this comment.The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
- →
Expected Behavior:
The expected behavior would be that falling sand cannot create invisible blocks.
Code Analysis:
Code analysis by Marcono1234 can be found in this comment.
is duplicated by
MC-237229
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
- →
Expected Behavior:
The expected behavior would be that falling sand cannotcreate invisible blocks.Code Analysis:
Code analysis by Marcono1234 can be found in this comment.
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
Observed Behavior:
Falling sand creates invisible blocks.
Expected Behavior:
Falling sand would not be able to create invisible blocks.
Code Analysis:
Code analysis by Marcono1234 can be found in this comment.
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
Observed Behavior:
Falling sand creates invisible blocks.
Expected Behavior:
Falling sand would not be able to create invisible blocks.
Code Analysis:
Code analysis by Marcono1234 can be found in
this comment.The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
Observed Behavior:
Falling sand creates invisible blocks.
Expected Behavior:
Falling sand would not be able to create invisible blocks.
Code Analysis:
Code analysis by Marcono1234 can be found in this comment.
is duplicated by
![[Mod] Les3awe](../../../data/avatars/users/79847.png){kind=small}
is duplicated by
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
Observed Behavior:
Falling sand creates invisible blocks.
Expected Behavior:
Falling sand would not be able to create invisible blocks.
Code Analysis:
Code analysis by Marcono1234 can be found in this comment.
The Bug:
Falling sand creates invisible blocks.
Steps to Reproduce:
- Run the following command whilst standing on a stone block.
- Take note as to whether or not falling sand creates invisible blocks.
Observed Behavior:
Falling sand creates invisible blocks.
Expected Behavior:
Falling sand would not be able to create invisible blocks.
Code Analysis:
Code analysis by Marcono1234 can be found in this comment.
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
is duplicated by
Probably duplicates MC-72248
Relates to:
Is duplicated by/reason for:
I don't really understand how the whole FallingSand Time tag should work, but it is definitely pretty strange. First of all, it is a byte which decreases all possibilities in an extreme way. Maybe that should get fixed.
Special time tags:
- 0 despawn just after it was spawned, but doesn't drop an item! and replaces block if it has the same block id
- Any other number will also "replace" the block but leaves a ghost block (
MC-72248orMC-55106)
For whatever reason this happens:
- -128 is some ticks later -124
- -1 is some ticks later 3
- 1 is some ticks later 5
- 127 is some ticks later -125
I really have no clue to what it is counting down, but you can also not prevent this timer to count down...
What you experience might be MC-72248
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-72248
Duplicate of MC-72248. If you have not, please use the search function in the future to check whether your bug already has been reported. More than 50% of all bugs ever reported had to be closed as duplicate.
Thank you for your report!
However, this issue has been closed as a Duplicate of MC-72248.
It has been linked to this report. If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Relates to MC-72248
The bug
Falling blocks are not rendered if the block state they are displaying is at the block position of the entity. The shadow of the falling block is still rendered.
Expected behavior
The expected behavior is that falling block entities are always rendered. Otherwise the player might be confused why he sees a shadow but no entity or why he cannot click / hit at a position because he cannot see the falling block entity blocking his view.
Even with regular falling blocks which begin to fall changing it to have the entity always be rendered does not make a visible difference.
How to reproduce
- Place a block, for example a trapdoor
/setblock ~2 ~ ~ oak_trapdoor
- Summon a falling block entity displaying the block
/summon falling_block ~2 ~0.9 ~ {NoGravity:1b,Time:-2147483648,BlockState:{Name:"oak_trapdoor"}}Note: The block will probably get invisible because of
MC-72248. Right clicking the trapdoor block should solve this.
→ You should see that the falling block entity is not rendered unless you break the trapdoor or change its state, for example by right clicking it
Code analysis
Based on 1.11.2 decompiled using MCP 9.35 rc1
The method net.minecraft.client.renderer.entity.RenderFallingBlock.doRender(EntityFallingBlock, double, double, double, float, float) does not render the falling block entity if the block state it is displaying is at the block position of the entity.
Probably duplicates MC-72248
I still cannot reproduce I'll ask helpers and mods if they can. For the second one that you mention I'm pretty sure that would be MC-72248.
Does MC-72248 describe this issue?
Sounds like a duplicate of MC-72248
This actually appears to be a duplicate of MC-72248, as this ticket provides more information regarding the issue, along with a detailed code analysis.
Duplicate of MC-72248.
Thank you for your report!
We're tracking this issue in MC-72248, 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! If you think it was incorrect, please notify us on Discord or Reddit
Sounds like MC-72248. The client thinks it became air.
Thank you for your report!
We're tracking this issue in MC-72248, 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.
MC-72248, yeah.
Thank you for your report!
We're tracking this issue in MC-72248, 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.
I believe that this issue duplicates MC-72248
Thank you for your report!
We're tracking this issue in MC-72248, 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.
This has been fixed along with MC-72248.
Confirmed in single player survival. Very interesting. However this appears to be a duplicate of
MC-48476.confirmed just if anyone misunderstands it, the block your standing on becomes invisible
Someone might double check me since I'm a newb. The dupe I mentioned above looks right for what he's reporting but it might be something slightly different. Apologies if I got it wrong.
it is diffrent, this is about the block below turning invisible, that was about the summoned falling sand turning invisible
"it is diffrent, this is about the block below turning invisible, that was about the summoned falling sand turning invisible"
True, I use this for a plugin that is how I found out.
The Tag TileID is deprecated, use the tag Block instead
it may be depreciated, but this bug also happens when using the Block tag
Confirmed for
What is also strange, when you use
/summon FallingSand ~ ~-1 ~ {Time:1,Block:command_block,TileEntityData:{Command:/say Hi}}And do this on top of a command block with a command in it, then place at the bugging block another block (like stone), all NBT data gets deleted.
This only happens when you try to "overwrite" the bugged block. When you reopen the world, the first command block has still its command.
This is dupe of
MC-55106.I believe I know the cause of this bug. FallingSand entities have a special behavior where they delete the block they are inside if it has the same ID and their Time = 0. You can see the 1.7 implementation of this behavior here:
https://github.com/Bukkit/mc-dev/blob/master/net/minecraft/server/EntityFallingBlock.java#L76
The isStatic check above makes this code only run on the server. In the 1.8 code (which is not online for me to link to) this was moved outside the isStatic check and so the client is running it too. Because the Time property is not sent to the client, FallingSand entities always spawn with Time 0 and thus always delete the block.
Confirmed for
Duplicates indeed
MC-55106, but as this one is more active I rather suggest marking the other report as duplicateConfirmed for 15w47c
https://youtu.be/J3EiojcvJvY
Still seeing it as of 1.9 pre 2, I get it using a fast shovel, beating up a mix of dirt and sand or gravel on a low-ping or local vanilla server, survival, no commands are needed.
@jo:
MC-5694.Yes, my problem was
MC-5694.I then took the time to verify our issue here,
MC-72248, for 1.9pre4, as 'thanks'.jo: Is 1.9-pre4 affected or not ?
Ugh, been too long out of a shop... 'verify' is usually for fixes. :/
Sadly, 1.9-pre4 is still affected by summoned falling sand creating invisible blocks.
The enviroment is supposed to contain pc details.
Confirmed for
Please update the provided command. The Block tag (String) is used now
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.
It looks like Last Username was correct with his analysis (method net.minecraft.entity.item.EntityFallingBlock.onUpdate()). Replacing an existing block should be done server-side only because the client receives the block update packets anyways.
Confirmed for 1.12-pre6
Can confirm for MC 1.12.1.
Can confirm for 19w39a.
Affects 20w13a.
Can confirm in 20w46a.
Can confirm in 20w51a.
Can confirm in 21w03a.
Can confirm in 21w05b.
Can confirm in 21w06a.
I am happy to take ownership of this ticket since the reporter has been inactive since 2014.
I was able to reproduce this in 1.18.1, but can no longer in 22w03a, therefore, this has been fixed in 22w03a.
I am also unable to reproduce this issue in 22w05a.
Just for clarification purposes, this was fixed in 22w03a as well and not just 22w05a.