The Bug:
Camels with large "LastPoseTick" NBT values still behave strangely and cause a variety of issues.
MC-258430 fixed a lot of the severe problems when it comes to camels with large "LastPoseTick" NBT values, but some issues still remain.
The issues are as follows:
The player model is offset when riding the camel.
The camel doesn't move when the player steers it.
The camel will never naturally walk around.
The camel cannot be pushed.
Steps to Reproduce:
Summon a camel with a large "LastPoseTick" NBT value by using the command provided below.
/summon minecraft:camel ~ ~ ~ {LastPoseTick:500000L,SaddleItem:{id:"minecraft:saddle",Count:1b}}Mount the camel and look at the positioning of your player model.
Take note as to whether or not camels with large "LastPoseTick" NBT values still behave strangely and cause a variety of issues.
Observed Behavior:
Camels behave strangely.
Expected Behavior:
Camels would not behave strangely.
When setting camel LastPoseTick to a very large number (i.e. future) there are certain bits of camel logic that take effect:
Camel cannot be pushed: camels can be pushed only if certain time has passed from the last pose change (positive time), since we are now living in negative time with this camel, it still waits to be pushable. That's WAI
Camel will never naturally walk around: same logic as above, camel walking is inly enables when after changes its pose so WAI
Camel cannot be steered: same logic: WAI
I would add one extra bit:
Camels hitboxes are reversed: Standing camel in negative pose time sits (first stage of standing is sitting) and vice versa, Sitting camel starts is pose from standing position (first stage of sitting is standing), and that's WAI
What is not WAI is incorrect player position on the camel. Player should always be position where the saddle is visually located. This will be fixed for this ticket.