Logic Rules
Logic Rules are for conditional behavior. Use them when a prop should only run actions after several requirements are true or to combine multiple triggers into a single action path. You can also chain Logic Rules into each other to build more complex logic nesting Any/All/None setups.
UI path
- Open Configuration.
- Select Behavior.
- Open the behavior/rules area for Logic Rules.
- Add or edit a rule, naming it clearly.
- Add conditions.
- Choose whether all or any or no conditions must match.
Controls
| Control | What it does |
|---|---|
| Rule name | Human-readable label for the condition set |
| Conditions | State, input, analog, RFID, variable, sequence, collection, or integration checks |
| Match behavior | Determines whether all conditions or any condition can pass |
| Refire after | 0 means it fires only when transitioning from false to true. Putting a timer here allows it to continuously fire as long as it remains true with that delay between each. |
Firmware 1.1 additions
Logic Rules include switch/router mode improvements for routing one condition result into different behavior paths without duplicating the same checks in several places. Rules can also be enabled or disabled at runtime, which gives you a cleaner way to pause parts of the logic during resets, service flow, or alternate game branches.
Logic conditions support keyboard copy/paste, making it easier to reuse a tested condition group while building larger rules. Variable conditions can also use the 1.1 structured lookup and random/pick expression improvements where appropriate.
When to use Logic Rules
Use Logic Rules when the behavior reads like a sentence with multiple requirements. For example: when the prop is armed, all four switches are correct, and the RFID collection is complete. Logic Rules have no outputs aside from triggering themselves. You will use Action Triggers to define the output of what happens when a Logic Rule triggers.