Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Armorstand rotation updates don't pass through in 1.8->1.9 #3802

Open
4 tasks done
FlorianMichael opened this issue Apr 24, 2024 · 1 comment
Open
4 tasks done

Armorstand rotation updates don't pass through in 1.8->1.9 #3802

FlorianMichael opened this issue Apr 24, 2024 · 1 comment
Assignees
Labels
Bug Confirmed bug Plausible

Comments

@FlorianMichael
Copy link
Member

/viaversion dump Output

https://dump.viaversion.com/2f0eeff2c6e6203cc5290a1d22593d5f48119898d0ed063200106cfed5c484fa

Console Error

No response

Bug Description

If you spawn an armor stand using packets and only change its yaw (to make the head turn), players between versions 1.9 and 1.9.4 don't see the armor stand rotating. It only rotates if X Y Z changes.

Steps to Reproduce

Do what the bug description says

Expected Behavior

Armor stand should rotate like it does for 1.8 players, probably something in our entity tracker?

Additional Server Info

No response

Checklist

  • Via plugins are only running on EITHER the backend servers (e.g. Paper) OR the proxy (e.g. BungeeCord), not on both.
  • I have included a ViaVersion dump.
  • If applicable, I have included a paste (not a screenshot) of the error.
  • I have tried the latest build(s) from https://ci.viaversion.com/ and the issue still persists.
@Barvalg
Copy link
Member

Barvalg commented Apr 24, 2024

Platform: git--PaperSpigot--445%20%28MC%3A%201.8.8%29
ViaVersion (4.9.3): 8 commits behind master

Please update all Via* plugins from https://ci.viaversion.com/. In case the issue still persists send the new dump and the issue will be reopened

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Confirmed bug Plausible
Projects
None yet
Development

No branches or pull requests

2 participants