Literal values can simply be written as they are, as long as they do not include a colon.

For example: 3, true, or page1

Sometimes you might also want to specify an array of values. In this case the values are enclosed in brackets, with individual values separated by commas, for example, [red, green, blue].

In special cases where your value contains a lot of special character you might want to prefix the value with String: to explicitly tell reactor that the rest of the value is a literal value.

Eg: String:{"DATA":"Custom JSON value"}

Variables can be referenced by combining the type and the variable key.

For example: Var:SEC_Page or Var:DeviceIndex

Modifiers can be added at the end

For example: Var:SEC_Page:Name (displays the friendly name of the variable) or Var:DeviceIndex:Current:Name (displays the label of the current value)

Parameters of devices follow the following syntax:

DC:[name of the core¹]/[device index]/[name of parameter]/[dimension1 index]/[dimension2 index]/...:Modifiers

The device index and the dimension indexes can be set in different ways. They are IOReferences itself, meaning that it can be a Variable, BehaviorConstant or any other reference. If this reference would include slashes (/) it needs to be wrapped in curly braces {}

Examples: DC:bmd-atem/{Var:DeviceIndex}/AuxSource/{Var:AuxChannel}/

Reference to AUX sources on the ATEM switcher with Device ID found in "Var:DeviceIndex" and in the AUX Channel denoted by "Var:AuxChannel".
Both examples provided are identical. In this scenario, encapsulating the nested IO Reference is not required, as there are no forward slashes included that might interfere with the parsing process.

Panel Parameters like brightness and sleep can be controlled using this type of parameter reference

The basic format looks like this:

Panels:[target type]/[target index]/[panel parameter type]

Target Type can be one of the following:

• Canvas - Directly address the whole canvas (panel group) by it's id
• Panel - Address a specific panel by it's id
• CanvasOfPanel - Address the whole canvas (panel group) of the panel specified by the target ID

The target index can be set in different ways. It is an IOReferences itself, meaning that it can be a Variable, BehaviorConstant or any other reference. If this reference would include slashes (/) it needs to be wrapped in curly braces {}

Important: Normally the way addressing is done in reactor for panel parameters is like so: Panels:CanvasOfPanel/Behavior:Panels/[panel parameter type]. This makes sure we always address the full panel group of the panel that the behavior is mapped to. In most cases this is the best way to do it.

Panel Parameter Type can be one of the following:

