About the bot
DBLX keeps chat moving.
The DontBlameLexi bot is the stream-side control layer for chat commands, quick replies, game-night helpers, overlays, Discord relays, and moderator dashboards across the DBLX crew.
Twitch Commands
Apex Stats
Fallout 76
Discord Relay
OBS Overlays
Mod Tools
Built for the DontBlameLexi and TehKluma side of the stream stack, with enough flexibility to support channel-specific commands.
What it does
One bot, a lot of tiny saves.
Most of the useful work is quiet: answering chat, keeping links consistent, helping mods, and making game-night commands feel instant.
Fast answers without stopping the show
Common chat prompts, links, shoutouts, raid calls, socials, timers, and stream info stay ready so Lexi and the mods can keep the stream moving.
!commands
!discord
!socials
!so
Game-aware utility commands
The bot can carry seasonal helpers like Fallout 76 Minerva shop info with !mshop, plus game-specific notes when the channel needs them.
!mshop
!game
!rank
!queue
Stats with provider fallback
Apex lookups are routed through the DBLX stat bridge so provider issues can be isolated without breaking the whole chat flow.
!stats
!apex
!ranked
!legend
Built for mods and trusted helpers
Private dashboards, route launchers, and access checks help the team manage the stream stack from one place.
Portal
Dashboard
Discord
Overlays
How it fits
Public chat, private controls.
Viewers get simple commands. Mods and operators get protected dashboards. The stream gets fewer interruptions.
Commands should feel boring in the best way.
A viewer asks for a link, a stat, a shop check, or a stream note. The bot answers cleanly, uses the right channel context, and leaves the humans free to keep talking.
The heavy buttons stay behind Twitch auth.
Route launchers, dashboard access, overlay tools, and provider checks live in the DBLX control layer instead of being exposed as public page clutter.
When providers act up, the bot should make it obvious.
Stats, game data, and external APIs can disagree. DBLX keeps those checks separated so the team can tell whether the issue is the stream code, an upstream provider, or stale third-party data.