StaffChat

[1.0.1] — 2026-04-16

Fixed

• Staff messages were leaking through DCIntegration (and any other Discord-bridge mod that hooks ServerMessageEvents.ALLOW_CHAT_MESSAGE). Reported by the SYLX server team running DCIntegration. Root cause: Fabric's ALLOW_*_MESSAGE invoker iterates listeners in phase order and short-circuits on the first false, but listener order within a phase is undefined — so when DCIntegration registered in the DEFAULT phase the same as us, its forward-to-Discord listener sometimes ran first, posted the message, and only then did our return false cancel the in-game broadcast. The Discord channel saw the staff message; the in-game global chat didn't.

  Fixed by registering our listener in a dedicated staffchat:veto phase declared to run before Event.DEFAULT_PHASE. Other mods that register implicitly (the common case for chat-bridge mods including DCIntegration) land in DEFAULT and therefore run after us — meaning our return false cancels the message before they ever see it. Verified against the bytecode of fabric-message-api-v1 0.116.10: the invoker really does short-circuit on the first false return.

  If a Discord-bridge mod also registers in an earlier custom phase, this fix won't fully isolate it (no Fabric API can resolve that conflict generically). For that case, configure the bridge to ignore staff chat or talk to the bridge author. The vast majority of Fabric chat-bridge mods, including DCIntegration, use the default phase.

Notes for server operators

If you're upgrading from 1.0.0 specifically because of the leak, drop the new jar in mods/ and restart the server. No config changes needed — the fix is entirely on the listener-registration side.