YouTube channels connected to StreamElements now get two more paid event types.
Kick subscriber totals in the dashboard and overlay session data now refresh from Kick’s active subscriber count, including gifted subscriptions.
Previously, the total kept increasing with subscription events, including renewals, without correcting for expired subscriptions. This could leave StreamElements showing more subscribers than your Kick dashboard.
Kick channels connected to StreamElements now get the full treatment for KICKs, Kick’s paid gifts.
{name}, {amount} and {message} variables and amount-based variations, including “Session top”.kicks-* session data keys and a kicks-latest listener, shaped like the Twitch cheer keys.Channels that connected before today are being resubscribed to the new Kick event in the background. If your channel does not receive KICKs events, log in to StreamElements again and it will pick them up.
The new channel.chatbot.audiencequeue topic delivers audience queue events in real time: queue opened, updated, and closed, plus member joins, selections, and removals.
The Language filter is now available under Chatbot → Spam filters.
Pick the languages your chat is allowed to use, and the bot moderates messages written in anything else. It detects 75 languages, and you can add emote names and channel slang to Ignored words so they never sway the result.
The filter only acts when the detector is sure. Short messages like gg or ok carry too little signal to identify, so they are left alone rather than punished. Minimum detection confidence sets that bar, and defaults to 40%.
Four chatbot modules that previously had no documentation now have full pages:
!ticket max, subscriber luck, and the full lifecycle from start to drawing winners.!bet, including the exact payout formula (winners take their stake back plus a proportional share of the losing pool).Every command syntax, bot message, and settings table was checked against the chatbot source before publishing.
We ran a full accuracy review of the documentation, checking claims directly against the chatbot and realtime service source code. Highlights:
channel.session.reset delivers session data flat under data (not data.session) — the payload reference and all client examples now agree. Session keys are documented in their real follower-latest format, and channel.session.update’s full payload is now listed.!raffle and !sraffle arguments are optional — defaults, caps, and the automatic winner-count brackets are now spelled out.If you spot anything that doesn’t match what the product does, the Edit page link at the bottom of every page goes straight to the source on GitHub.
The StreamElements documentation has moved to a new site built on Astro and Starlight.
Alongside per-product navigation and faster search, the new site adds this changelog — with per-product RSS feeds at /changelog/rss.xml — and an AI-friendly llms.txt.
The WebSocket documentation has been overhauled to match the protocol spec of Astro, StreamElements’ dedicated pubsub websocket gateway.
The docs now cover the full connection lifecycle — the welcome message on connect, the server-side heartbeat (PING frames every 30 seconds, with a 70-second pong timeout), reconnect tokens for resuming after a graceful shutdown, and the error codes returned when the server is draining or the connection rate limit is exceeded.
The new channel.overlay.broadcast topic delivers custom events to a channel’s overlays in real time. Events can target all overlays globally or a specific overlay by ID.
Each event carries a custom event name (max 256 characters) and a custom payload of up to 5KB.
Added a new variable: $(teamfighttactics).
Also fixed an issue which caused some Viewer Queue commands to send multiple responses.
Added support for Twitch Warnings in spam filters and banned words.
A new dropdown menu lets you customize the moderation action taken:
Fixed an issue with Link Protection which could flag emote combinations as links on YouTube.
The loyalty system now distributes points and watchtime more dynamically, replacing the previous fixed 10-minute interval for all channels:
We gave the Chatbot documentation a comprehensive update for clarity and accuracy:
$(channel) docs, including previously missing arguments$(user) and $(sender) variable docs