[1.8->1.7] generic.maxHealth attribute changes applied via item results in being stuck on respawn screen
calcastor opened this issue ยท 4 comments
/viaversion dump
Output
https://dump.viaversion.com/e6f35bd590d62b51aa3476b3a04363e7d9e18534fa8b435ff41819beed40a05a
Console Error
None
Bug Description
Applying a generic.maxHealth attribute via an item results in becoming stuck on the respawn screen. This is mitigated by the absorption effect.
The usage of the attribute in this situation is to reduce the player's health cap.
Steps to Reproduce
- Be on 1.7.10 and switch to an item with a generic.maxHealth attribute on a 1.8 server (specifically one that reduces health)
- Observer stuck respawn screen (respawn button does nothing)
Expected Behavior
Respawn screen should not appear
Additional Server Info
1.7.10 player on 1.8.8 Paper-based server
Checklist
- Via plugins are only running on EITHER the backend servers (e.g. Paper) OR the proxy (e.g. Velocity), 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.
- I have looked at https://www.spigotmc.org/resources/viarewind-legacy-support.52924/ and it does not offer a fix for my problem
I believe this happens in the 1.16->1.15.2 protocol, meaning 1.16+ clients shouldn't have the issue while 1.15.2 and older do, maybe you can confirm/check this?