DYNAMIC TIMERS

If you want to use any other trigger than a Command or Channel Point Reward, you can use the variables that you see in the respective actions, like timerId, timerName or timerValue. If both, the variables as well as rawInput are available, rawInput will always take priority. timerId will always take priority over timerName if both are available.

Under Custom -> DYNAMIC TIMERS you will be able to find various triggers that populate variables with the timer's info.

Available variables:

• timerName string - the name of the timer
• timerId int - the ID of the timer
• timerInitialDuration string - A timestamp in a hh:mm:ss format of the starting duration.
• timeStartedAt datetime - Date and time of when the timer initially started.

You can add URL Parameters at the end of the URL to customize certain things. The first parameter is getting added with a ?, every additional one with a &.

Example: https://tawmae.xyz/overlays/dynamic-timers.html?hideBackground=true&font=Segoe+UI&idColor=pink

How can I create a timer with a Channel Reward?

For any trigger other than a command, you will have to use the variables seen in the 1 - Create Timer action: timerName, timerDescription and timerValue. For best practice the variable subactions in the 1 - Create Timer action are disabled, so they don't overwrite our previous values.



What you do is create a new action, then add your channel reward trigger and the Core -> SetArgument subactions. You can then specify the title, description and the duration of the timer. And they accept variables too, and since we use a channel reward trigger, we can use stuff like %rewardName% or %rewardCost%.

We then use a Core -> Actions -> Run Action subaction to run the 1 - Create Timer action. And we pass the variables over to it, so it'll create a timer with our set values. You can now create as many actions as you like, with any triggers you like and apply the same logic to all of them :)

How do I trigger something when a timer ends?

You can check the Custom Triggers section above to see what custom triggers are available and what variables they offer. In our case, we want the Timer Finished trigger. But since that trigger fires for ALL finished timers and not just specific ones, we have to do the filtering ourselves.

For that we create a Core -> Logic -> If/Else subaction and check if the variable timerName matches the title of our timer we want this to trigger on. So let's say our timer is called "AFK", then we check if timerName equals AFK and if so, continue. But if it doesn't we break the action. So then below the if/else check you can add the subactions that fire when our AFK timer finishes, like playing a sound and sending a message to chat.

My triggers fire multiple times even though they should just fire once, why?

That's probably because you have multiple instances of the script running, e.g. having two Browser Sources with the dynamic timer in them. You are only supposed to run a single browser source. If you want to have the timers in multiple scenes, use nested scenes or Source Clones instead.