StreamBridge 0.1.0

First release. A Minecraft server can now drive OBS.

What it does

• Eight server-side event types — deaths (with cause, killer and position), boss kills, advancements, low health with hysteresis, dimension changes, join and leave, chat messages, server start and stop.
• A rule engine in config/streambridge.json: match an event, add conditions (equality, negation, regex, numeric comparison), set a cooldown, list what to do.
• Eighteen action types over obs-websocket v5 — program and preview scene, studio transition, source toggle by name, filter toggle, replay-buffer save, recording and stream control, text-source updates, hotkeys by name, and raw for anything else the protocol accepts.
• Placeholders from the event in any string parameter: {player}, {cause}, {killer}, {entity}, and regex captures such as {scene}.
• Chat commands — an operator can type !scene Just Chatting and OBS switches, from a single rule that covers every scene.
• Delayed actions — cut away now, cut back in six seconds, from one rule.
• An in-game dashboard — /streambridge dashboard or a right-click on an unbound Scene Remote. Lists the scenes OBS reports (click to switch, bind to write one onto a remote) and your rules with trigger counts, a test button and an on/off toggle. Reload, clip and recording controls along the bottom.
• The Scene Remote — one item per scene, right-click to switch, the bound scene shows in the item name.
• /streambridge status, /streambridge reload, /streambridge test <rule> and /streambridge dashboard.

Built for a live server

• Nothing runs on the server thread; the OBS socket has its own daemon thread.
• Requests are dropped rather than queued while OBS is disconnected.
• A global token bucket caps outgoing requests at 5 per second, burst 10.
• Per-rule cooldowns survive a config reload.
• An invalid config is reported in /streambridge status instead of crashing anything.
• A rejected OBS password stops the reconnect loop rather than hammering OBS.

Known limitations

• One-way for now: the game drives OBS, not the other way round. Twitch and YouTube chat as an input is the next feature.
• NeoForge only. A Fabric build is planned.
• The dashboard and the Scene Remote compile against 1.21.11 but have not been through a real session yet.
• The protocol and rule layers have 51 automated tests behind them, including a full obs-websocket handshake against a stand-in server. The game-side event wiring is new and has not been through months of real use — bug reports welcome.