Fuzss

Here are some more reports I've gathered on this issue. Seems to be rather critical. https://github.com/Fuzss/enchantinginfuser/issues/132 https://github.com/Fuzss/forgeconfigapiport/issues/84 https://github.com/Fuzss/forgeconfigapiport/issues/83 https://github.com/thexaero/open-parties-and-claims/issues/695

Seems to be a Linux only issue. I've attempted a fix via [Mixin](https://github.com/SpongePowered/Mixin), still waiting on feedback though if it fully resolves the issue: https://github.com/Fuzss/forgeconfigapiport/commit/38c6c0ba87642140c35e827e57ad2bd625761c8a

I've gotten confirmation from one of the affected users that my fix mentioned above works for them. All I did was revert the calls to `IoUtils::tempConfigFileName` to `Path::getFileName + ".new.tmp"`....

Any update on this?

Additional notes: - The issue does not happen on Fabric in the exact same environment. - The issue does not happen using the official NeoForge template with the ModDevGradle plugin

This issue is currently being investigated by the NeoForge team (has been reported to them on Discord).

Not sure if this really needs a before variant. After all the point of the event is to sync custom data to the client which is not really possible if...

Not sure this really goes far enough. The system used by NeoForge has always been pretty ideal (although quite invasive): splitting gui rendering into all the different parts (health, hotbar,...

> The height problem is just reading the code to see the height where bars and components render right? Are you suggesting we provide z constants for different HUD elements?...

> Im not sure events like this are the best way to do this. An API that allows you to register LayeredDrawer.Layer's in the desired order may be better? This...