Command: *register:

A Device may use this command to notify the Core that it would like to serve a particular role with respect to that Core that requires the Core to know it is doing so. For example, a battery meter needs to be kept informed of the Core's charge level, but a Core should not announce its charge level as often as it might be appropriate to update the meter (to avoid unnecessary lag in the sim).

Usable in: Commands

Parameters

 * type
 * The type of device, which will indicate its role.


 * method
 * See Universal Parameters, but most Cores will require it for this command, so it is best to include it.


 * trust
 * A string designed to prove to the Core that this Device is created by a trusted creator. See trust script.


 * subscribe
 * A list of Core variables (settings) whose value the Device would like to be kept informed of. The Core should reply immediately with and other messages listing the current values of those variables, and should send the Device another message when any of those variables changes. The special values "*restraints", "*control", and "*controldefs" may be used to provoke, {{DL|control}, and {{DL|controldefs}, respectively.

Response(s) Expected
Based on subscribe, potentially any or all of:
 * (if any state variables are requested)
 * (if "restraints" is specified)
 * (if "controls" is specified)
 * (if "controldefs" is specified)

Or in case of failure,.

Implementation Details: ACS
Minimum Level:

Other constraints: