Skip to content
Conduit

conduit-render

conduit-render is the in-world rendering module. It draws interactive panels, floating billboard labels, and animated 3D block/item displays at exact world positions. The server holds authority over every renderable — it sends typed payloads describing what to draw. The actual drawing happens in a small client companion mod that registers receivers for those payloads; vanilla clients silently skip them and rely on chat / entity fallbacks the consuming mod provides. There are no mixins on the server side.

When to depend on this

Section titled “When to depend on this”
  • You want to put a clickable settings panel on a wall in front of a lobby.
  • You need a floating “WALK IN TO PLAY” hologram above a hub pad.
  • You want a spinning trophy block hovering over the winner.
  • You’re building any UI that has to live in the world rather than on the player’s HUD.

Features

Section titled “Features”

API surface

Section titled “API surface”
me.zlex.conduit.screen                  — ServerScreenManager, ScreenContent,
                                          ScreenDef, ScreenElement (sealed),
                                          TextElement, ButtonElement, ImageElement,
                                          RectElement, TextInputElement
me.zlex.conduit.screen.ui               — Region, Theme, Widgets
me.zlex.conduit.screen.ui.layout        — ScreenLayout, ScreenWidget, ScreenLayoutCompiler
me.zlex.conduit.screen.placement        — ScreenPlacement, Placements
me.zlex.conduit.label                   — ServerLabelManager, WorldLabel, LabelDef
me.zlex.conduit.display                 — WorldBlockDisplay, BlockDisplaySpec
me.zlex.conduit.{screen,label,display}.packet — engine payload types (wire format)

Auto-id ranges: screens start at 1000, labels at 5000, block displays at 9000. Stable caller-managed ids should sit outside these.

Maven coordinate: me.zlex:conduit-render:<engine_version>. Depends on conduit-core.