[MC-667] Lily pads can be placed intersecting entities Created: 26/Oct/12  Updated: 07/Apr/21  Resolved: 28/May/20

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2, Minecraft 1.7.4, Minecraft 14w04b, Minecraft 14w05b, Minecraft 1.7.5, Minecraft 14w11b, Minecraft 1.7.6-pre1, Minecraft 1.7.10, Minecraft 14w30b, Minecraft 14w30c, Minecraft 14w31a, Minecraft 14w33c, Minecraft 14w34a, Minecraft 14w34b, Minecraft 14w34c, Minecraft 14w34d, Minecraft 1.8-pre1, Minecraft 1.8, Minecraft 1.8.1-pre3, Minecraft 1.8.6, Minecraft 15w36d, Minecraft 15w44b, Minecraft 15w45a, Minecraft 1.8.9, Minecraft 15w51b, Minecraft 16w02a, Minecraft 1.9 Pre-Release 3, Minecraft 1.9, Minecraft 1.9.1 Pre-Release 3, Minecraft 1.9.1, Minecraft 1.9.2, Minecraft 16w14a, Minecraft 1.9.3 Pre-Release 3, Minecraft 1.9.4, Minecraft 16w20a, Minecraft 16w21a, Minecraft 16w21b, Minecraft 1.10 Pre-Release 1, Minecraft 1.10 Pre-Release 2, Minecraft 1.10, Minecraft 1.10.1, Minecraft 1.10.2, Minecraft 16w32a, Minecraft 16w32b, Minecraft 16w33a, Minecraft 16w35a, Minecraft 1.11.2, Minecraft 1.12, Minecraft 1.12.1, Minecraft 1.12.2, Minecraft 17w50a, Minecraft 18w11a, Minecraft 18w14a, Minecraft 18w14b, Minecraft 18w15a, Minecraft 18w16a, Minecraft 18w19a, Minecraft 18w20a, Minecraft 18w20b, Minecraft 18w20c, Minecraft 18w21a, Minecraft 18w22a, Minecraft 18w22b, Minecraft 18w22c, Minecraft 1.13-pre1, Minecraft 1.13-pre2, Minecraft 1.13-pre3, Minecraft 1.13-pre4, Minecraft 1.13-pre5, Minecraft 1.13-pre6, Minecraft 1.13-pre7, Minecraft 1.13-pre8, Minecraft 1.13-pre9, Minecraft 1.13-pre10, Minecraft 1.13, Minecraft 18w30a, Minecraft 18w30b, Minecraft 18w31a, Minecraft 18w32a, Minecraft 18w33a, Minecraft 1.13.1-pre1, Minecraft 1.13.1-pre2, Minecraft 1.13.1, Minecraft 1.13.2-pre1, Minecraft 1.13.2-pre2, Minecraft 1.13.2, Minecraft 18w43b, Minecraft 18w43c, Minecraft 18w44a, Minecraft 18w45a, Minecraft 18w46a, Minecraft 18w47a, Minecraft 18w47b, Minecraft 18w48a, Minecraft 18w48b, Minecraft 18w49a, Minecraft 18w50a, Minecraft 19w02a, Minecraft 19w03a, Minecraft 19w03b, Minecraft 19w03c, Minecraft 19w04a, Minecraft 19w04b, Minecraft 19w05a, Minecraft 19w06a, Minecraft 19w07a, Minecraft 19w08a, Minecraft 19w09a, Minecraft 19w11a, Minecraft 19w11b, Minecraft 19w12a, Minecraft 19w12b, Minecraft 19w13a, Minecraft 19w13b, Minecraft 19w14a, Minecraft 19w14b, Minecraft 1.14 Pre-Release 1, Minecraft 1.14 Pre-Release 2, Minecraft 1.14 Pre-Release 3, Minecraft 1.14 Pre-Release 4, Minecraft 1.14 Pre-Release 5, Minecraft 1.14, Minecraft 1.14.1, Minecraft 1.14.2 Pre-Release 1, Minecraft 1.14.2 Pre-Release 3, Minecraft 1.14.2, Minecraft 1.14.3 Pre-Release 1, Minecraft 1.14.3 Pre-Release 2, Minecraft 1.14.3 Pre-Release 3, Minecraft 1.14.3 Pre-Release 4, Minecraft 1.14.3, Minecraft 1.14.4 Pre-Release 1, Minecraft 1.14.4 Pre-Release 2, Minecraft 1.14.4 Pre-Release 3, Minecraft 1.14.4 Pre-Release 4, Minecraft 1.14.4 Pre-Release 5, Minecraft 1.14.4 Pre-Release 6, 1.14.4 Pre-Release 7, 1.14.4, 19w34a, 19w35a, 19w36a, 19w37a, 19w38b, 19w38a, 19w39a, 19w40a, 19w41a, 19w42a, 19w44a, 19w45a, 19w45b, 19w46a, 19w46b, 1.15 Pre-release 1, 1.15 Pre-Release 2, 1.15 Pre-release 3, 1.15 Pre-release 4, 1.15 Pre-release 5, 1.15 Pre-release 6, 1.15 Pre-release 7, 1.15, 1.15.1, 1.15.1 Pre-release 1, 1.15.2 Pre-Release 1, 1.15.2 Pre-release 2, 1.15.2, 20w06a, 20w07a, 20w08a, 20w09a, 20w10a, 20w11a, 20w12a, 20w13a, 20w13b, 20w14a, 20w15a, 20w16a, 20w17a, 20w18a, 20w19a, 20w20a, 20w20b, 20w21a
Fix Version/s: 20w22a

