Your chat.
Your game.
Their next move.

Before starting the listener, open Game Protection, select your running game, enable protection and apply the settings. Protection is off by default and covers the whole application, including its other windows and dialogs. It does not focus the game or send keys to the background. After restarting TikoPlay, select the game and enable protection again; the shortcut resets to F10. After restarting the game itself, stop listening and select its new process. Check that the shortcut is active; a failed shortcut change keeps the previous working registration. Focus detection and keyboard input are separate system operations, so protection reduces risk but cannot guarantee blocking every key during a window switch. Native Windows/game checks and physical shortcut verification in the packaged app remain pending.

For each profile, set a command cooldown and a per-viewer cooldown from 0 to 60,000 ms; zero disables that limit. Choose 1–100 waiting actions and an expiry time of 100–5,000 ms. Defaults are 300 ms per command, no per-viewer cooldown, 100 waiting actions and 1,000 ms validity. Save changes, then Stop and Start listening to apply them. A full queue skips new arrivals without using their cooldown, and expiry is checked before execution. These controls do not prevent bots or multiple accounts.

The activity log shows a limited sample during heavy traffic so chat spam does not overwhelm the panel. Use the exact session counters and the last 30 decisions in Spam Controls to diagnose skipped commands. These statistics are separate from the OBS overlay, which still updates after each confirmed action.

Try one comment or up to 1,000 messages over 60 seconds of virtual time, including a ready-made spam example. The report explains viewer filtering, missing mappings, cooldown, a full queue and expired actions. It uses the same saved profile limits as live control, shows their values, ignores unsaved drafts and flags an outdated report after configuration changes. The simulation does not affect live chat, its queue or keyboard output. It predicts action timing, not actual game or system latency.

In TikoPlay, open OBS Overlay, enable it, save and copy its address. Add a Browser source in OBS, paste the complete overlay URL and start with a 900 × 600 canvas. Run OBS and TikoPlay on the same computer. The overlay only displays information; it cannot start listening or change your settings. Its preview uses sample data, and simulator results do not appear in the live overlay. If OBS loaded the source before TikoPlay started, refresh that source. Browser and automated checks have passed; verification in actual OBS and on Windows is still pending.

TikoPlay sends keyboard input to the active application. Use a game that accepts those inputs and allows this kind of automation. Presets are editable starting points, not dedicated game integrations. A game is not included.

Use one platform at a time. TikTok needs a live channel. Twitch requires account authorization and a configured Twitch Client ID; the current test package does not include one. YouTube Live requires an active stream, a YouTube Data API key and available API quota. Kick uses an unofficial integration that may be affected by platform changes.

No. Viewers type commands in the platform’s regular live chat. TikoPlay runs on the computer with your game. Your computer needs an internet connection to receive chat messages.

It responds to matching text messages. Gifts, likes, paid events and audience voting are not controls in the current version.

Choose the Windows or macOS package for your computer from GitHub Releases and read that release’s installation notes. macOS builds are not notarized. Keyboard control may require system permissions. Test your setup before going live; platform compatibility and input latency can vary.