Lily pads can be placed intersecting entities
The bug
Be on the surface of water, look down, and right-click with a lily pad. The lily pad will be placed intersecting the player, which is not possible with normal solid blocks.
It is easiest to test this by standing in one-block-high water, but it works no matter the depth. Both Survival and Creative mode.
Also, if you stand on the edge of water (half on a solid block, half on water) and place a lily pad, then move out towards the lily pad, you will get the jumpy "stuck in midair" effect. Presumably this is due to client/server disagreement on whether you're on top of or falling through the lily pad.
As of 19w14a, placing a lily pad within yourself will also trigger the crawling animation.
Code analysis
Based on 1.11.2 decompiled using MCP 9.35 rc1
Placing lily pad on side of block
The class BlockLilyPad does not override the method net.minecraft.block.BlockBush.getCollisionBoundingBox(IBlockState, IBlockAccess, BlockPos) which returns no collision box.
Placing lilypad without looking at block
The method net.minecraft.item.ItemLilyPad.onItemRightClick(World, EntityPlayer, EnumHand) does not test at all if the block can be placed there or if entities (method World.mayPlace(Block, BlockPos, boolean, EnumFacing, Entity)).
Linked Issues
testing discovered2
is duplicated by4
relates to5
- Fixed
Connor Steppie
Kevin Reid
[Mojang] Matthew Gatland- 23
- 16
- Confirmed
Low
- Hitboxes
- collision lily_pad water
1.4.2 - 20w21a
1.4.2 1.7.4 14w04b 14w05b 1.7.5 14w11b 1.7.6-pre1 1.7.10 14w30b 14w30c 14w31a 14w33c 14w34a 14w34b 14w34c 14w34d 1.8-pre1 1.8 1.8.1-pre3 1.8.6 15w36d 15w44b 15w45a 1.8.9 15w51b 16w02a 1.9-pre3 1.9 1.9.1-pre3 1.9.1 1.9.2 16w14a 1.9.3-pre3 1.9.4 16w20a 16w21a 16w21b 1.10-pre1 1.10-pre2 1.10 1.10.1 1.10.2 16w32a 16w32b 16w33a 16w35a 1.11.2 1.12 1.12.1 1.12.2 17w50a 18w11a 18w14a 18w14b 18w15a 18w16a 18w19a 18w20a 18w20b 18w20c 18w21a 18w22a 18w22b 18w22c 1.13-pre1 1.13-pre2 1.13-pre3 1.13-pre4 1.13-pre5 1.13-pre6 1.13-pre7 1.13-pre8 1.13-pre9 1.13-pre10 1.13 18w30a 18w30b 18w31a 18w32a 18w33a 1.13.1-pre1 1.13.1-pre2 1.13.1 1.13.2-pre1 1.13.2-pre2 1.13.2 18w43b 18w43c 18w44a 18w45a 18w46a 18w47a 18w47b 18w48a 18w48b 18w49a 18w50a 19w02a 19w03a 19w03b 19w03c 19w04a 19w04b 19w05a 19w06a 19w07a 19w08a 19w09a 19w11a 19w11b 19w12a 19w12b 19w13a 19w13b 19w14a 19w14b 1.14-pre1 1.14-pre2 1.14-pre3 1.14-pre4 1.14-pre5 1.14 1.14.1 1.14.2-pre1 1.14.2-pre3 1.14.2 1.14.3-pre1 1.14.3-pre2 1.14.3-pre3 1.14.3-pre4 1.14.3 1.14.4-pre1 1.14.4-pre2 1.14.4-pre3 1.14.4-pre4 1.14.4-pre5 1.14.4-pre6 1.14.4-pre7 1.14.4 19w34a 19w35a 19w36a 19w37a 19w38b 19w38a 19w39a 19w40a 19w41a 19w42a 19w44a 19w45a 19w45b 19w46a 19w46b 1.15-pre1 1.15-pre2 1.15-pre3 1.15-pre4 1.15-pre5 1.15-pre6 1.15-pre7 1.15 1.15.1 1.15.1-pre1 1.15.2-pre1 1.15.2-pre2 1.15.2 20w06a 20w07a 20w08a 20w09a 20w10a 20w11a 20w12a 20w13a 20w13b 20w14a 20w15a 20w16a 20w17a 20w18a 20w19a 20w20a 20w20b 20w21a- 20w22a
Created Issue:
Lily Pads can be placed intersecting oneself
Stand in one-block-high water, look down, and right-click with a lily pad. The lily pad will be placed intersecting the player, which is not possible with normal solid blocks.
duplicates
Resolving this ticket as duplicate, because
MC-2208is of better quality.
relates to
duplicates
Stand in one-block-highwater, look down, and right-click with a lily pad. The lily pad will be placed intersecting the player, which is not possible with normal solid blocks.Be on the surface of water, look down, and right-click with a lily pad. The lily pad will be placed intersecting the player, which is not possible with normal solid blocks.
It is easiest to test this by standing in one-block-high water, but it works no matter the depth. Both Survival and Creative mode.
Also, if you stand on the edge of water (half on a solid block, half on water) and place a lily pad, then move out towards the lily pad, you will get the jumpy "stuck in midair" effect. Presumably this is due to client/server disagreement on whether you're on top of or falling through the lily pad.
is duplicated by
The bug
Be on the surface of water, look down, and right-click with a lily pad. The lily pad will be placed intersecting the player, which is not possible with normal solid blocks.
It is easiest to test this by standing in one-block-high water, but it works no matter the depth. Both Survival and Creative mode.
Also, if you stand on the edge of water (half on a solid block, half on water) and place a lily pad, then move out towards the lily pad, you will get the jumpy "stuck in midair" effect. Presumably this is due to client/server disagreement on whether you're on top of or falling through the lily pad.
Code analysis
Placing lily pad on side of block
The class BlockLilyPad does not override the method net.minecraft.block.BlockBush.getCollisionBoundingBox(IBlockState, IBlockAccess, BlockPos) which returns no collision box.
Placing lilypad without looking at block
The method net.minecraft.item.ItemLilyPad.onItemRightClick(World, EntityPlayer, EnumHand) does not test at all if the block can be placed there or if entities (method World.mayPlace(Block, BlockPos, boolean, EnumFacing, Entity)).
The bug
Be on the surface of water, look down, and right-click with a lily pad. The lily pad will be placed intersecting the player, which is not possible with normal solid blocks.
It is easiest to test this by standing in one-block-high water, but it works no matter the depth. Both Survival and Creative mode.
Also, if you stand on the edge of water (half on a solid block, half on water) and place a lily pad, then move out towards the lily pad, you will get the jumpy "stuck in midair" effect. Presumably this is due to client/server disagreement on whether you're on top of or falling through the lily pad.
Code analysis
Based on 1.11.2 decompiled using MCP 9.35 rc1
Placing lily pad on side of block
The class BlockLilyPad does not override the method net.minecraft.block.BlockBush.getCollisionBoundingBox(IBlockState, IBlockAccess, BlockPos) which returns no collision box.
Placing lilypad without looking at block
The method net.minecraft.item.ItemLilyPad.onItemRightClick(World, EntityPlayer, EnumHand) does not test at all if the block can be placed there or if entities (method World.mayPlace(Block, BlockPos, boolean, EnumFacing, Entity)).
relates to
relates to
Confirmed in 1.8-pre1
testing discovered
LilyPads can be placed intersecting the playerLily pads can be placed intersecting the player
testing discovered
The bug
Be on the surface of water, look down, and right-click with a lily pad. The lily pad will be placed intersecting the player, which is not possible with normal solid blocks.
It is easiest to test this by standing in one-block-high water, but it works no matter the depth. Both Survival and Creative mode.
Also, if you stand on the edge of water (half on a solid block, half on water) and place a lily pad, then move out towards the lily pad, you will get the jumpy "stuck in midair" effect. Presumably this is due to client/server disagreement on whether you're on top of or falling through the lily pad.
As of 19w14a, placing a lily pad within yourself will also trigger the crawling animation.
Code analysis
Based on 1.11.2 decompiled using MCP 9.35 rc1
Placing lily pad on side of block
The class BlockLilyPad does not override the method net.minecraft.block.BlockBush.getCollisionBoundingBox(IBlockState, IBlockAccess, BlockPos) which returns no collision box.
Placing lilypad without looking at block
The method net.minecraft.item.ItemLilyPad.onItemRightClick(World, EntityPlayer, EnumHand) does not test at all if the block can be placed there or if entities (method World.mayPlace(Block, BlockPos, boolean, EnumFacing, Entity)).
[Placement] Lily pads can be placed intersecting the player
[Placement]Lily pads can be placed intersecting the player
is duplicated by
Lily pads can be placed intersectingthe playerLily pads can be placed intersecting entities
is duplicated by
is duplicated by
relates to
relates to
Since my report MC-667 was closed as a duplicate of this, I am repeating it here since it is not about blocks placed on blocks, and so might not be actually the same bug:
Stand in one-block-high water, look down, and right-click with a lily pad. The lily pad will be placed intersecting the player.
Stairs placeable intersecting the player confirmed for 14w04b. Note that you must be standing on the lower half of a stair block for this to happen as originally described.
Lily pads placeable intersecting the player confirmed for 14w04b, no special conditions. I stand by my previous claim that MC-667 should be considered a different bug than this, as lily pad placement is unlike regular block placement and the code causing the bug is most likely different.
Duplicate of MC-667
Ok, prepare for something... Could please a mod mark the versions for every bug I tell you here? That would be nice.
I have a world set up for fast bug testing. That means that going into each bug report and saying "Confirmed for 1.10.1" is way more work than actually testing it. So I want to confirm for 1.10.1 with this comment:
MC-4, MC-9, MC-14, MC-87, MC-112, MC-201, MC-212, MC-234, MC-258, MC-460, MC-577, MC-667, MC-679, MC-696, MC-697, MC-849, MC-868, MC-926, MC-957, MC-997, MC-1040, MC-1127, MC-1133, MC-1168, MC-1207, MC-1218, MC-1297, MC-1390, MC-1429, MC-1530, MC-1531, MC-1538, MC-1541, MC-1555, MC-1578, MC-1673, MC-1685, MC-1691, MC-1981 and MC-2023.
All of these are tested in 1.10.1. For some others I have additional information:
MC-711 not testable with my setup because of a crash that's new in 1.10.1.
MC-779: At least some appear outside, didn't test all. What's sure is that no general solution got introduced.
Confirmed MC-1511 for stone button, lever, torch, redstone dust, normal rail, end rod, tripwire hook, ladder and flower pot. Others are untested.
Confirmed MC-1874 for chest, brewing stand, enchanting table and flower pot. Others are untested. It's apparent that there isn't a general solution here either.
Similar to MC-667.
In a 1x1 space of water, a player can place a lily pad inside themselves, causing a brief visual jumping glitch.
Likely resulted from the fix to MC-129863/MC-131116/MC-130572/MC-132482.
This can happen in many different cases:
- Placing a lily pad within yourself (
MC-667) - Closing a door on yourself
- Closing a fence gate on yourself
- Having a piston push a block into your feet
- Solid plants growing within a player (e.g. bamboo, trees)
- Intersecting a falling block after it lands
- Having a piston push a block into your head (likely intended - especially if the pushed block comes from above, and makes for easy entrances to one-block-high passageways)
- Using an ender pearl to enter a one block high area (likely intended - stops you from suffocating, and sounds very useful)
- Closing a trapdoor on yourself (likely intended - makes for easy entrances to one-block-high passageways, assuming the trapdoor is waist height)
It would be best if all intersections with the top half of the player still caused them to start crawling, but all intersections with the bottom half would not.
The underlying issue seems to be that the lily pad is placed despite intersecting with you, see MC-667.
The underlying bug is MC-667 (which previously only covered placing inside players). Therefore I resolved this report as duplicate.
The bug
This is not a duplicate of MCPE-32638, but it clones that ticket. This is a parity issue, since this was fixed for java in 1.16. MC-667 Normally you can’t place blocks inside yourself or other entities, however lily pads can be placed inside entities.
How to reproduce:
- Go into a sea or an ocean and be at the top of the water
- Try to place a lily pad inside yourself
Observed Result: The lily pad is placed and you will get pushed away from it.
Expected Result: The lily pad doesn’t get placed, since it would be placed inside you.
You can place frogspawn over boats on the water:
Steps to Reproduce:
- In a body of water spawn a boat
- Stand over or generally above the boat
- Crouch and use a frogspawn while aiming at the boat
Observed Behavior:
The frogspawn will place on top of the boat.
Expected Result:
Because the boat is the first targeted right-click interaction, when it fails (due to shift click being held), nothing would happen. The frog spawn would only be valid for placement if the player is directly targeting water.