• SleepTime (minutes)
• DimTime (in minutes)
• DisplayBrightness (0-8)
• LEDBrightness (0-8)
• GlobalBrightness (0-8)
• Sleep (binary: "on", "off") - (Is reset by the panel when it wakes up again. It's probed once a second, so it can feel a little like a "hold down" function)
• ResetSleepTimer (one-shot trigger)
• Name (read only)
• Model (read only)

System Variables can be accessed using the System parameter Type.

Current list of possible options:

• System:PanelLock - Lock function for the whole of reactor

• System:IPAddress - Show the IP Address of reactor. Can also change the system IP using a set value command or the SKAARHOJ:ChangeIP Settings Template

• System:CurrentProject - Allows to trigger a change of projects using SetValue

• System:RestartEngine - Perform a restart of reactors engine, like switching projects

• System:ProjectTitle - Show current Project title

• System:ConfigTitle - Show current name of root layer

• System:UptimeFormatted - Show uptime since Reactor was started

• System:Panels:Connected - Number of currently connected panels

• System:Panels:Warnings - Number of panels with warnings

• System:Panels:Unconnected - Number of unconnected panels (errors)

• System:Panels:LastEvent - Last event as a string, eg. "Down (T)" if a four way buttons top edge was pressed down.

• System:Panels:LastEventSource - The HWC source of last event, including panel ID, on form "P[panel id]#[HWC id]", for example "P1#43"

• System:Devices:Connected - Number of connected devices

• System:Devices:Warnings - Number of devices with warnings

• System:Devices:Unconnected - Number of unconnected devices (errors)

• System:Devices/[idx]:Name - Name of devices. idx is just an index.

• System:Warnings - Total number of warnings in Reactor

• System:Errors - Total number of errors in Reactor

Using Behavior Parameters you can reference some of the values configured for the current Behavior or show some information about it. This is used in many of the built in Settings Templates

Format: Behavior:[sub type]:[additional type]:Modifiers...

Subtypes

• IOReference (main parameter reference)

Using this subtype the main Parameter in the Behavior can be referenced. Additionally Modifiers can be added. This way you can refer to the main parameters value or name without having to hardcode it in other parts of a behavior (like feedbacks or event handlers)

Examples: Behavior:IOReference:Name (Display the main parameters Name) or Behavior:IOReference:Current (Display the main parameters current value)

• Const (BehaviorConstant)

Using Behavior:Const:[constant key] you can access constant fields of the behavior. This way you can create SettingsTemplates for behaviors that have certain constant fields that can be customized in an easy way. This is used in many of the built in Settings Templates

Advanced Subtypes

Several other subtypes exist to access information about the current behavior:

• Name The friendly name of the behavior

• Path - Returns the "path" of the behavior in the layer tree. Eg. "0/3/0/A3"

• ID - Returns the behaviors main mapping to a panel, for example "_p4.32" (panel Id 4, Hardware Component (HWC) 32)

• Panels - An array of all Panel Ids this behavior is mapped to (used mainly for accessing panel parameters, see below at Panel Settings)

• Script - Using the Script subtype you can access information about current running scripts of this behavior. See

• LastEvent Access information about the last hardware event (trigger) received by the behavior.

  IO Reference	Comment
  Behavior:LastEvent:Type	Type of last event. Options: Binary, Pulsed, Analog, Speed
  Behavior:LastEvent:TimeToNow:[Limit]	This returns the time in milliseconds that has passed since the last event. Although setting a limit is optional, it's recommended to set it at or above the comparison value for performance efficiency. If a limit is set, it designates the maximum returned value.
  Behavior:LastEvent/Binary:Pressed	Returns whether the last binary trigger was pressed (ActDown) or not (ActUp). Options: true, false
  Behavior:LastEvent/Binary:Edge	Returns which edge the last binary trigger sent. Options: NoEdge, Top, Left, Bottom, Right, Encoder
  Behavior:LastEvent/Pulsed:Direction	Returns the direction of the last pulsed trigger received
  Options: Up, Down
  Behavior:LastEvent/Pulsed:Value	Returns the value of the last pulsed trigger
  Behavior:LastEvent/Analog:Value	Returns the value of the last analog trigger (0 to 1000)
  Behavior:LastEvent/Speed:Value	Returns the value of the last intensity trigger (-500 to 500)

• Events
  Access information about the last event handler received by the behavior.

  Behavior:Events/[event handler key]:TimeToNow:[Limit]

  Returns the time in milliseconds that has passed since the last accepted trigger for the specified event handler. It is recommended to set a maximum limit for performance reasons in reactor.

  Behavior:Events/[event handler key]:SequenceStep: The current sequence step being executed (See Binary Sequence)

Preset Parameters are used to control reactors Parameter Preset Engine. You can learn more about here: Parameter Preset Engine

The basic Format looks like this:

Preset:[preset kind name]/[command]/[preset index]/[device index]/

Command can be one of the following:

• Store
• Recall
• Delete

The preset index and the device indexes can be set in different ways. They are IOReferences itself, meaning that it can be a Variable, BehaviorConstant or any other reference. If this reference would include slashes (/) it needs to be wrapped in curly braces {}

Flags can be referenced to set, clear or display them. The basic format looks like this:

Flag:[flag group name]/[flag color]/[flag number]:modifier1:modifier2:modifier3

Make sure you have created a flag group before to use this. More info can be found here Flag Groups

The Flag color can be selected from the fixes list of [Red, Gree, Blue, White]

Finally a index between 0 and 99 can be selected

Note: Flags are generally used for SKAARHOJ Default Tally Forwarding and Routing Triggers. otherwise most things that can be done with flags can also be achieved with variables.

This type of parameter reference allows read only access to a value in a constant set table directly.

This can be useful to access settings values defined on the home screen or access values of a constant set in virtual triggers.

Reactor's constants are unchangeable values embedded in the configuration code, used for various purposes within the configuration. Unlike variables, constants can only be modified by altering the configuration. Constant Sets in Reactor are essentially tables of related constants.

The basic format looks like this:

Const:[constant set name]/[row index]/[constant name (column)]/:Modifiers...

Row Index can be set in different ways. It is an IOReferences itself, meaning that it can be a Variable, BehaviorConstant or any other reference. If this reference would include slashes (/) it needs to be wrapped in curly braces {}

Examples:

Const:CameraSelector/0/CameraName

Returns the value of the constant called "CameraName" in the first row (index 0) of the constant set "CameraSelector".

Const:CameraSelector/{Var:CameraIndex:Current:Offset:-1}/CameraName

This retrieves the value of the constant CameraName from the row in the CameraSelector constant set, as indicated by the CameraIndex variable. If the CameraIndex variable is set to 1, it refers to the first row (index 0), because the variable's value is reduced by one when inserted as the value for the row index. (:Current:Offset:-1)