passive messages
The safety bolts have been engaged or disengaged. This corresponds to the underlying state imposed by the @bolts command. If the bolts are on, then peripherals should be locked in place (@detach=n in RLV); if they are off, then the detachment restriction should be released (@detach=y). The automatic bolts setting (release when powered down) is handled by the controller, so it is unnecessary to check whether the system power is on before reacting to the bolts message over the light bus.
This message is sent to newly-authenticated active devices immediately following the add-confirm message.
This message is sent to newly-authenticated active devices immediately following the add-confirm message.
The unit has entered or left the 'broken' state, which indicates that it has been damaged. Apply appropriate sound and visual effects. This is applied automatically in response to ATOS damage, as well as briefly following a teleport. Additionally, it may be manually controlled with the !broken and !fixed cortex commands.
The unit is being carried by the avatar <key> using the handle device at address point <device>. If no handle applies, then <device> will be "none".
The actual charging process has begun or ended. Apply visual effects as appropriate. This message will be sent even when connecting to a stative wireless charger, such as a Destruir Technologies Wireless Charging Station.
The system's current color, measured in floating point (i.e., each value must be in the range [0, 1].) Sent whenever it changes, or in response to the color-q message.
The system's current secondary color, measured in floating point (i.e., each value must be in the range [0, 1].) Sent whenever it changes, or in response to the color-q message. By convention, the secondary color is recommended for indicating a positive situation or outcome on devices and may default to green.
The system's current tertiary color, measured in floating point (i.e., each value must be in the range [0, 1].) Sent whenever it changes, or in response to the color-q message. By convention, the tertiary color is recommended for indicating a negative situation or outcome on devices and may default to red or orange.
The system's current quaternary color, measured in floating point (i.e., each value must be in the range [0, 1].) Sent whenever it changes, or in response to the color-q message. By convention, the quaternary color is recommended for indicating a concerning or urgent situation on devices and may default to yellow.
There is a device at address <device> with the key <key>. This is normally only sent to the HUD, either in response to a device addition or in bulk when the HUD is installed. This message is deprecated in 8.6 in favor of device-list, which is more efficient.
The current fan speed, measured from 0 to 100.
The unit has been instructed to follow the avatar or object <target>. This can be requested with the follow-q message. Devices such as collars may desire this information so they can send leash particles. If the unit is not following anyone or anything, then <target> will be NULL_KEY.
The unit's motors have been locked in place (or released) for some reason other than normal disablement of the movement subsystem. This commonly occurs during charging, or when carried using a handle device.
Reports the system's current gender settings for the attribute <topic>. Supported topics are physical, mental, or voice. For <value>, the format varies by topic; physical and mental genders will describe a full set of comma-separated pronouns and the name of the gender, while voice gender only supplies the name of the gender.
Examples:
Examples:
- The unit's physical gender is 'inanimate': gender physical its,its,it,it,itself,inanimate
- The unit's mental gender is 'female': gender mental hers,her,she,her,herself,female
- The unit's voice gender is 'male': gender voice male
Correct usage in role play: It is recommended that the physical gender be used to specify pronouns in emotes, e.g. /me uses <physical possessive pronoun> charger., and the mental gender be used when the unit speaks about itself, e.g. /me says, "This unit is <mental subject pronoun> whom you seek.". Voice gender should be used only to decide what sort of vocalizations to play; e.g. a grunt of pain or pleasure might be based on voice gender.
Less obviously, Speech Standard 1 dictates that physical gender be used when speaking about another, not mental gender; units abiding by SS1 regard their physical gender as the "truth" and mental gender (especially if inanimate) as a form of subjugation. While this is contrary to the experience of organic gender minorities, it synergizes well with gender transformation fantasies: in most such scenarios, a physical change may precede a mental one if they are not simultaneous, and the very act of assuming another's physical gender to be accurate plays into the reinforcement process of the acceptance of change. Personas and other scripts may elect to use such "forward-looking" or "objective" pronouns to refer to the unit in canned speech if it facilitates an intentional change in identity.
Less obviously, Speech Standard 1 dictates that physical gender be used when speaking about another, not mental gender; units abiding by SS1 regard their physical gender as the "truth" and mental gender (especially if inanimate) as a form of subjugation. While this is contrary to the experience of organic gender minorities, it synergizes well with gender transformation fantasies: in most such scenarios, a physical change may precede a mental one if they are not simultaneous, and the very act of assuming another's physical gender to be accurate plays into the reinforcement process of the acceptance of change. Personas and other scripts may elect to use such "forward-looking" or "objective" pronouns to refer to the unit in canned speech if it facilitates an intentional change in identity.
The system has been exposed to ACS interference, described here. The <type> field is a string consisting of the single-character constants for each class of interference, concatenated together. For practical reasons, these are indicated based on the types of function impairment they cause.
For example, a type of "MCY" indicates that motor control, cortex operation, and memory access are all impaired. At the conclusion of interference, "interference-state " is sent, with a trailing space.
| class | effects |
|---|---|
| M | Impairment of motor control |
| C | Impairment of cortex operation |
| S | Impairment of sound (speech) output |
| N | Impairment of sensory functions |
| Y | Impairment of memory access |
For example, a type of "MCY" indicates that motor control, cortex operation, and memory access are all impaired. At the conclusion of interference, "interference-state " is sent, with a trailing space.
The current unit name, including the prefix. Peripherals that can be interacted with by a user are encouraged to name themselves according to the full unit name plus a description in parentheses. This should be performed whenever a name message is sent, or immediately after receiving add-confirm based on the object name given in the name parameter of the listen() event. The name message is only sent when there is an update to this value.
For example, the chromatic communicator icon attached to an SXD unit named vi0let should take the unit's full name (SXD vi0let) and append " (icon)" to the end, resulting in the full name SXD vi0let (icon). This provides a consistent interface when interacting with a unit's peripherals. However, vi0let's battery does not need to rename itself, as it is not part of the unit's body and does not have any interactive features during regular use.
For example, the chromatic communicator icon attached to an SXD unit named vi0let should take the unit's full name (SXD vi0let) and append " (icon)" to the end, resulting in the full name SXD vi0let (icon). This provides a consistent interface when interacting with a unit's peripherals. However, vi0let's battery does not need to rename itself, as it is not part of the unit's body and does not have any interactive features during regular use.
Indicates the state of system main power. ("on" will be sent when the unit is powered on, and "off" when it is shut down.) No messages are sent when the unit enters or leaves auxiliary power mode. For various reasons, such as in response to the power-q message, this may be re-sent without the unit changing power state, so any devices that have boot-up or shut-down actions should store the current power state and verify that the power state has changed before taking action.
The unit's active persona is now <name>. Sent in response to persona-q, or when the persona changes. If no persona is active, then <name> is default.
Indicates the current level of power remaining, measured as a fraction of total capacity from 0.0 to 1.0. This is sent when the battery is connected, or whenever the integral percentage changes (e.g. 99% to 98%.) It can also be triggered manually with the power-q message.
The net rate of power consumption, measured in J/s. When power is received from an exterior source, this value is lessened, and is typically negative during charging.
Subsystem <SS> is either on (1) or off (0), where <SS> is a numeric value indicating:
These values were changed in Companion 8.4 to be more consistent. See practical breakdown here.
| subsystem | numeric value |
|---|---|
| VIDEO | 1 |
| AUDIO | 2 |
| MOVE | 4 |
| TELEPORT | 8 |
| RAPID | 16 |
| VOICE | 32 |
| MIND | 64 |
| PREAMP | 128 |
| POWER_AMP | 256 |
| RADIO_IN | 512 |
| RADIO_OUT | 1024 |
| GPS | 2048 |
| IDENTIFY | 4096 |
These values were changed in Companion 8.4 to be more consistent. See practical breakdown here.
See combat protocols.
The FTL subsystem is refreshing, and the unit will be unable to teleport for <time> more seconds. Sent every second.
See combat protocols.
The unit has entered or left the 'working' state, which indicates that it is currently performing a calculation or other processing task. Play appropriate lighting and sound effects. This is triggered automatically during vox filter processing, or manually, with the !working and !done cortex commands.