DBLBot 2077 // Operator OS v2.1.0
Broadcast like an operator.
One Control Surface. Every route, command, relay, and live system under your control.
Every route. Every command. One operator.
Installed Systems
Deploy a module.
Each module is a live DBLBot subsystem with its own route, scope, and operational state.
Main Chat Router
Moderation, command routing, timers, telemetry, and the primary TehKluma Control Surface.
Apex Command Surface
The xThyQueen operations module for queue nights, rapid responses, and scene-specific control.
Apex stats via the TehKluma API proxy with Tracker.gg, Wraith, and Mozambique Here fallback.
Community Relay
Discord relay, utility hooks, and community-side DBLBot systems on a dedicated Control Surface.
KimberBarks Command Matrix
Remington4122 chat commands, rotating responses, and KimberBarks automation controls.
Protected Control Layer
Public telemetry stays visible while private systems remain behind Twitch authentication.
Operator Console
One Control Surface. Every stream.
Deploy routes, arm commands, inspect telemetry, and move between broadcast systems without breaking flow.
System Architecture
Built for operator velocity.
Fast deployments, protected systems, visible telemetry, and clean handoffs when another operator takes control.
Operator Authentication
Twitch-linked identity gates every private Control Surface without access codes.
Deployment Router
Every live module is one deliberate jump from the Operator Console.
Community Relay
Discord operations stay linked to the same DBLBot command network.
Protected Control Layer
Authorized operators deploy private systems through a Twitch-linked session.
Operator Handoffs
Clear module states keep control transfers fast when another operator takes the chair.
Network Telemetry
Root, Control Surface, and Discord routes stay visible as one connected system.