This section is subject to change in the near future as the space mechanics are revised. This document will not go into great detail on designing specs; that's left as an exercise to the reader. Your best bet is to start with the sample objects on the support MUX (see the README file), and tweak various fields to improve or weaken certain systems. This section outlines the attributes that need to be set on consoles and space objects.

To configure an object, one must set configuration attributes (prefixed with CF_) that should not change in an object's lifetime; status attributes (prefixed with ST_) that may change in an object's lifetime; and status flags (stored in ST_FLAGS or ST_SHIPFLAGS) that can also change in an object's lifetime, though not very frequently.

Note that these fields are only read when an object is added to space (except for flags which may be set or reset while an object is in space). At this time, the engine reads the DB object, ensures that enough information is present, then creates a new space object. When the space object is removed from space for whatever reason, or requested to save its state, it will record ST_STARTPOS, the damage registers, and ST_DOCKED_AT, ST_ODOMETER and ST_TIME_ACTIVE if the object is a ship.

The following sections detail what is required to configure the various types of objects.

I.1: Generic Objects

• I.1.1: Attributes
• I.1.2: Flags

• I.2.1: Attributes
• I.2.2: Flags
• I.2.3: Damage Locations