OAuth, stream telemetry, EventSub, chat, moderation, channel management, analytics and overlays.
CLOVERCAST DOCUMENTATION
Connect it. Design it. Put it in OBS. Run it live.
Current setup and product guidance for CloverCast Desktop, CloverCast Web, Twitch, TikTok, YouTube, Kick and the OBS workflow around them.
Ctrl / ⌘ + K
Current docs: Desktop v3.4.2 · Web v3.4.2 · Website v12.4.2 · TikTok engine v0.4.8
The normal CloverCast workflow
1Sign inUse the same Luckyy Studios account on Desktop and Web.
2Choose / connect a platformTwitch, TikTok, YouTube and Kick are available. FREE uses one locked primary platform after selection.
3Design & testBuild in Overlay Studio or use dedicated TikTok tools, then test before going live.
4Add to OBSUse the Browser Source URL or a supported Desktop Add-to-OBS workflow.
CONNECT→DESIGN→TEST→OBS→GO LIVE
OBS stays the broadcast engine. CloverCast handles the creator workflow around it: live data, overlays, chat/events, automation and remote production controls.
Four platforms, platform-aware behavior
Server-side LIVE connection through the CloverCast engine, session analytics, comments/events, gifts, coins, Studio Core and automation.
Channel data, analytics, active broadcast viewers, supported Live Chat and platform-aware overlays.
Official OAuth/API integration, channel management, telemetry, chat, moderation, KICKs, rewards and webhook events.
Platform capabilities are not forced to be identical. CloverCast keeps the UI consistent but only exposes actions and analytics supported by the real integration.
The TikTok command centre
Platforms → TikTok is the main TikTok workspace. It uses a responsive four-tab layout rather than a horizontally scrolling admin-style page.
Overview
Username and Connect LIVE / Disconnect controls, engine status, viewers, peak viewers, likes, comments, shares, follows, gifts, coins, activity and leaderboard/session summaries where real engine data is available.
Studio Core
Rankings, goals, event feeds / OBS docks, last events, alerts, announcements, stats overlays, timer, social tools, Top Gifts and existing core tools.
Gifts
Gift Browser, Gallery, Interaction Bars, Gift Jar and other gift-focused tools. The catalogue comes from the VPS and supports real gift art and metadata.
Automation
TikTok Automation Studio remains integrated with existing FREE / PRO rule behavior rather than becoming a separate fork.
Dedicated TikTok OBS runtime: Top Gifter, Top 3 Gifters, Top Gift and Top Streak intentionally keep their specialised TikTok runtime instead of being forced through the generic Overlay Studio renderer.
How TikTok LIVE connects
The connection is server-side using the CloverCast TikTok engine at engine.luckyystudios.com. The current engine version for this release is v0.4.8. Public UI must never expose VPS/admin tokens.
Gift Browser data
Gift Browser should use the actual catalogue returned by the engine. Search can match gift name, gift ID or coin value; sorting and pagination should operate on that real catalogue without inventing gifts.
One editor, platform-aware workspaces
Overlay Studio supports Twitch, TikTok, YouTube, Kick and Universal workspaces. TikTok portrait resolutions such as 1080×1920 can be selected alongside standard landscape canvases.
Save projects to My Overlays, use templates/designs, preview changes and copy the Browser Source URL for OBS. PRO unlocks the broader multi-platform workspace and premium design content.
Publish what OBS needs
General overlay projects produce Browser Source output. Keep scene/platform URLs intact when copying them into OBS, and do not replace dedicated TikTok overlay URLs with generic renderer URLs when the specialised runtime is required.
CLOVERCAST→BROWSER SOURCE URL→OBS
Security: treat Browser Source keys and any authenticated bridge data as private. Admin/VPS engine tokens belong server-side and should never be placed in public page markup or client JavaScript.
A focused Twitch clip workflow, separate from CloverCast.
CloverClipper is a standalone Luckyy Studios product with a Windows desktop app and a matching web workspace. It uses one Luckyy Studios-managed CloverClipperBot for chat access, while every creator connects only their own Twitch broadcaster account.
1 · Connect broadcaster
Sign in with a Luckyy Studios account, connect the Twitch channel you stream from, then save Bot Settings. Normal users do not connect or receive credentials for CloverClipperBot.
2 · Enable triggers
Enable !clip, choose a cooldown and optionally add one exact emote trigger. Chat announcements can be switched on or off per creator.
3 · Create the clip
While the broadcaster is live, a matching chat trigger asks Twitch to create a clip. The bot verifies the result before saving and optionally announcing the Twitch clip URL in chat.
4 · Keep it organised
Each Luckyy Studios account has its own clip library. Creators can rename saved links locally or remove them from their library without changing the Twitch clip itself.
Shared bot model: creators only authorize their broadcaster account. CloverClipperBot is managed centrally by Luckyy Studios and can listen to multiple authorised channels without sharing bot credentials.
Does CloverClipperBot need to be a moderator?
The current trigger flow uses the broadcaster authorization required for chat access. Moderator status is not required for the tested !clip workflow.
Can it create clips while the channel is offline?
No. Twitch clip creation requires a live broadcast. The channel can remain configured and listening while offline, but a real clip can only be created from a live stream.
Desktop or Web?
Both use the same Luckyy Studios account and clip library. The Windows app opens directly into the CloverClipper experience after login; the web version remains available through the normal Luckyy Studios website.
Combined when you want it, filterable when you do not
Chat & Events supports Twitch, TikTok, YouTube and Kick platform toggles. TikTok comments are represented as chat/comment activity, while supported TikTok gifts, follows, shares, likes and joins remain event activity.
🟣 Twitch♪ TikTok🔴 YouTube🟢 Kick→ Combined view
Popout Chat / Events should preserve the same platform availability. TikTok popouts can show the current TikTok viewer count when real LIVE state is available.
Build event-driven actions
Automation Studio uses the events CloverCast actually receives. FREE includes up to three alert rules; PRO removes the rule limit and supports the broader multi-platform workflow.
Trigger
Select a supported platform event such as a follow, gift, chat/comment or other event exposed by the integration.
Action
Run the supported CloverCast action, overlay behavior, audio/TTS or Desktop Companion operation configured by the rule.
Desktop stays beside OBS
CloverCast Desktop connects to OBS WebSocket for local production controls. OBS Studio 28+ includes WebSocket support; a normal local setup uses the OBS WebSocket endpoint on the streaming PC.
CREATORCloverCast WebRemote UI
authenticated bridge →STREAM PCCloverCast DesktopCompanion
local WebSocket →BROADCASTOBS StudioScenes + Browser Sources
Single-PC first, remote-friendly
🖥Desktop
Lives with OBS, local assets and companion functionality. It can keep the production-side connection alive.
🌐Web
Provides the browser command surface and can use the authenticated Desktop bridge for supported remote production tasks.
FREE vs PRO
FREE
One primary platform, core Dashboard and Stream Manager, primary-platform Chat & Events, up to three alert rules, 7-day analytics, core Overlay Studio and local OBS controls through Desktop.
PRO
All supported platforms, multi-platform Chat & Events, unlimited automation, longer analytics views where data exists, premium design content, OBS Live Editor Beta, remote OBS controls and optional Dual PC mode.
Fast checks
TikTok says offline
Confirm the username, verify the creator is actually LIVE, check engine status, then reconnect. If the public app is healthy but engine state is unavailable, diagnose the VPS/connector rather than fabricating local analytics.
Overlay does not update in OBS
Confirm the correct Browser Source URL, refresh the OBS source, verify Desktop/engine connectivity for the data source, and check that the widget belongs to the selected platform workspace.
Web cannot control OBS
Desktop must be online on the OBS machine, OBS WebSocket must be enabled and the authenticated companion/PRO requirements for that action must be satisfied.
Need more help?
Use the Help or Support pages and include the platform, app version, what you expected and what actually happened.