Type: Bug
Reporter: Connor Steppie Assignee: [Mojang] Matthew Gatland
Resolution: Fixed Votes: 23
Labels: collision, lily_pad, water

Attachments: PNG File 2020-04-27_19.12.12.png    
Issue Links:
Bonfire Testing
testing discovered MC-136405 Lily pads and frogspawn cannot be pla... Open
testing discovered MC-147266 Intersecting solid blocks under certa... Resolved
Duplicate
is duplicated by MC-42250 Placing a lily pad in the same block ... Resolved
is duplicated by MC-165859 Special placing of a lily pad lets yo... Resolved
is duplicated by MC-172703 Place lily pad and break instantly wh... Resolved
is duplicated by MC-173029 Can place lilypads through boats Resolved
Relates
relates to MC-11242 When you jump and place a fence post ... Resolved
relates to MCPE-32638 Lily pads can be placed inside player... Resolved
relates to MC-2208 Blocks with special placement can be ... Resolved
relates to MC-221278 Lily pads can instantly break when pl... Open
relates to MCPE-112516 Lily pads can be placed inside entities Open
CHK:
Confirmation Status: Confirmed
Category:
Hitboxes
Mojang Priority: Low

 Description   

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)).



 Comments   
Comment by [Helper] Jack McKalling [ 30/May/20 ]

Confirmed fixed in 20w22a

Comment by Flare [ 27/Apr/20 ]

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.

Comment by [Helper] Jack McKalling [ 13/May/19 ]

Confirmed for 1.14.1

Comment by [Helper] Jack McKalling [ 09/May/19 ]

Confirmed for 1.14.1 pre-2

Comment by [Helper] Jack McKalling [ 07/May/19 ]

Confirmed for 1.14.1 pre-1

Comment by [Helper] Jack McKalling [ 23/Apr/19 ]

Confirmed for 1.14

 

Comment by [Helper] Jack McKalling [ 18/Apr/19 ]

Confirmed for 1.14 pre-5

Comment by [Helper] Jack McKalling [ 16/Apr/19 ]

Confirmed for 1.14 pre-3

 

Comment by Fabian Röling [ 10/Apr/19 ]

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.

Comment by [Helper] Jack McKalling [ 10/Apr/19 ]

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.

Comment by Fabian Röling [ 10/Apr/19 ]

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.

Comment by [Mod] Urielsalis [ 10/Apr/19 ]

Can you share reproduction steps Fabian?

Comment by Fabian Röling [ 10/Apr/19 ]

Being able to place blocks with hitboxes inside yourself is always a bug (except for scaffolding).

Confirmed for 1.14-pre1.

Comment by [Helper] Jack McKalling [ 10/Apr/19 ]

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.

Comment by Connor Steppie [ 03/Apr/19 ]

...hence why there's a testing discovered link for MC-147266.

Comment by [Helper] Jack McKalling [ 03/Apr/19 ]

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.

Comment by [Helper] Jack McKalling [ 29/Mar/19 ]

Confirmed for 19w13b

Comment by [Helper] Jack McKalling [ 21/Mar/19 ]

Confirmed for 19w12b

Comment by [Helper] Jack McKalling [ 14/Mar/19 ]

Confirmed for 19w11b

Comment by [Helper] Jack McKalling [ 28/Feb/19 ]

Confirmed for 19w09a

Comment by [Helper] Jack McKalling [ 06/Feb/19 ]

Confirmed for 19w06a

Comment by [Helper] Jack McKalling [ 30/Jan/19 ]

Confirmed for 19w04b

