Skip to content
Conduit

What is Conduit?

Conduit is a server-side Fabric framework for building Minecraft minigames. It packages the patterns we re-implemented across half a dozen modes — instancing, lobby flow, world-anchored UI, safe teleports, disconnect/reconnect, spectator state — into eight small modules you can pick from.

It targets Minecraft 26.1.2, Java 25, Fabric Loader 0.19.2+, and Fabric API 0.149.1+26.1.2.

What Conduit gives you

Section titled “What Conduit gives you”
  • Lifecycle out of the box. A Game abstract class with explicit phases (STAGING → RUNNING → CELEBRATION → RESET), a PhaseMachine to drive transitions, and hooks for death/quit/respawn that you override.
  • Hub + lobby + instance pool. A permanent hub world, a lobby that boots your game from a staging area, and a pool of eight instance dimensions claimed and released on demand.
  • In-world UI. Interactive screens, floating labels, and 3D block displays painted in world space. The rich rendering ships in a small client companion mod; vanilla clients still connect and play, falling back to chat-driven prompts and entity-based displays.
  • Safe cross-dimension teleports. Teleports defer one tick and ticket-load the destination chunk so players never land in unloaded terrain or trigger spectator desync crashes.
  • Inventory stash and player session manager. Save inventories before meetings or shops; snapshot full player state on disconnect so they pop back into the right phase on reconnect.
  • Authored scenes. Reusable JSON-defined world chunks (blocks, screens, labels, zones) you spawn and despawn at runtime with variable substitution.
  • Operator command suite. /conduit for inspecting instances, forcing phase changes, ending games.

What Conduit doesn’t do

Section titled “What Conduit doesn’t do”
  • It’s not a game. Conduit is the framework; your minigame is a separate Fabric mod built on top.
  • It isn’t fully client-free. Everything gameplay-related is server-authoritative, but in-world UI is rendered by a small client companion mod the engine ships alongside the server jars. Vanilla clients still connect; they just see chat / entity fallbacks instead of rich panels.
  • It’s not a mod loader, plugin system, or scripting runtime. It’s a Java library you depend on from your Fabric mod.

When to use it

Section titled “When to use it”

Use Conduit if you’re building any server-side Minecraft minigame for Fabric — especially one with rounds, lobbies, multiple concurrent games, or non-trivial in-world UI. The patterns it encodes are the ones every minigame eventually re-invents.

If your mod is a single-purpose tweak (a new mob, a recipe pack, an event listener), Conduit is overkill — drop down to plain Fabric API.

Where to go next

Section titled “Where to go next”
  • Quickstart — install Conduit and ship a minimal game in 10 minutes.
  • Installation — Gradle config + version pinning.
  • Architecture — the dependency stack and what each module owns.