HS-SYSTEMS
From HSpace
HS-SYSTEMS
Engineering systems in HSpace are very conveniently modeled to provide the highest level of flexibility. Objects, such as ships, can often be very different from one another, and thus there is no way to predict which engineering systems will be present on a given space object. For all of our examples, we will refer to ships, since they are most likely to possess systems.
What is an engineering system? An engineering system is really any "system" on the ship that helps it function. This may be a computer, a sensor array, a fuel management system, shields, etc. The list is nearly endless, though fortunately it's not! Systems can be given power, or they may provide power, such as with a ship's reactor. Systems may be stressed, and how easily they stress depends on how tolerant they are. Each engineering system at least possesses the following attributes:
- OPTIMAL POWER
- TOLERANCE
- STRESS
- DAMAGE
- CURRENT POWER
- NAME
- VISIBLE
"Visible" systems are those systems that you can interact with -- you can transfer power to and from it. Not all systems are visible, such as with an internal fuel management system. It manages itself and doesn't let you touch it.
A ship may possess from none to many engineering systems, depending on how functional that ship is. For example, it may have jump drives, allowing it to travel at faster than light (FTL) speeds. It may, or may not, have engines, allowing it to move at sublight speeds. Many systems are included in HSpace that can be added to some HSpace objects, such as ships.
See also: @space/addsysclass, @space/setsysclass, @space/sysset, HS-SYSTEM-TYPES, HS-SYSTEM-ATTRS
