Yes, <key> has permission to operate the unit. Sent in response to auth or auth-compare messages.

The device was successfully installed and may now send active commands.

Device installation unsuccessful; usually caused by another device in the same slot or refusal of a foreign connection.

The user has typed @<command> <parameters>; handle accordingly.

Returns the value of a specified setting in response to a conf-get query. If multiple requests were made in the original message, then they will be returned separated by linebreaks.

See combat protocols.

Sends the device address/key relation over the light bus. Multiple messages may be sent if the whole list is more than 240 characters (around 5 devices), so if caching the output of this message, clear the stored value before sending devices, not when receiving it.

See combat protocols.

The user <id> has requested the device's status. Send chat containing this information to <id> on channel 0.

The user <id> has requested access to the device's menu interface. Present some form of UI (llDialog(), hotlinked text, Facet welcome, etc.) to <id>. If using a nonstandard presentation mode (e.g. Facet), warn the user on channel 0. Note also that hotlinked text is incompatible with the controller's chat forwarding mode; depending on the device in question it may be sensible to warn users of this, too.

The indicated policy is in the given state. State information is usually 1 (enforced) or 0 (unenforced), although the 'radio' policy uses 1 to indicate users only and 2 to indicate owners only.

The curfew policy will provide additional information: <state> <time> <triggered> <home_sim> <home_pos>

The key indicated can provide port functionality of the type. Resend request, to <key>. This message is sent in response to a port-connect query by hardware that wishes to connect a cable to the system.

Something is connecting to the device that receives this message. Trigger connect effects.

Something is disconnecting from the device that receives this message. Trigger disconnect effects.

Send cable particles to <key>. This message is sent in response to port-connect if the controller itself has ports on it.

The main controller's device manager has been reset. All devices that wish to use active messages must send the add message again to register with the controller, or they will be rejected.

Uninstallation successful; proceed.

Uninstallation not successful, don't proceed (e.g. removing a battery while the power is on)

See combat protocols.

sxdwm (exhibition 4) session <session-number> has been created for <key>.

See combat protocols.

See combat protocols.