Score a switch

Score a switch

You’ll take a device you’ve already placed and author its scoring rule against the live engine — changing what it’s worth, gating it behind a condition, or having it update a variable.

  1. Open the Rules Editor. If the toolbar has no rule-editing buttons you’re on the sample (a ?sample URL) — drop that parameter and reload.
  2. Press / and type the device’s name (bumper_001) to find it.
  3. Select its Scoring rule ◆ node — the only editable node kind.
  4. Use Points to change the award, or + Rule to add a second rule on the same trigger.
  5. Optionally add a Condition like var.frenzy_active > 0 so it only scores in a mode, and Updates like combo = var.combo + 1 to track state.

You should see — the graph re-render from what the engine accepted, and the new value award the next time you hit that device in the table view.

An edit the engine rejects comes back with its exact reason in a red banner and nothing changes, so you can’t leave the diagram describing a rule that isn’t real. Ctrl/Cmd+Z undoes any of it. A blank Condition, Emit, or Updates field clears that aspect — cancelling the dialog instead leaves the rule untouched.

Faster route: right-click the device in the Object Editor and pick Open in editor ▸ Rules editor to land on its node directly.