Examples
A handful of Logic Rules patterns we've seen built across haunts, escape rooms, and immersive attractions. Use them as starting points and adapt to your install.
1. Simple input → show
The hello world. Wire a button to a show.
Use the Triggers button on the show. This is exactly what it's for.
2. Random scare from a pool
Every guest who walks past the sensor gets a scare, but you have three different scares and you want them shuffled.
Set the Random block's output count to match your number of scares (here, three). Each guest gets one of the three picked at random, with equal odds. Want one scare to come up more often? Wire it to two of the outputs.
3. "Rare scare" every Nth guest
Most guests get the regular scare. Every fifth one gets a special one instead.
Set the Every Nth Trigger block to 5. Guests 1 to 4 get the regular scare, guest 5 gets the rare one, and the count starts again on its own, so the rare scare also plays for the 10th guest, the 15th, and so on. The two outputs never fire for the same guest.
If the rare scare should play as well as the regular one, wire the sensor straight to the regular show and through a Counter with Auto-reset on to the rare show.
4. Take turns through a set of scares
Three scares in a fixed rotation, so back-to-back groups never get the same one.
Each time the sensor fires, the Cycle block moves to the next output. Leave Start again after the last output on and it goes A, B, C, A, B, C. Compare this with example 2: Random can pick the same scare twice in a row, Cycle never does. Cycle needs firmware 2.2.3 on the controller that runs the rule.
5. Any of several buttons
Four doors in a hallway. Opening any of them plays the same creak, even if another door is still standing open.
An Or gate would not work here: it stays on while any door is open, so a second door opening changes nothing. Any Input fires again for every door. It needs firmware 2.2.3 on the controller that runs the rule.
6. Escape room: four switches in any order
Four magnetic switches must all be flipped to unlock the next phase. Order doesn't matter; all four must be set.
Each Latch captures a switch flip and holds it on. The And gate fires when all four latches are set. Add a reset input to each Latch (driven by a phase-reset button) so the room can be reset between groups.
7. Escape room: a timed combination
Four buttons must be pressed in the right order within 20 seconds. Each correct press lights the next lamp, a wrong press plays a buzzer, and running out of time resets the attempt.
Arrange the buttons in the Sequence block's Step order list, turn on Limit attempt time, and set Complete within to 20 seconds. The clock starts on the first correct press. Choose Keep progress if a wrong press should only sound the buzzer, or Start over if it should send players back to the first button. Step outputs, the time limit, and the buzzer in Keep progress mode need firmware 2.2.3 on the controller that runs the rule.
Connect a room-reset button to the Sequence block's Reset input and press it between groups. After success, the puzzle stays completed until you reset it. Reset clears the puzzle progress and Success output; it does not stop shows or audio already playing. Reset the lamps and other effects separately as part of your room-reset setup.
8. Multi-controller coordination
Input on Box A fires a lighting show on Box B and an audio show on Box C.
A rule on any controller can fire a Show Trigger for any show in your Studio, including shows that run on other controllers. So Box A's input launches the lights on Box B and the audio on Box C just by firing each show's trigger. Firing shows across controllers is one cross-controller path; you can also watch another controller's input directly inside a rule (example 11 below, and the Input block). Named Triggers, by contrast, only chain rules within the same controller.
9. Webhook bridge
External system fires a webhook → your show fires.
Studio gives you a unique URL for the webhook. Configure your external system to hit it. When it does, your show fires.
For the reverse direction (show fires → external webhook), use a Webhook Emitter:
See Webhooks for details.
10. Anti-spam with a delay
Sensor fires too frequently? Use a Latch + Delay + reset pattern to ignore re-triggers for a window.
The sensor fires the latch and the show. Five seconds later, the delay output resets the latch. Within the 5-second window, additional sensor fires don't re-trigger because the latch is already set.
If all you need is "ignore repeat presses for a while," set a Cooldown on the input instead. It needs no rule at all.
11. Watching inputs on other boxes
The rule runs on one controller (the executor), but its Input blocks can watch inputs on any controller in your Studio. A dedicated input controller like the Input 16 makes a natural brain: it executes the logic while pulling signals from boxes all over the building.
Each Input block simply points at another controller's input instead of a local one; the signal rides the local network, so the boxes must share it. This is the mirror image of example 8: there, one input fired shows on many boxes; here, many boxes' inputs feed one rule.
When examples aren't enough
If you've designed a rule and you're not sure it's going to work, try it in the rule editor first. The editor's preview lets you try inputs and watch the logic respond, without running any real effects. Then deploy the rule and use Direct Trigger to fire its inputs for real, with everyone clear of the effects.
For thornier debugging, drop us a note on Discord. We've seen most patterns and can usually point you at the right approach.