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)).
Related issues
is duplicated by
relates to
MC-11242
When you jump and place a fence post under you you will get inside the fence post
MCPE-32638
Lily pads can be placed inside players in a confined space
MC-221278
Lily pads can instantly break when placed near immobile boats
MCPE-112516
Lily pads can be placed inside entities
MC-112516
Current Language: ~~ERROR~~ NullPointerException: null
testing discovered
Attachments
Comments
migrated
kumasasa
Separated this ticket from MC-2208
migrated
Confirmed.
Ezekiel
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.
migrated
Confirmed for 14w30c
migrated
Confirmed for 14w31a
migrated
Confirmed for 1.8.9 and 15w51b.
migrated
Confirmed for 16w02a.
migrated
Confirmed for 1.9-pre3
migrated
Confirmed for 1.9.0
migrated
Confirmed for 1.9.1-pre3.
migrated
Confirmed for 1.9.3-pre3.
migrated
Confirmed for 1.9.4.
migrated
Confirmed for 16w20a.
migrated
Confirmed for 16w21a.
migrated
Confirmed for 16w21b.
migrated
Confirmed for 1.10-pre1.
migrated
Confirmed for 1.10-pre2.
migrated
Please do not mark unreleased versions as affected.
You don't have access to them yet.
migrated
Confirmed for 1.10.
FaRo1
When unreleased versions shouldn't be marked as affected (for obvious reasons), why is it possible at all?
Ezekiel
It's a limitation with the software we use to manage tickets
migrated
Confirmed for 1.10.1.
JUE13
Confirmed for 1.12.1
muzikbike
Affects 18w11a
muzikbike
Affects 18w14a
muzikbike
Affects 18w14b
muzikbike
Affects 18w15a
muzikbike
Affects Bedrock Edition, see MCPE-32638
muzikbike
Affects 18w16a
muzikbike
Affects 18w19a
muzikbike
Affects 18w20a
muzikbike
Affects 18w20b. Possibly intentional via resolution of MCPE-32638.
muzikbike
Affects 18w20c
muzikbike
Affects 18w21a
muzikbike
Affects 18w22a
muzikbike
Affects 18w22b
muzikbike
Affects 18w22c
muzikbike
Affects 1.13-pre1
muzikbike
Affects 1.13-pre2
muzikbike
Affects 1.13-pre3
muzikbike
Affects 1.13-pre4
migrated
Please do not mark unreleased versions as affected.
You don't have access to them yet.
Jack McKalling
Confirmed for 18w50a
Jack McKalling
Confirmed for 19w03b
Jack McKalling
Confirmed for 19w03c
Jack McKalling
Comfirmed for 19w04a
Jack McKalling
Confirmed for 19w04b
Jack McKalling
Confirmed for 19w06a
Jack McKalling
Confirmed for 19w09a
Jack McKalling
Confirmed for 19w11b
Jack McKalling
Confirmed for 19w12b
Jack McKalling
Confirmed for 19w13b
Jack McKalling
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.
muzikbike
...hence why there's a testing discovered link for MC-147266.
Jack McKalling
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.
FaRo1
Being able to place blocks with hitboxes inside yourself is always a bug (except for scaffolding).
Confirmed for 1.14-pre1.
Uriel Salischiker
Can you share reproduction steps Fabian?
FaRo1
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.
Jack McKalling
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.
FaRo1
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.
Jack McKalling
Confirmed for 1.14 pre-3
Jack McKalling
Confirmed for 1.14 pre-5
Jack McKalling
Confirmed for 1.14
Jack McKalling
Confirmed for 1.14.1 pre-1
Jack McKalling
Confirmed for 1.14.1 pre-2
Jack McKalling
Confirmed for 1.14.1
migrated
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.
[media]
Jack McKalling
Confirmed fixed in 20w22a
mgatland