Manual › Shortcuts
Shortcuts
Manual for the Shortcuts module
This module is coming soon.
Shortcuts like Ctrl+Alt+R, gamepad buttons (Xbox, PS4 …) or MIDI pads trigger animations in the overlay or make the chat bot write – even mid-game. Knobs, faders and sticks smoothly control opacity, size, position and more via keyframe tracks. Needs the Shortcuts extension, which you download after purchase.
Needs the Shortcuts extension – so that shortcuts also work in games. Download it on the website after purchase; the app guides you through installing it. See The app → Extensions.
First steps: your first shortcut
Everything is already there to try it out:
- In the app under Shortcuts → ⚙ there's the shortcut testkrzl with Ctrl+Alt+T.
- In the Shortcuts editor choose the template “First shortcut: testkrzl” and save it, then paste the overlay link into your streaming software.
- Press Ctrl+Alt+T (even mid-game) – “testkrzl!” appears in the overlay.
Every shortcut is also a variable with its name, e.g. {testkrzl}: “ja” while you press it (at least 1 s, adjustable under “Shortcut variable on for at least”), otherwise “nein”. With it you build conditions like “show while testkrzl is pressed” – the variables are in the editor under “Your shortcuts”. On a controller/MIDI there's no release: only the minimum duration applies.
Every shortcut works like this: the name in the app (here “testkrzl”) is the trigger in the editor (“Shortcuts” tab or a trigger of type “Shortcut”). Your own shortcuts: in the app click “Record” and press the key (name optional) – then create a trigger with that name in the editor and assign layers. If the chat bot should write instead: in the chat bot editor under “Ventoview bot” create a “Shortcut” element with the name.
“Shortcuts” tab in the editor
In the module's editor – and in every design that has Shortcuts as a data source – there's the Shortcuts tab at the top. Your triggers are listed there like layers, with the assigned layers indented below.
- ⚡ Trigger creates a new one; on the right you choose the shortcut, the pause (it won't react again for this long) and the length (0 = until the last layer is finished).
- Layers without a trigger are at the bottom – drag them onto a trigger to assign them, “Detach” takes them out again (then they run normally).
- “Fire” tests the shortcut via the app – also in your streaming software.
- You create the shortcuts themselves in the app (Shortcuts → ⚙ → “Record”), then “↻ Load shortcuts” in the editor. A ? means: the shortcut no longer exists in the app.
More about gamepads, MIDI and dials: Controllers & MIDI.
Getting started
- Activate the module (app or Home → Modules).
- In the app click “Set up overlay” on the module – or Open editor.
- Choose a template, adjust it, save it and paste the overlay link into your streaming software.
Settings
In the app click ⚙ on the module – or in the editor under “Settings”.
| Setting | Meaning |
|---|---|
| Your shortcuts | Click “Record” and press the key – keyboard, gamepad or MIDI pad, the app detects it by itself. Without a name the shortcut is named after the key (e.g. ctrl_alt_t or note16); click it to rename. Use the name in the editor as a trigger (type “Shortcut”) and in the chat bot under “On shortcut”. To try it out, “testkrzl” (Ctrl+Alt+T) is already set up – matching the template “First shortcut”. |
| Shortcut variable on for at least (seconds) | Every shortcut is also a variable with its name, e.g. {testkrzl}: “ja” while you press it – at least this long, so a short press is visible in the overlay too. |
| Dial | “+ Dial” for every knob, fader, stick or trigger. Then calibrate: “Record min”, move the dial and turn it all the way down, “Done” – then the same with “Record max”. In the editor you choose it on a keyframe track, in texts its name is the variable, e.g. {fader_left} (0–100). |
Variables
Use in texts and conditions, e.g. {shortcutname}. You see the sample values in the editor as long as there's no real data.
Shortcuts
| Variable | Meaning | Example |
|---|---|---|
{shortcutname} | Last pressed: name | results |
{shortcutkeys} | Last pressed: keys | Ctrl+Alt+R |
{shortcutcount} | Pressed since start | 3 |
{shortcutlist} | All shortcuts | results (Ctrl+Alt+R) · gg (Ctrl+Alt+G) |
Trigger
In the editor under Settings → Triggers: Shortcuts. Layers you assign to the trigger only appear when it applies.
Behavior
- Play: Once per key press
Templates
| Template | Description |
|---|---|
| First shortcut: testkrzl | To try it out: Ctrl+Alt+T (shortcut “testkrzl”, already set up in the app) shows “testkrzl!”. Every shortcut works like this: name in the app = trigger in the editor – and {testkrzl} is “ja” while you press it. |
| Shortcut reactions (3 triggers) | results → big announcement with fanfare · gg → GG explosion · hype → fire rain. Create shortcuts with these names in the app. |
| Shortcut popup | Every key press appears briefly at the bottom – with name and keys |
| Shortcuts bar | Permanent bar with all shortcuts and how often they were pressed |
| Dial control | Dial 1 sets the opacity, dial 2 fills the arc, dial 3 enlarges the star – on a MIDI device or controller |
Elements
Ready-made building blocks in the editor (on the left under Layers):
- GG explosion – “GG” bursts out of the middle
- Fire rain – Fire, explosions and lightning rain down from above