Double-tall plants do not cause updates when broken
The bug
When you place a block that is used to fall (sand, gravel, or anvil) up to a dual grass block or any new plant of two blocks height and break the grass the block just gets stuck when it was supposed to fall.
Code analysis
Code analysis by Marcono1234 can be found in this comment.
Linked Issues
is duplicated by14
- Fixed
Raptor341
- 16
- 13
- Confirmed
- block-update falling_block float tall_grass
13w37a - 1.13-pre2
13w37a 13w38a 13w38b 13w38c 13w39a 13w39b 13w41a 13w41b 1.7.1 1.7.2 13w47a 13w47b 13w47c 1.7.4 14w04b 14w05b 14w06a 14w06b 14w07a 14w08a 1.7.5 14w11b 1.7.9 14w21b 14w25b 14w26b 14w26c 14w33c 14w34a 14w34b 14w34c 14w34d 1.8-pre1 1.8-pre2 1.8 1.8.1 1.8.3 15w36d 15w46a 1.9 1.9.2 1.9.3-pre3 1.9.3 1.9.4 16w20a 1.10.2 1.11.2 17w06a 1.12.2 17w45b 17w46a 17w47a 17w47b 17w50a 18w03b 18w11a 1.13-pre2- 1.13-pre3
Created Issue:
Bug
When you place a block that is used to fall (sand Gravel or anvil) up to a dual grass block or any new plant of 2 blocks wheight and break the grass the block just get stucked where it is and it was supose to fall
Environment
all
BugDouble-tall plants do not cause updates when broken
is duplicated by
duplicates
is duplicated by
duplicates
is duplicated by
relates to
all
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
When you place a block that is used to fall (sand Gravel or anvil) up to a dual grass block or any new plant of 2 blocks wheight and break the grass the block just get stucked where it is and it was supose to fall
Code analysis by Marcono1234 can be found in this comment .
is duplicated by
When you place a block that is used to fall (sand
Gravel or anvil) up to a dual grass block or any new plant of2blockswheight and break the grass the block just get stuckedwhere it is andit was supose to fall
Code analysis by Marcono1234 can be found in this comment.
When you place a block that is used to fall (sand, gravel, or anvil) up to a dual grass block or any new plant of two blocks height and break the grass the block just gets stuck when it was supposed to fall.
Code analysis by Marcono1234 can be found in this comment.
When you place a block that is used to fall (sand, gravel, or anvil) up to a dual grass block or any new plant of two blocks height and break the grass the block just gets stuck when it was supposed to fall.
Code analysis by Marcono1234 can be found in this comment.
The bug
When you place a block that is used to fall (sand, gravel, or anvil) up to a dual grass block or any new plant of two blocks height and break the grass the block just gets stuck when it was supposed to fall.
Code analysis
Code analysis by Marcono1234 can be found in this comment.
is duplicated by
relates to
relates to
Fixed in 1.13-pre6. Was possibly fixed in earlier versions. Please reimplement! If floating blocks can be created during world generation, builders should have access to them too.
Duplicate of MC-31038 - If you have not, please use the search function in the future, to see if your bug has already been submitted. If you could not find the original report, please comment with the keywords you searched for.
Duplicate of MC-31038
Dupe of MC-31038
Duplicate of MC-31038. It's not a lag issue.
Dupe of MC-31038
Thanks for reporting this issue, but this is a duplicate of MC-31038.
Duplicate of MC-31038, if you have not, please use the search function in the future to see if your issue has already been reported.
The bug
Observer blocks do not detect the following actions:
- Chests opening/closing
- Ender chests opening/closing
- Lighting a nether portal
- When a command block is successful (can be detected with a comparator)
- Beacon activating/deactivating
- Something teleported by the end gateway
- Ringing a bell by hand or by projectile
- Brewing stands finish brewing a potion
- Ender dragon head being powered/unpowered
- Left clicking a note block (might be intended)
Fixed
• Fixed in an unknown version (presumably in a 1.17 snapshot):
- Grass blocks changing into podzol blocks when a 2x2 spruce tree grows
• Fixed in 20w14a:
- Don't react to the state change of fences/walls/bars/panes when a tree grows next to them
• Fixed in 1.14.2:
- Shulker Boxes opening/closing
- Don't react to the state change of fences/walls/bars/panes when large mushrooms grow next to them
• Fixed in 17w47a:
- Playing a note block
- Adding or removing a plant from a flower pot
- Farmland going through intermediate stages of hydration 0–6, which appear dry
- Locking / unlocking a redstone repeater
- Connecting / Orientation (north, south, etc) State for Cobblestone Walls
- Shape State for Stairs
- Changes to the data value of fire that signifies flammable surfaces surrounding fire
- The change of facing fences, (stained) glass panes, iron bars, pumpkin/melon stems, tripwire and redstone wire
- Snowy State for:
- Grass Block
- Podzol
- Mycelium
- The opening/closing of the top part of a door by hand, as opposed to by redstone power.
• Fixed in 16w44a:
- Grass/ferns growing into tall grass/tall ferns
- Grass blocks changing to dirt due to sheep "eating" the grass
- Anvil damage changes
- Dragon egg teleports to a destination
- Inserting or removing music discs from a jukebox- 1
- Dry sponge becomes wet
- Changes in number of snow layers
- Placing/breaking top part of a double plant (
MC-31038) - Chorus flower growth to chorus plant
- Opening and closing door, trapdoor or fence gate
- Vine/Crop growing (e.g. cocoa, potatoes, nether wart)
- Placing/removing bottles/potions in/from brewing stands 1
- Placing an eye of ender in an end portal block 1
- Changing the water level of a cauldron with a glass bottle or water bucket 1
- Switching comparators between comparison and subtraction modes.
- Sleeping in beds.
- Changing command block/structure block type
- Changing command block to conditional/unconditional
- Repeater/comparator/detector rail/activator rail/powered rail getting (un)powered
- Nether portals be lit/activated
- End portals be activated
So, I mentioned in my last comment how players can take advantage of trait of 2-block high plants not updating the blocks surrounding their upper blocks when they're placed or broken to make floating gravity-affected blocks without the use of mods or external map editors. My primary purpose in mentioning that feature at all is that I saw it as likely being inevitable that it would be added to this bug report, and I hoped that by me being the one who brought it up, I could perhaps influence things so that when was listed, it was listed with some note of how some Minecraft players would like that feature to remain in the game. I hoped that it would be listed in the bug description as something like this:
"• The upper block of a 2-block tall plant (e.g. tall grass, rose bush) replacing/being replaced by an air block when that plant is placed or broken (MC-31038) (Some players would like this feature to remain in the game because of how they can use it to make floating gravity-affected blocks.)"
However, when it was added, it was simply added like this:
"• Placing/breaking top part of a double plant (MC-31038)"
I know that there are many players who appreciate this feature being in the game, and I would like that voice to be represented in some way here. I'm concerned that the developers might assume that this comment thread is just made up of us adding additional block state changes that don't cause block updates to the list, and miss the concern I expressed that about the idea of making the placing/breaking of 2-block high plants update all surrounding blocks. So I'd like to request that that concern be represented in the bug description, perhaps using the language I suggested above in this comment. Do you (the mods) feel that that's a reasonable request?
Thank you for your report!
However, this issue is Working as Intended.
The report you have submitted is working as intended, mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.
This was caused by the fix in MC-31038
Full Version History – Snapshot Version History – Feature Requests and Suggestions
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki



Confirmed.
Affects 14w04a
Appears to only affect the bottom block since 14w06b.
Confirmed for 14w11b (lower part)
Confirmed for 14w26c
Confirmed for 1.8pre2
Confirmed in 1.8.
Confirmed for 1.8.3
Confirmed affecting 1.8.3 here too (used red sand on peony)
Sorry if I posted this here. Is there a way that I can edit the post so I can add my MC version affected with that bug or I will just needed to comment "Confirmed for ..*" and a mod will rescue and put it into the "Affects Versions" tab in the post?
No, you are correct. Only the reporter of an issue and mods can edit it, for security reasons.
Confirmed for 15w46a
Floating sand can't be done using /setblock command. and only can be done using this method. Weird. :[
Confirmed for Minecraft Release 1.9
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 the reason for this are missing block updates. The problem is that currently the class net.minecraft.block.BlockDoublePlant overrides the method net.minecraft.block.Block.onBlockHarvested(World, BlockPos, IBlockState, EntityPlayer), which is called before the block is set to air. Because of this it cannot replace the other plant part with an update. If it would do that the update would cause the harvested part to be detected as incomplete because it was not removed yet.
To solve this the class should probably override the method net.minecraft.block.Block.onBlockDestroyedByPlayer(World, BlockPos, IBlockState) instead which is called after the block was replaced. Then block updates can be applied without any side effects (hopefully).
Have a look at the method net.minecraft.server.management.PlayerInteractionManager.removeBlock(BlockPos) to see the order.
confirmed for 1.10.2
Please don't fix this bug
Looks like it was 1.13-pre3 :/