Repository navigation
Releases
darkbot v0.7.4
What's new
Timers: several messages per timer, random without repeats or in order
A timer can now hold up to 20 messages (one per line in the editor) and
posts one of them each time it fires, so socials no longer repeat the
same line every few minutes.
- Random (default) deals the messages like a shuffled deck of cards:
every message comes exactly once per round, and a new round never
starts with the message that ended the previous one, so nothing is
posted twice in a row. - Top to bottom posts them in the written order and starts over.
- The order selector appears only with two or more messages; the timer
list shows e.g. "every 20 min, 3 messages, random". - Settings from v0.7.3 and older keep working: the single "message" is
moved into "messages" when the config loads (ChatTimer.Lines covers
unnormalised values). Clone now deep-copies each timer's messages. - The deck lives in memory only; editing the messages deals a new one
and a restart reshuffles. - Validation per message (Twitch's 500 characters, with the line number
in the error), empty lines dropped, at most 20 messages.
Download
- Windows 10/11:
darkbot-windows-amd64.exe - macOS, Apple Silicon:
darkbot-macos-arm64.app.zip - macOS, Intel:
darkbot-macos-amd64.app.zip - Linux:
darkbot-linux-amd64
Already installed? darkbot updates itself on the next start.
Full changelog: v0.7.3...v0.7.4
darkbot v0.7.3
What's new
Statistics: 7, 30, 60 and 90 days with a separate history file
The statistics view now switches between this stream and the last 7,
30, 60 and 90 days. Up to a week the chart shows every hour; longer
ranges show one bar per day (hover for messages and chatters).
Storage stays small and the disk quiet:
- Finished days move to stats-history.json, which is written only when
a day ends. stats.json keeps today and the session, so a busy chat
still only rewrites a few KB every few seconds. Files of v0.7.2 (seven
days in stats.json) are moved over automatically. - Days older than a week keep only their 200 most active people. The
top lists stay right; "chatters" over a long range is shown as "at
least". The day's own chatter count is kept from before the cut. - Logins are only stored when they differ from the display name.
Measured with different chatters every day for 90 days: 50 a day 0.9 MB
memory and a 229 KB history file, 300 a day 3.6 MB / 910 KB, 1,000 a
day (the cap) 4.7 MB / 1.1 MB. Building the 90-day view takes ~10 ms.
Download
- Windows 10/11:
darkbot-windows-amd64.exe - macOS, Apple Silicon:
darkbot-macos-arm64.app.zip - macOS, Intel:
darkbot-macos-amd64.app.zip - Linux:
darkbot-linux-amd64
Already installed? darkbot updates itself on the next start.
Full changelog: v0.7.2...v0.7.3
darkbot v0.7.2
What's new
Statistics view: top chatters, subs, Bits, raiders and 7-day chat activity
A new "Statistics" tab next to the dashboard shows, for this stream or
the last 7 days: messages, chatters, subs and Bits, and the top 5
chatters, subs (gifted subs count for the gifter), Bits and raiders.
Below, a chart of chat messages per hour over the last 7 days with
messages and chatters per day (hover shows the hour).
Bots never count. Twitch has no bot flag in channel.chat.message (the
Chat Bot Badge only exists for app-token bots), so darkbot goes by name:
a built-in list (Nightbot, StreamElements, Streamlabs, Moobot, Fossabot
and more) plus your own list in the tab. Your own messages don't count
either, since darkbot replies as you.
Storage stays small: people are kept per session and per local day
(keyed by Twitch user ID), days older than 7 are dropped, and each day
and session keeps at most 1,000 people (the least active drop out
first; the chatter count is then shown as "at least"). stats.json is
now written compact.
Download
- Windows 10/11:
darkbot-windows-amd64.exe - macOS, Apple Silicon:
darkbot-macos-arm64.app.zip - macOS, Intel:
darkbot-macos-amd64.app.zip - Linux:
darkbot-linux-amd64
Already installed? darkbot updates itself on the next start.
Full changelog: v0.7.1...v0.7.2
darkbot v0.7.1
What's new
Status colors: green = on, red = off, amber = problem
On/off lights (command, timer, event and clip rows, sound pads), ticked
checkboxes, radio choices and OBS track picks were amber, the same color
the dashboard uses for warnings. Now on is green and off is red, as
everyone reads them; amber is left for problems and as the accent of
buttons, tabs and focus. In the activity feed, played is green, not
played amber, errors red, and channel events green.
Bits: channel.bits.use instead of channel.cheer, new event Power-ups
channel.cheer only reports cheers. channel.bits.use v1 reports every
Bits use: cheers, Twitch's Power-ups (giant emote, message effect,
celebration) and the channel's own Power-ups. darkbot now subscribes to
it instead (both would count cheers twice).
- Cheers stay the "Bits" event with their settings.
- New "Power-ups" event with sound, chat, alert and minimum amount;
{powerup} names it (custom ones by their title). - Power-up Bits count into the dashboard. Same scope bits:read, so no
reconnect is needed. - channel.bits.use has no is_anonymous field.
Twitch API audit against the current docs: fixes
Checked every Twitch API darkbot uses against dev.twitch.tv and its
changelog. Nothing is deprecated and all versions are current. Fixed:
- channel.ad_break.begin: the reference's example sends duration_seconds
as a string; accept both forms instead of dropping the event. - stream.online: only type "live" counts (not rerun, premiere, playlist,
watch party), matching Get Streams type=live. - Redemptions revoked as version_removed or refused as deprecated no
longer cause an endless reconnect loop; darkbot logs "update darkbot"
and the rest keeps running. - Corrected the subscription cost comment (cost 0 when the broadcaster
authorized the app).
Shared Chat: darkbot writes nothing in chat during a session
With a user access token, Send Chat Message reaches every channel of a
Shared Chat session and Twitch says this cannot be changed. darkbot has
no app token (a desktop app can't keep a client secret), so it stays
silent in chat while the channel is in a session. Sounds, alerts and
clips keep working, and the log names every message that wasn't sent.
Detected with channel.shared_chat.begin/end v1 (no authorization needed)
and Get Shared Chat Session at start. The Chat tab explains it.
"Events" tab is now "Alerts", with category sub-tabs
Events are grouped into Support, Hype & goals, Polls & predictions and
Channel. A category without events has no tab yet. The number on a tab
counts how many alerts are switched on there. Categories are defined in
Go (twitch.Category) and a test makes sure every kind has one.
New alerts: title/category changes, Twitch's channel point rewards
- channel.update v2: alert when the stream title or category changes.
Language-only or label-only updates are dropped by comparing with the
channel read at connect. Placeholders: {title}, {category}. - Automatic channel point rewards v2 (highlighted message, emote
unlocks, ...): alert with {reward} and the price as {amount}. - Hype train status is read at connect, so a train already running
reports its next level-up instead of using it as the baseline.
None of these needs a new scope.
!marker and !snooze, new Twitch permissions
- Twitch login asks for the permissions of everything in this round at
once: channel:manage:ads, moderator:manage:shoutouts,
channel:manage:broadcast, channel:read:goals, channel:read:polls,
channel:read:predictions. - Helix: Get Ad Schedule, Snooze Next Ad, Send a Shoutout, Create Stream
Marker, Get Creator Goals (its "follower" type is normalized to the
events' "follow"). - !marker sets a stream marker (text after it becomes the description)
and answers with the position. !snooze pushes the next ad back 5
minutes. Both are off by default, moderators only unless opened up. - The Chat tab's built-in commands block lists !clips, !marker and
!snooze with one editor; their names can't clash.
Raid shoutouts and an ad warning
- Raid alert option: give the raider Twitch's shoutout automatically.
- New "Ad coming up" alert. Twitch has no event for it, so while live
darkbot reads Get Ad Schedule every 15 s and warns a set time before
the ad (default 60 s). It warns once per ad, and again after a snooze
moves the ad.
Goals, polls and predictions: alerts and OBS overlays
- EventSub channel.goal., channel.poll. and channel.prediction.* v1.
- New alerts: goal started/reached, poll started/ended, prediction
started/locked/resolved, with {title}, {winner} and {amount}. - Two OBS overlays, switched on in their Alerts tab: goal progress bars
(top left) and the running poll or prediction (top right) with its
result. Goals set before darkbot started are read with Get Creator
Goals. "Test" shows a sample on the overlay. - The OBS browser-source code is now shared by all overlays; Now Playing
is unchanged.
README: Alerts tab, new alerts and overlays, !marker/!snooze, Shared Chat
Download
- Windows 10/11:
darkbot-windows-amd64.exe - macOS, Apple Silicon:
darkbot-macos-arm64.app.zip - macOS, Intel:
darkbot-macos-amd64.app.zip - Linux:
darkbot-linux-amd64
Already installed? darkbot updates itself on the next start.
Full changelog: v0.7.0...v0.7.1
darkbot v0.7.0
What's new
!clips: viewers make a clip of the last 60 seconds from chat
New built-in chat command (Chat tab, off until turned on). A viewer types
!clips, darkbot creates a 60-second clip with Helix Create Clip, asks Get
Clips every 3 s until Twitch lists it (Twitch documents: not listed after
60 s = failed) and replies with the link. The clip also lands in the
activity feed with a link that opens in the browser.
- Settings: command name (default "clips"; can't clash with song commands
or the streamer's own ! commands, both ways), who may use it, cooldown
for everyone (default 60 s, broadcaster and mods skip it), optional
title with {user} (empty keeps the stream title). One clip at a time. - Chat explains Twitch's documented failures: not live (404), category
not clippable or title refused by AutoMod (400, retried once without
the title), clips off or limited (403); other errors give a short
"try again", details in the log. - The Twitch login now requests clips:edit, so existing logins are asked
to reconnect once; the Chat tab says why clips can't run yet. - Helix errors carry their HTTP status (APIError) so callers can tell
cases apart. - Tests: Create/Get Clip on a fake Twitch, the handler's flows and
errors, settings validation, config defaults for old configs.
Download
- Windows 10/11:
darkbot-windows-amd64.exe - macOS, Apple Silicon:
darkbot-macos-arm64.app.zip - macOS, Intel:
darkbot-macos-amd64.app.zip - Linux:
darkbot-linux-amd64
Already installed? darkbot updates itself on the next start.
Full changelog: v0.6.0...v0.7.0
darkbot v0.6.0
What's new
Now Playing overlay for OBS: six designs and their own tab
The song that Spotify or YouTube Music is playing can now be shown in the
stream. The new "Now Playing" tab shows:
- what is playing, on which service
- the switches: show in OBS, cover, progress bar, who requested it, hide
while paused - all six designs as live previews with the current song (a sample song
when nothing plays). One click picks a design.
The designs are Console, Glass, Lower third, Vinyl, Minimal and Compact.
They live in one page, frontend/dist/overlay/nowplaying.html. OBS shows
that same page, so a preview looks exactly like the stream.
OBS: darkbot adds a browser source, "[darkbot] now playing", to its scene
in the bottom-left corner. The source shows the page, which darkbot
writes into its settings folder with the font next to it. darkbot sends
the song over the existing OBS connection with obs-browser's emit_event
vendor request (checked against the obs-browser README and source), so
darkbot still opens no port. The page is rewritten, and reloaded in OBS,
only when an update changed it. The source is set up again after OBS
reconnects and removed along with darkbot's other OBS parts. An OBS
without browser sources gets a clear message.
Data: Spotify's Get Currently Playing Track (darkbot already has the
scope; ads are skipped) and Pear Desktop's /api/v1/song. darkbot asks
every 3 s, and only while the overlay is on or the tab is open; the page
moves the progress bar on by itself in between. A playing service wins
over a paused one. "Requested by" comes from !sr.
Security:
- song titles and artists go into the page only as textContent; tested
with HTML in a title - cover URLs must be http(s)
- the preview's cover is downloaded by darkbot (https only, max 2 MB) and
served from memory, so darkbot's window still loads nothing from the
internet
Not yet tried in a real OBS: the page was tested with the same
CustomEvent that obs-browser dispatches.
Test: wait for idle before the simulated OBS crash
TestOBSKeepAlive simulated an OBS crash right after reconnecting, while darkbot's after-connect requests (scene check, hiding old alerts) were still queued. goobs sends one request at a time, and each queued request to a dead OBS fails only after its 5 s response timeout. On a slow CI runner the drop therefore came after the test's limit: it failed on CI and once locally. The test now waits until darkbot has sent no request for a moment, as it already did after the first connect. A crash while idle is noticed at once, so the test takes about 2 s instead of 11 s. The fake OBS gained Total() for this.
Download
- Windows 10/11:
darkbot-windows-amd64.exe - macOS, Apple Silicon:
darkbot-macos-arm64.app.zip - macOS, Intel:
darkbot-macos-amd64.app.zip - Linux:
darkbot-linux-amd64
Already installed? darkbot updates itself on the next start.
Full changelog: v0.5.0...v0.6.0
darkbot v0.5.0
What's new
Chat commands: word triggers and random answers from a text file
A chat command can now react to a word at the start of a message instead
of !name. For example "hi" (with aliases such as "hallo" and "moin")
also catches "Hi!" and "hi everyone"; case and the punctuation around
the word don't matter. The streamer's own messages never trigger a word,
so their "hi" to chat doesn't make their account answer itself. A word
and a !command may share a name. Song command names are reserved only
for !commands.
A command can answer with a random line from a text file the streamer
picks:
- one answer per line; {user} and {target} work
- empty lines are skipped; a UTF-8 BOM and CRLF line ends are handled
- at most 1 MB and 10,000 lines per file
- the file is linked, not copied, and read again when its time or size
changes, so it can be edited during a stream - the same line never comes twice in a row
- a missing or empty file gives no answer, is logged, and uses up no
cooldown
"Answer each viewer only once per stream" suits greetings. It is on by
default for new word commands, and the list of answered viewers resets
when the stream goes live.
Command editor: choice of trigger, answer as text or file (it shows how
many answers the file has), and the once-per-stream switch. The command
list shows words without "!" and the answer file's name.
CI: time-box and retry the Linux package install
Ubuntu's package mirrors stalled the "Linux GUI dependencies" step for more than 15 minutes twice today: during the v0.4.0 release, which delayed the downloads, and on the next build. Each apt run now has a time limit (update 5 min, install 10 min, 30 s network timeout plus apt's own retries) and is retried up to three times. The step gives up after 20 minutes instead of blocking a release.
Dashboard: status colors, YouTube Music always in Logins
The dashboard keeps its layout and gets status colors. Each Logins card
now has a state, shown by the LED, a state word and, when the card needs
the streamer, a tinted frame:
- Running (green)
- Attention (amber): the Spotify login ends within 14 days, or Twitch
needs a reconnect for new permissions. The card says why and offers
"Connect again". - Problem (red): the last call failed, with the error shown.
- Off / Unchecked (grey)
Color is never the only sign: every state has a word too.
The YouTube Music card is always shown (off, with Connect, when it isn't
set up). It reads "Unchecked" until Pear Desktop has answered once since
darkbot started, because darkbot doesn't poll it.
Top bar: Redemptions turns red when logged in but not receiving, OBS red
in OBS output mode without a connection, Twitch amber when a reconnect is
needed.
Meters: unfollows, refused redemptions and rejected song requests show
red once they are above zero.
Download
- Windows 10/11:
darkbot-windows-amd64.exe - macOS, Apple Silicon:
darkbot-macos-arm64.app.zip - macOS, Intel:
darkbot-macos-amd64.app.zip - Linux:
darkbot-linux-amd64
Already installed? darkbot updates itself on the next start.
Full changelog: v0.4.0...v0.5.0
darkbot v0.4.0
What's new
Song requests on YouTube Music through Pear Desktop
!sr now also queues on YouTube Music. YouTube Music has no public queue
API, so darkbot uses Pear Desktop (the open-source YouTube Music app,
formerly th-ch/youtube-music) and its API Server plugin, like the
Streamer.bot extensions do. darkbot only connects to 127.0.0.1 as a
client, so it still opens no port. The streamer allows darkbot once in
Pear Desktop; the token lives in the OS keychain.
Routing between Spotify and YouTube Music:
- a link goes to the service it belongs to (open.spotify.com /
music.youtube.com, youtube.com, youtu.be) - "!sr " searches on the service chosen in the settings, or on
the other one while that one is off - !song, !next, !queue and !skip use the service playing right now
- other links get "this kind of link doesn't work here"
Pear Desktop answers "added" even for IDs it can't add, and adds
asynchronously. darkbot therefore serialises adds and watches the queue
until the song shows up (at most 5 s) before it confirms in chat. Links
are resolved by searching their video ID, so title, length and the
explicit mark are known and the length limit and explicit filter work
like on Spotify.
Tested end to end against Pear Desktop 3.12.1: search, links, playlist
refusal, duplicates, !song/!next/!queue/!skip. That run found one bug,
now fixed: Pear Desktop's Node server closes idle connections after
5 s, so a request after a pause failed with "connection reset". The
client now opens a fresh connection per request.
UI: a YouTube Music block in Settings > Song requests (switch, status,
setup steps, port, connect with cancel, disconnect) and the choice of
search service. When YouTube Music is on, the dashboard shows a card
with the date Pear Desktop allowed darkbot, its last answer and a
"check now" button.
Internals: the songs package is now service-neutral (a Player interface
with Spotify and YouTube Music adapters). Spotify gained Playing()
(Get Playback State).
Also fixed: the "Name song titles" checkbox could be reset by a refresh
before saving.
Download
- Windows 10/11:
darkbot-windows-amd64.exe - macOS, Apple Silicon:
darkbot-macos-arm64.app.zip - macOS, Intel:
darkbot-macos-amd64.app.zip - Linux:
darkbot-linux-amd64
Already installed? darkbot updates itself on the next start.
Full changelog: v0.3.0...v0.4.0
darkbot v0.3.0
What's new
Keep the activity feed, and find what happened while darkbot was off
The activity feed lived only in the window, so a restart or an update
emptied it, and nothing that happened while darkbot was closed ever
showed up.
- The feed (redemptions, song requests, channel events) is saved to
activity.json and loaded on start: the last 200 lines, newest first,
older days shown with their date. Tests are shown but not kept. A
"Clear" button (two-step) empties it. - Unfollow detection saves the follower list (followers.json, tied to
the Twitch account). The first check after a start reports unfollows
and follows from while darkbot was off, since EventSub has no
catch-up. They are marked "while off", sorted in at their follow
time, and play no sound, post nothing and don't count for the
session. - An account missing from the paged follower list is checked once more
on its own before it counts as an unfollow, so someone unfollowing
mid-read can't make a page shift look like another unfollow.
Review before v0.3.0: security, correctness and performance fixes
A full review (security, concurrency/correctness, performance) before
the first stable release, plus govulncheck and staticcheck.
Dependencies
- Go 1.27.4, Wails 2.17.1, x/net 0.63, x/crypto 0.59, x/sys 0.50,
x/text 0.44: govulncheck reported 23 reachable vulnerabilities
(stdlib crypto/x509 and net/http, x/net, Wails origin check), now
none. CI runs govulncheck from now on.
Chat safety
- One budget for everything darkbot posts (60 per 30 s; Twitch mutes
at 100) and one for event thank-yous (15 per 30 s): a follow-bot wave
can no longer make the streamer's account spam chat. - Song requests: at most 10 per minute for the whole channel.
- All of darkbot's own messages are recognised when they come back
through chat, so event thanks don't count as chat lines for timers.
Bugs
- Chat command sounds got a 404 in device output mode.
- Nothing stopped on exit (Wails v2 never cancels its context): darkbot
now has its own run context; on exit queued redemptions are refunded
and pending files saved, also when restarting for an update. - One revoked EventSub type stopped all of EventSub; channels without
channel points retried forever instead of keeping chat and events. - Start/stop of EventSub and unfollow detection could race into two
listeners; a stopped session could still report itself connected. - A redemption refused for a full queue still started its cooldown.
- Any request OBS rejected dropped the connection; an alert could stay
visible after OBS reconnected; slow attempts against something that
isn't OBS leaked a socket every 5 s (now backing off to 1 min). - Follows that arrived live were repeated as "while off" after a
restart. - A corrupt config.json stopped darkbot from starting; atomic writes
did not fsync. Now the file is set aside and defaults are used. - A local clock behind Twitch's could wipe the first minutes of a
session; clearing the feed could be undone by a save in flight.
Secrets
- The OBS password moves from config.json to the OS keyring.
- A newer fallback token file wins over an older keyring entry
(single-use refresh tokens made the older one dead). - Logout revokes the Twitch token at Twitch.
Performance
- Cooldown ring: at most 10 updates/s instead of every frame.
- State events: no more re-render every minute/5 min/30 min when
nothing changed; bursts render at most twice. - Follower list written only when it changed; EventSub dedupe pruned
every 30 s; sound files over 25 MB are refused.
Song titles in chat can be switched off
Spotify titles can be any text, and darkbot posts its answers as the
streamer's own account, which AutoMod doesn't filter: a viewer could
request a track whose title says something offensive. A new setting,
"Name song titles in chat" (on by default, like common chat bots),
lets the streamer answer requests and skips without titles; !song,
!next and !queue then say that titles aren't posted. The activity feed
still shows titles to the streamer.
Download
- Windows 10/11:
darkbot-windows-amd64.exe - macOS, Apple Silicon:
darkbot-macos-arm64.app.zip - macOS, Intel:
darkbot-macos-amd64.app.zip - Linux:
darkbot-linux-amd64
Already installed? darkbot updates itself on the next start.
Full changelog: v0.2.9...v0.3.0
darkbot v0.2.9
What's new
Watch streaks as a channel event
When a viewer shares their watch streak in chat ("watched 5 streams in a
row"), darkbot now shows it in the feed and can react like to any other
event: a sound, a chat message, an alert in OBS, optionally only from a
number of streams on. {amount} is the streak and {points} the channel
points Twitch awarded for it.
Twitch delivers watch streaks as a chat notice (channel.chat.notification,
added by Twitch in April 2026). It needs the chat permission darkbot
already asks for. The other notices on that subscription (subs, raids,
...) come through their own events already and are ignored, as are
notices from other channels in a Shared Chat.
Download
- Windows 10/11:
darkbot-windows-amd64.exe - macOS, Apple Silicon:
darkbot-macos-arm64.app.zip - macOS, Intel:
darkbot-macos-amd64.app.zip - Linux:
darkbot-linux-amd64
Already installed? darkbot updates itself on the next start.
Full changelog: v0.2.8...v0.2.9