Comment by [Helper] Jack McKalling [ 24/Jan/19 ]

Comfirmed for 19w04a

Comment by [Helper] Jack McKalling [ 19/Jan/19 ]

Confirmed for 19w03c

Comment by [Helper] Jack McKalling [ 17/Jan/19 ]

Confirmed for 19w03b

 

Comment by [Helper] Jack McKalling [ 12/Dec/18 ]

Confirmed for 18w50a

Comment by [Bot] Arisa [ 25/Jul/18 ]

Please do not mark unreleased versions as affected.
You don't have access to them yet.

Comment by Connor Steppie [ 27/Jun/18 ]


Affects 1.13-pre4

Comment by Connor Steppie [ 21/Jun/18 ]

Affects 1.13-pre3

Comment by Connor Steppie [ 15/Jun/18 ]

Affects 1.13-pre2

Comment by Connor Steppie [ 04/Jun/18 ]

Affects 1.13-pre1

Comment by Connor Steppie [ 31/May/18 ]

Affects 18w22c

Comment by Connor Steppie [ 31/May/18 ]

Affects 18w22b

Comment by Connor Steppie [ 30/May/18 ]

Affects 18w22a

Comment by Connor Steppie [ 23/May/18 ]

Affects 18w21a

Comment by Connor Steppie [ 18/May/18 ]

Affects 18w20c

Comment by Connor Steppie [ 16/May/18 ]

Affects 18w20b. Possibly intentional via resolution of MCPE-32638.

Comment by Connor Steppie [ 15/May/18 ]

Affects 18w20a

Comment by Connor Steppie [ 09/May/18 ]

Affects 18w19a

Comment by Connor Steppie [ 19/Apr/18 ]

Affects 18w16a

Comment by Connor Steppie [ 16/Apr/18 ]

Affects Bedrock Edition, see MCPE-32638

Comment by Connor Steppie [ 11/Apr/18 ]

Affects 18w15a

Comment by Connor Steppie [ 05/Apr/18 ]

Affects 18w14b

Comment by Connor Steppie [ 04/Apr/18 ]

Affects 18w14a

Comment by Connor Steppie [ 14/Mar/18 ]

Affects 18w11a

Comment by user33 [ 09/Aug/17 ]

Confirmed for 1.12.1

Comment by null (Inactive) [ 22/Jun/16 ]

Confirmed for 1.10.1.

Comment by [Mod] Ezekiel (ezfe) [ 09/Jun/16 ]

It's a limitation with the software we use to manage tickets

Comment by Fabian Röling [ 09/Jun/16 ]

When unreleased versions shouldn't be marked as affected (for obvious reasons), why is it possible at all?

Comment by null (Inactive) [ 08/Jun/16 ]

Confirmed for 1.10.

Comment by [Bot] Arisa [ 07/Jun/16 ]

Please do not mark unreleased versions as affected.
You don't have access to them yet.

Comment by null (Inactive) [ 07/Jun/16 ]

Confirmed for 1.10-pre2.

Comment by null (Inactive) [ 03/Jun/16 ]

Confirmed for 1.10-pre1.

Comment by null (Inactive) [ 26/May/16 ]

Confirmed for 16w21b.

Comment by null (Inactive) [ 25/May/16 ]

Confirmed for 16w21a.

Comment by null (Inactive) [ 18/May/16 ]

Confirmed for 16w20a.

Comment by null (Inactive) [ 11/May/16 ]

Confirmed for 1.9.4.

Comment by null (Inactive) [ 05/May/16 ]

Confirmed for 1.9.3-pre3.

Comment by James (inactive) [ 15/Mar/16 ]

Confirmed for 1.9.1-pre3.

Comment by Commander Sealand [ 01/Mar/16 ]

Confirmed for 1.9.0

Comment by Erik [ 25/Feb/16 ]

Confirmed for 1.9-pre3

Comment by James (inactive) [ 13/Jan/16 ]

Confirmed for 16w02a.

Comment by James (inactive) [ 22/Dec/15 ]

Confirmed for 1.8.9 and 15w51b.

Comment by Liam Whitt [ 31/Jul/14 ]

Confirmed for 14w31a

Comment by Kevin Reid [ 25/Jul/14 ]

Confirmed for 14w30c

Comment by [Mod] Ezekiel (ezfe) [ 25/Jul/14 ]

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.

Comment by Deleted account [ 04/Feb/14 ]

Confirmed.

Comment by Kumasasa [ 26/Jan/14 ]

Separated this ticket from MC-2208

Generated at Sun Jan 12 11:51:49 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.