Installation
Conduit ships eight Maven artifacts. A consuming mod depends on the modules it actually uses.
Versions
Section titled “Versions”| Component | Version |
|---|---|
| Minecraft | 26.1.2 |
| Java | 25 |
| Fabric Loader | 0.19.2 |
| Fabric API | 0.149.1+26.1.2 |
| Loom | 1.16-SNAPSHOT |
| Conduit | 0.8.0+mc26.1.2 |
The version suffix (+mc26.1.2) is part of the coordinate. Pin it explicitly — 0.4.0 alone will not resolve.
From mavenLocal (development)
Section titled “From mavenLocal (development)”cd conduit && ./gradlew publishToMavenLocalArtifacts land at ~/.m2/repository/me/zlex/conduit-{core,render,…}/0.8.0+mc26.1.2/.
In your mod’s build.gradle:
repositories { mavenLocal()}
dependencies { implementation "me.zlex:conduit-core:0.8.0+mc26.1.2" implementation "me.zlex:conduit-render:0.8.0+mc26.1.2" // …whichever modules you need}From GitHub Packages
Section titled “From GitHub Packages”Conduit’s CI publishes every module to GitHub Packages on every push to main and mc-26.1. To consume:
repositories { maven { name = 'ConduitGitHubPackages' url = uri('https://maven.pkg.github.com/zlexo/conduit') credentials { username = System.getenv('GITHUB_ACTOR') password = System.getenv('GITHUB_TOKEN') } }}The token must have read:packages scope. GitHub Packages requires authentication for every download — there’s no anonymous read.
Modules
Section titled “Modules”| Artifact | When to depend |
|---|---|
conduit-core | Always. Every other module depends on it. |
conduit-render | If you draw screens, labels, or 3D displays in world space. |
conduit-world | If you need per-instance world settings or void terrain. |
conduit-spectator | If you promote/demote players to spectator mid-round. |
conduit-fx | For countdowns, bossbars, particle/sound effects. |
conduit-prefab | If you author scenes as JSON and spawn them at runtime. |
conduit-arena | For hub-lobby-instance games with multiple concurrent rounds. |
You can mix and match. A simple command-driven mod often needs only conduit-core + conduit-render. A full hub-lobby game with concurrent instances uses everything.
Jar-in-Jar bundling
Section titled “Jar-in-Jar bundling”To ship your mod as a single .jar that contains the Conduit modules it depends on, use Loom’s include:
dependencies { implementation "me.zlex:conduit-core:0.8.0+mc26.1.2" include "me.zlex:conduit-core:0.8.0+mc26.1.2"}include pulls the dependency into your mod jar as a nested Fabric Jar-in-Jar. Players only need your one jar; the Conduit modules unpack on mod load.