Skip to content

Conduit log

ConduitLog exposes one SLF4J logger per engine subsystem. Using per-subsystem loggers (rather than a single mod-wide one) means production logs filter cleanly by area — grep InstanceManager, grep ScreenManager, grep PlayerSession — and log appenders can route them independently.

The class is named ConduitLog in the source (inventory listed it as EngineLog; the engine rebrand renamed it).

When to use it

You’re contributing to the engine and want to log against the matching subsystem name.
You’re a consumer mod that wants to add to one of the existing engine streams for unified ops tooling.

API

package me.zlex.conduit;

public final class ConduitLog {
    public static final Logger INSTANCE_MANAGER;   // conduit.InstanceManager
    public static final Logger HUB_MANAGER;        // conduit.HubManager
    public static final Logger SCENE_STORE;        // conduit.SceneStore
    public static final Logger LOBBY;              // conduit.Lobby
    public static final Logger SCREEN_MANAGER;     // conduit.ScreenManager
    public static final Logger LABEL_MANAGER;      // conduit.LabelManager
    public static final Logger BLOCK_DISPLAY;      // conduit.BlockDisplay
    public static final Logger SPECTATOR;          // conduit.Spectator
    public static final Logger TELEPORT;           // conduit.Teleport
    public static final Logger CONFIG;             // conduit.Config
    public static final Logger PERMISSIONS;        // conduit.Permissions
    public static final Logger TICK_BUDGET;        // conduit.TickBudget
    public static final Logger PLAYER;             // conduit.PlayerSession
}

Example

import me.zlex.conduit.ConduitLog;

public final class HubExtensions {

    public static void rebuildPad(String zoneId) {
        ConduitLog.HUB_MANAGER.info("rebuilding hub pad {}", zoneId);
        try {
            // ...
        } catch (Exception e) {
            ConduitLog.HUB_MANAGER.error("rebuild failed for {}: {}", zoneId, e.toString());
        }
    }
}

Notes

Your own mod should still use its own SLF4J logger — share ConduitLog only when you’re extending an engine subsystem.
Logger names are stable strings; ops can write log4j filters against them.
Adding a new subsystem logger is a one-line addition here, done as new subsystems land.