Summoning entities with motion that will collide with walls induces entity client-side position desync
The entity still follows the path it's supposed to make in server-side (I've tested it with setblocks @ its position), but the client-side gets desynchronized. It gets fixed when the entity touches the floor.
/summon minecraft:creeper ~ ~ ~ {Motion:[0.0d,3.0d,-9.0d]}
Run the command above with a wall and a hole in -Z direction (also works in all directions in the X-Z plane).
The bug could be affecting the Y axis too, but it's more difficult to appreciate (second 14 of the shorter video, the mobs don't reach the roof even when they should have collided with it).
- Cannot Reproduce
FACS01- 12
- 6
- Confirmed
- Entities
- collision motion
1.13.2 - 1.17.1-pre1
1.13.2 19w04b 19w05a 19w06a 19w07a 19w08b 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-pre1 1.14.1-pre2 1.14.1 1.14.2-pre1 1.14.2-pre2 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 19w34a 19w35a 19w36a 19w37a 19w38b 19w39a 19w40a 19w41a 19w42a 19w44a 19w45b 19w46b 1.15-pre1 1.15-pre2 1.15-pre3 1.15-pre4 1.15-pre6 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 20w14a 20w15a 20w16a 20w17a 20w18a 20w20a 20w21a 20w22a 1.16-pre1 1.16-pre3 1.16-pre5 1.16-pre6 1.16-pre7 1.16-pre8 1.16-rc1 1.16 1.16.1 20w27a 20w28a 20w29a 20w30a 1.16.2-pre1 1.16.2-rc1 1.16.2 1.16.3 1.16.4-pre2 1.16.4-rc1 1.16.4 20w45a 20w46a 20w48a 20w49a 20w51a 21w03a 21w05b 21w07a 21w10a 21w11a 1.17 1.17.1-pre1
Created Issue:
Summoning entities with Motion that will collide with walls induces entity cleint side Position desync
The entity still follows the path it's supposed to make in server-side (I've tested it with setblocks @ its position), but the client-side gets desynchronized. It gets fixed when the entity touches the floor.
/summon minecraft:creeper ~ ~ ~ {Motion:[0.0d,3.0d,-9.0d]}
with a wall and a hole in -Z direction.
but also works in all directions in the X-Z plane.
The bug doesn't affect the Y axis.
Summoning entities with Motion that will collide with walls induces entity cleintside Position desyncSummoning entities with Motion that will collide with walls induces entity client-side Position desync
Summoning entities withMotion that will collide with walls induces entity client-sidePosition desyncSummoning entities with motion that will collide with walls induces entity client-side position desync
The entity still follows the path it's supposed to make in server-side (I've tested it with setblocks @ its position), but the client-side gets desynchronized. It gets fixed when the entity touches the floor.
/summon minecraft:creeper ~ ~ ~ {Motion:[0.0d,3.0d,-9.0d]}
with a wall and a hole in -Z direction.
but also works in all directions in the X-Z plane.
The bug doesn't affect the Y axis.
The entity still follows the path it's supposed to make in server-side (I've tested it with setblocks @ its position), but the client-side gets desynchronized. It gets fixed when the entity touches the floor.
/summon minecraft:creeper ~ ~ ~ {Motion:[0.0d,3.0d,-9.0d]}Run the command above with a wall and a hole in -Z direction (also works in all directions in the X-Z plane).
The bug doesn't affect the Y axis.
The entity still follows the path it's supposed to make in server-side (I've tested it with setblocks @ its position), but the client-side gets desynchronized. It gets fixed when the entity touches the floor.
/summon minecraft:creeper ~ ~ ~ {Motion:[0.0d,3.0d,-9.0d]}Run the command above with a wall and a hole in -Z direction (also works in all directions in the X-Z plane).
The bug
doesn'taffect the Y axis.The entity still follows the path it's supposed to make in server-side (I've tested it with setblocks @ its position), but the client-side gets desynchronized. It gets fixed when the entity touches the floor.
/summon minecraft:creeper ~ ~ ~ {Motion:[0.0d,3.0d,-9.0d]}Run the command above with a wall and a hole in -Z direction (also works in all directions in the X-Z plane).
The bug could be affecting the Y axis too, but it's more difficult to appreciate and to test.
The entity still follows the path it's supposed to make in server-side (I've tested it with setblocks @ its position), but the client-side gets desynchronized. It gets fixed when the entity touches the floor.
/summon minecraft:creeper ~ ~ ~ {Motion:[0.0d,3.0d,-9.0d]}Run the command above with a wall and a hole in -Z direction (also works in all directions in the X-Z plane).
The bug could be affecting the Y axis too, but it's more difficult to appreciate
and to test.The entity still follows the path it's supposed to make in server-side (I've tested it with setblocks @ its position), but the client-side gets desynchronized. It gets fixed when the entity touches the floor.
/summon minecraft:creeper ~ ~ ~ {Motion:[0.0d,3.0d,-9.0d]}Run the command above with a wall and a hole in -Z direction (also works in all directions in the X-Z plane).
The bug could be affecting the Y axis too, but it's more difficult to appreciate (second 14 of the shorter video, the mobs don't reach the roof even when they should have collided with it).
In version 19w11a I noticed that: if the summon command is executed in chat, the bug doesn't appears, but if the command is executed in a command block it still appears.
I'm not sure but maybe when Workflow changed from Global Mojang to Java, this bug's assigned priority got lost? Can't find it on Details.
Can't reproduce on 1.17.1 Pre-release 1