conduit-arena
conduit-arena is the top of the engine. It composes everything else into a complete hub-lobby-arena flow: a permanent hub world with pads for each registered game, a fixed pool of eight instance dimensions you acquire and release on demand, a staging-box lobby builder, a phase machine, a Game record + registry, the /conduit operator command, and ready-made in-world lobby/winner/world-settings screens. If your minigame fits the “walk into a portal, ready up, play, celebrate, reset” shape, this module owns most of the orchestration for you.
When to depend on this
Section titled “When to depend on this”- You’re building a multi-lobby minigame and want the hub-pad + instance pool wired automatically.
- You want a
Gameregistry, a phase machine, and lifecycle hooks instead of writing your own controller. - You need ready-made lobby info, winner, and world-settings screens.
- You want session policies that route reconnects to the right instance dimension.
Features
Section titled “Features”- Instance manager
- World template
- Hub manager
- Base lobby
- Lobby engine
- Lobby staging builder
- Built-in lobby screens
- Game record
- Game kind
- Game registry
- Phase machine
- Lobby + staging config
- Game-start lifecycle
/conduitcommand- Arena session policies
- GameStateSavedData
API surface
Section titled “API surface”me.zlex.conduit.instance — InstanceManager, GameInstance, WorldTemplate, HubManager, HubZoneme.zlex.conduit.lobby — BaseLobby, LobbyEngine, LobbyStagingBuilderme.zlex.conduit.lobby.screen.builtin — LobbyScreen, WinnerScreen, WorldSettingsScreenme.zlex.conduit.game — Game, GameRegistry, GameKind, GameHooks, Phase, PhaseFlow, PhaseMachine, LobbyConfig, StagingConfig, ConduitCommandme.zlex.conduit.lifecycle — GameStartme.zlex.conduit.player — ArenaSessionPoliciesme.zlex.conduit.state — GameStateSavedDataMaven coordinate: me.zlex:conduit-arena:<engine_version>. Depends on conduit-core, conduit-render, conduit-world, conduit-prefab, conduit-spectator, conduit-fx.