• Getting Started
  • Platforms
  • Twitch
  • YouTube
  • Kick
  • Velora
  • Integrations
  • Amazon Polly
  • Crowd Control
  • Discord
  • DonorDrive
  • Fourthwall
  • Google Cloud TTS
  • IFTTT
  • JustGiving
  • Ko-fi
  • Loupedeck
  • Lumia Stream
  • Meld Studio
  • Microsoft Azure Speech
  • mtion studio
  • OBS Studio
  • Pally.gg
  • Patreon
  • PixelChat
  • PolyPop
  • Pulsoid
  • Rainmaker
  • ResponsiveVoice
  • SAMMI
  • Stream Avatars
  • Stream Deck
  • StreamElements
  • Streamlabs
  • Streamlabs Desktop
  • Streamloots
  • Throne
  • Tiltify
  • TipeeeStream
  • TITS
  • TreatStream
  • TTS.Monster
  • Twitter / X
  • veadotube
  • Voicemod
  • VTS Pog
  • VTube Studio
  • XSplit
  • Actions
  • Actions
  • Chat Action
  • Command Action
  • Conditional Action
  • Consumable Action
  • Counter Action
  • External Program Action
  • File Action
  • Game Queue Action
  • Group Action
  • Input Action
  • Moderation Action
  • Music Player Action
  • Overlay Action
  • Platform Message Action
  • Random Action
  • Repeat Action
  • Script Action
  • Serial Action
  • Sound Action
  • Special Identifier Action
  • Streaming Software Action
  • Text To Speech Action
  • User Lookup Action
  • Wait Action
  • Web Request Action
  • Action Groups
  • Events
  • Commands
  • Consumables
  • Consumables
  • Currency
  • Rank
  • Inventory
  • Stream Pass
  • Redemption Store
  • Overlays
  • Overlays
  • Overlay Widgets
  • Chat Widget
  • Custom Widget
  • End Credits Widget
  • Event List Widget
  • Game Queue Widget
  • Goal Widget
  • HTML Widget
  • Image Widget
  • Label Widget
  • Leaderboard Widget
  • Persistent Emote Effect Widget
  • Persistent Timer Widget
  • Poll Widget
  • Stream Boss Widget
  • Text Widget
  • Video Widget
  • Wheel Widget
  • YouTube Widget
  • Chat
  • Chat
  • Chat Commands
  • Pre-Made Chat Commands
  • Timers
  • Games
  • Moderation
  • Game Queue
  • Giveaways
  • Quotes
  • Music Player
  • Webhooks
  • Users
  • Reference
  • Special Identifiers
  • Developer API
  • MCP Server

  • The Timers feature allows you to run a series of commands on an automated basis. A timer command is run every time both of the following requirements are met:

    • The minimum time has occurred since the last timer command
    • The minimum number of messages have occurred in chat since the last timer command

    By default, all timers will follow the above settings. However, timers can run in more unique scenarios when you assign them to a group. There are 3 “categories” of timers that exist:

    1. Timers not in a group
    2. Timers in a group but without a timer interval
    3. Timers in a group with a timer interval

    All the timers in #1 & #2 are assembled together into one “mega group”. All the timers in this group will run one-after-another based on the global timer settings you set at the bottom of the Timers page (EX: You have 8 timers in total across various groups and the interval is set to 10 minutes, it’ll take 80 minutes to run through all the timers). So timers that fall into #2 are essentially more of a visual organization tool (EX: Here’s all my social media timers).

    All the timers in #3 are grouped up based on their groups and each group will run independently based on their own timer intervals. So if you have a group that has a timer interval of 5, it will run 1 timer from that group every 5 minutes as its own dedicated set of timers. These will run in parallel to the timers explained in the paragraph above. However these timers do not respect the global timer settings, which includes both the global timer interval & min messages. They only follow the timer interval set for the group.

    So here’s a more full example of how it’ll play out. Let’s say your global timer setting is once every 5 minutes and you have the following timers:

    • Timers not grouped
    • Timers grouped but without a timer interval
    • Timers in group A with a 10 minute interval
    • Timers in group B with a 20 minute interval

    You’ll have 3 sets of timers running in parallel to each other:

    • Every 5 minutes it’ll run a timer from the set of not grouped and grouped but without a timer interval
    • Every 10 minutes it’ll run a timer from group A with the 10 minute interval
    • Every 20 minutes it’ll run a timer from group B with the 20 minute interval

    Site Settings

    Accessibility

    Choose how the site looks. System follows your device setting.

    Cookies

    Choose which cookies to allow. Your preference is saved for 6 months.

    Necessary
    Required for the site to function correctly. Cannot be disabled.
    Analytics
    Helps us understand how visitors use the site. No personal data is shared with third parties.