Bindings & triggers.
A binding is one or more actions plus the trigger that fires them. Build them on the Remote Control page and run them from chat, a dashboard button, or a hotkey URL.
Actions
An action is a single thing to do in OBS or Meld: switch a scene, show or hide a source, mute or unmute an input, set a volume or gain, start or stop recording or streaming, and more. Source and layer pickers are scoped to the scene you choose, so you only see what lives in that scene.
Triggers
Every binding fires from one of three triggers:
- A !command in chat, with a who can use it picker so you choose exactly which roles (Broadcaster, Moderator, VIPs, Subs, or Everyone) are allowed to run it, plus an optional cooldown so it cannot be spammed. You can always run your own commands.
- A dashboard button on the Remote Control page that you press yourself.
- A hotkey URL you can copy onto a Stream Deck button or a keyboard macro to fire the binding without opening anything.
Several actions at once
A binding can run several actions in a row, for example mute your mic and hide a source and then switch to your "Be right back" scene. A binding can include at most one scene switch, and the scene switch always runs last, so the rest of your changes are in place before the new scene comes up.
Make a binding that mutes your mic, hides your camera, and switches to your break scene, then give it a !brb command limited to your mods and a Stream Deck button. One press and you are off.
Turn a source into a reward. Make a binding that shows a fun source or layer | a confetti burst, an emote rain, an air-horn clip that plays once and clears itself | then give it a !hype command limited to Subs with a short cooldown so it cannot be spammed. Now your subs can set off a little moment on stream as a perk, and the cooldown keeps it special, all without you lifting a finger.
Commands you create register in your bot command list as read-only, managed by Remote Control, so they can never clash with your other commands.