SKD Menu

v0.0.0-beta.4 - Custom loading screen removed

On a full modpack, the custom loading screen rendered black — only its progress bar showed — whenever a server applied its resource pack (and again on disconnect). This build drops the custom loading screen entirely and lets NeoForge's vanilla one handle those reloads. The title-screen customization is untouched.

Removed

• Custom loading-screen overlay (LoadingOverlayMixin). It replaced the whole vanilla loading overlay, but during an in-game resource reload its textured draws (background, banner, logo, progress-bar frame) rendered nothing — only GuiGraphics.fill primitives showed, leaving a black screen with a bare progress bar. Diagnostics confirmed the texture resolved to a valid DynamicTexture with a clean GL state; the blits were still swallowed on the overlay code path (the same blit works fine on the title screen), pointing at a GuiGraphics batching interaction with another client mod. Instead of fighting that, the overlay is gone: server-pack reloads now use NeoForge's own loading screen.
• Deleted LoadingConfig (the config/skd_menu/loading.json model) and EarlyDisplayInstaller (already a no-op on NeoForge 21.1.x), plus the bundled earlydisplay/ theme resources and textures/gui/bar_track.png. TextureResolver and SkdMenuClient are back to their beta.3 state.

Unchanged

• The title-screen customization — background (image / zoom / colour / panorama / animated), two corner logos, title image, button repositioning and hiding, custom buttons, image overlays, and third-party button control — works exactly as before.

Notes

Client-only menu mod, no gameplay content. Verified in-game: title screen keeps its custom look; server-pack join / disconnect now shows the vanilla NeoForge loading screen. ./gradlew clean build OK. The resource-reload duration itself is unchanged — that is the modpack (and any shader pack) rebuilding, not this mod.

JAR: skd_menu-1.21.1-neoforge-21.1.249-0.0.0-beta.4.jar

Tag: 1.21.1-neoforge-0.0.0-beta.4