mojira.dev
MC-258430

Camels with large LastPoseTime values offset the player view model strangely

 

When riding a Camel your model's viewpoint is usually on the back of the Camel. However it looks like this is determined by the LAST_POSE_TICK value for the Camel. When setting this to something high, such as 20000L it'll cause your view to jump up or down (depends on if the Camel is sitting or not) in the Y axis. 

Reproduction steps:

1. Create a world with the 1.20 experimental feature flag enabled.
2. Spawn a Camel.
3. Merge new NBT data into the Camel using /data merge entity <uuid> {LastPoseTick:80000L}  
4. Ride the Camel and notice your view jump by about 500 blocks.

How high the value is determining how far your view offsets. 

Linked issues

Attachments

Comments 5

⚠️ Please do not mark Unreleased Versions as affected. You don't have access to them yet.

We have removed it and added the latest released version

Please edit the Affects Version/s field and select the specific Released Version you were using when you encountered the reported issue.

If you can't find it in the list, please make sure that:

  • You are in the correct project on the bug tracker.

  • You were playing the latest release version or the latest development version of the game.

This issue is being temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit

 

I added a new screenshot of it in base Vanilla. Forgot I was using Fabric on one of my installs. 

When in singleplayer, the player is actually moved and can die because of this.

This is not necessarily related to commands, it can also happen in regular gameplay by just waiting

 

Leaving a server up for ~24 hours with a world and then returning to it and spawning new camels will cause all of them to perform this behavior. Commands will just trigger it whenever since it's setting the problematic value. This would be more closely related to an entity issue than command. 

After re-testing it appears to only be caused by the command itself.

mja00

gnembon

Confirmed

Expansion A

Very Important

Mob behaviour

1.19.3

23w03a

Retrieved