-
Notifications
You must be signed in to change notification settings - Fork 12
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
fix bossbar #80
base: main
Are you sure you want to change the base?
fix bossbar #80
Conversation
Doesn't build.
|
could you try commenting out the 1.12 project in settings.gradle.kts and building just 1.8.9 |
Yeah, that works. (Edit: the build) |
are we deadass?? |
oh shit you talking about building it my fault |
current state: proposed solution "works". no longer a glitched bossbar but instead the bossbar shows as being at max hp for a while instead which isn't a great solution. issue stems from health being greater than maxhealth (dont know why). bossstatus and the bossbar rendering are decoupled and cant store info to normalize and I don't know how I would modify maxhealth to be the max between itself and health (client-side). (tldr this fix "works" but causes other issues, don't know how to do a proper fix) would probably have to do some duck interface nonsense to get the entity instance |
Description
https://discord.com/channels/822066990423605249/1297626978165461175/1297626978165461175
Unable to replicate the issue, and not about to wait for a skyblock event or whatever. this is the only thing i can think of that would cause this. cant replicate it even with insane aspect ratios, and you cant set boss health above their hardcoded values in vanilla 1.8.9. not tested at all, dont know if this fixes anything.
Related Issue(s)
Fixes # https://discord.com/channels/822066990423605249/1297626978165461175/1297626978165461175
How to test
Release Notes
Documentation