Issue
Since updating to Hytale 0.5.1 and HyUI 0.9.7, I am seeing an issue where HyUI HUDs render only their first frame and then stop updating visually.
The HUD is created correctly, but countdown/progress text stays frozen on the client. The server-side logic still continues normally.
I tested this with two different mods that use HyUI HUDs, and both show the same behavior.
Custom pages still seem to render and interact correctly, so this looks specific to HUD rerenders rather than HyUI pages in general.
Possible cause
I am not 100% sure if this is only happening in my setup, but since the Hytale 0.5.1 update changed the custom HUD/custom page API, I think this may be coming from HyUI's HUD update path.
From what I found, the issue seems related to the new keyed HudManager behavior.
When HudManager.addCustomHud(...) is called with the same HUD instance/key that is already registered, it can return early. That means later rerenders may not send updated CustomHud commands to the client.
Possible fix
I opened a small PR with a possible fix here:
The PR changes existing HUD rerenders to rebuild the commands and send them through CustomUIHud.update(...) directly, while still keeping the native Hytale 0.5.1 HudManager approach for registration.
After applying that change locally, HUD updates started working again in my test cases.
Issue
Since updating to Hytale
0.5.1and HyUI0.9.7, I am seeing an issue where HyUI HUDs render only their first frame and then stop updating visually.The HUD is created correctly, but countdown/progress text stays frozen on the client. The server-side logic still continues normally.
I tested this with two different mods that use HyUI HUDs, and both show the same behavior.
Custom pages still seem to render and interact correctly, so this looks specific to HUD rerenders rather than HyUI pages in general.
Possible cause
I am not 100% sure if this is only happening in my setup, but since the Hytale
0.5.1update changed the custom HUD/custom page API, I think this may be coming from HyUI's HUD update path.From what I found, the issue seems related to the new keyed
HudManagerbehavior.When
HudManager.addCustomHud(...)is called with the same HUD instance/key that is already registered, it can return early. That means later rerenders may not send updatedCustomHudcommands to the client.Possible fix
I opened a small PR with a possible fix here:
The PR changes existing HUD rerenders to rebuild the commands and send them through
CustomUIHud.update(...)directly, while still keeping the native Hytale0.5.1HudManagerapproach for registration.After applying that change locally, HUD updates started working again in my test cases.