Regalia Slots API

v0.0.0-beta.15 - Third-party curio rendering

Bug-fix beta for Minecraft 1.21.1 / NeoForge 21.1.249 (Java 21).

Fixed

• Curios items from other mods rendered as nothing on the player. The bundled Curios compatibility layer bridged capabilities, slot types, predicates and attribute modifiers, but not the client renderer registry. Mods such as Relics register their curio models through top.theillusivec4.curios.api.client.CuriosRendererRegistry — a verbatim copy of the Curios class whose maps nothing ever read (load() was never called, and the render layer only queried Regalia's own registry). The item equipped and applied its effects, but was invisible on the body (for example Relics' amphibian_boot). Third-party curio renderers are now forwarded into Regalia's render layer.

Technical

• New com.skd.regaliaslotsapi.compat.curios.CuriosRendererAdapter adapts between the two identical-but-separate ICurioRenderer / SlotContext type hierarchies (top.theillusivec4.curios.api.* ↔ com.skd.regaliaslotsapi.api.*). Anonymous classes rather than lambdas, because ICurioRenderer#render is generic.
• CuriosRendererRegistry#register now forwards every registration to RegaliaSlotsApiRendererRegistry through the adapter. The existing RegaliaSlotsApiRendererRegistry.load() call in EntityRenderersEvent.AddLayers materialises them — no second listener is added, and there is no behaviour change for renderers registered directly into Regalia's registry.

Notes

Library / API mod (Curios API fork), no gameplay change. Incompatible with the real Curios mod (shared curios mod id); install one or the other. Verified: ./gradlew clean build is green. Rendering not yet verified in-game. LGPL-3.0-or-later; the full licence text ships in the jar.

JAR: regalia_slots_api-1.21.1-neoforge-21.1.249-0.0.0-beta.15.jar

Tag: 1.21.1-neoforge-0.0.0-beta.15