Separated this ticket from
MC-2208Confirmed.
Is this still a concern in the latest Minecraft version 14w30c? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Confirmed for 14w30c
Confirmed for 14w31a
Confirmed for 1.8.9 and 15w51b.
Confirmed for 16w02a.
Confirmed for 1.9-pre3
Confirmed for 1.9.0
Confirmed for 1.9.1-pre3.
Confirmed for 1.9.3-pre3.
Confirmed for 1.9.4.
Confirmed for 16w20a.
Confirmed for 16w21a.
Confirmed for 16w21b.
Confirmed for 1.10-pre1.
Confirmed for 1.10-pre2.
Please do not mark unreleased versions as affected.
You don't have access to them yet.
Confirmed for 1.10.
When unreleased versions shouldn't be marked as affected (for obvious reasons), why is it possible at all?
It's a limitation with the software we use to manage tickets
Confirmed for 1.10.1.
Confirmed for 1.12.1
Affects 18w11a
Affects 18w14a
Affects 18w14b
Affects 18w15a
Affects Bedrock Edition, see
MCPE-32638Affects 18w16a
Affects 18w19a
Affects 18w20a
Affects 18w20b. Possibly intentional via resolution of
MCPE-32638.Affects 18w20c
Affects 18w21a
Affects 18w22a
Affects 18w22b
Affects 18w22c
Affects 1.13-pre1
Affects 1.13-pre2
Affects 1.13-pre3
Affects 1.13-pre4
Please do not mark unreleased versions as affected.
You don't have access to them yet.
Confirmed for 18w50a
Confirmed for 19w03b
Confirmed for 19w03c
Comfirmed for 19w04a
Confirmed for 19w04b
Confirmed for 19w06a
Confirmed for 19w09a
Confirmed for 19w11b
Confirmed for 19w12b
Confirmed for 19w13b
Although still affecting 19w14a, as you attempt to place a lily pad intersecting yourself, you get pushed underneath the lily pad, immediately in the swimming position. Similar to what is described in
MC-141824....hence why there's a testing discovered link for
MC-147266.Due to the new mechanics, I don't think I can reproduce this anymore. If you're supposed to be pushed underneath the lily pad when you place it in yourself.
Being able to place blocks with hitboxes inside yourself is always a bug (except for scaffolding).
Confirmed for 1.14-pre1.
Can you share reproduction steps Fabian?
The same as always: Punch a 1×1×1 hole into the ground, put water in it, stand in it, place lily pad on the water.
When I try that, I get pushed below the lily pad "block" and will thereby not be intersecting anymore. Hence why I don't know how to reproduce this.
Being pushed under might be intended, it might not, but you still placed the block where you were standing. If that was intended, you might as well place a full block on your head level and get pushed under.
Confirmed for 1.14 pre-3
Confirmed for 1.14 pre-5
Confirmed for 1.14
Confirmed for 1.14.1 pre-1
Confirmed for 1.14.1 pre-2
Confirmed for 1.14.1
As of 1.15.2, sneaking on the edge of a shore still allows for unresolved placement of an intersecting lily pad.
The resulting state exhibits some incongruencies:
For the acting client, their self is shown as standing, regardless of input, while their BB remains in a sneaking state.
For peers, both their model and BB are stuck sneaking. Following a server restart, this switches to standing.
Regardless, sneaking input by the actor is reflected in their nametag opacity.
Confirmed fixed in 20w22a