| Type: | Bug | ||
| Reporter: | Connor Steppie | Assignee: | [Mojang] Matthew Gatland |
| Resolution: | Fixed | Votes: | 23 |
| Labels: | collision, lily_pad, water | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CHK: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Confirmation Status: | Confirmed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Category: |
Hitboxes
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Mojang Priority: | Low | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
| 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 |
| 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 |
| 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. |
| Comment by Connor Steppie [ 27/Jun/18 ] |
|
|
| 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 |
| 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 |
| 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. |
| 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 |