NS

Name	Radiation Generator
MSRP	L$ 250
XVS server	xvendor:0
Permissions	copy, modify
Land impact	5
Attachment point	—
Function	ACS Interference Generator
SKU	16-0233-F
Requirements	none
First release	XXXX
Latest release	—
Related products	TBD

# radiation config file 1.0
#
# based on the weather zone configuration format; zones are specified by key (keys must be unique; sorry)
#
#  - shape: this defines how radiation operates
#
#    for spherical zones, use 'point' shape
#    for volumetric zones, use 'volume' shape (anything inside the object, presuming the object is a phantom, invisible rectangular prism)
#
#  - radius ('point' shape only): defines the distance within which someone must be to experience interference; must be specified AFTER shape
#
#  - type: a combination of the letters M, C, S, N, Y indicating the type of subsystems affected by the radiation
#
#    M: Motors
#    C: Cortex
#    S: Speech
#    N: seNsory (video + hearing)
#    Y: memorY (identity + GPS)
#
#  - intensity: wattage of the field; 1 is enough to block subsystems. Smaller values (e.g. 0.5) are useful for triggering Geiger counters. As of this writing, any intensity value greater than one 1 has the same effect on units as an intensity of 1, but this may change in the future. However, higher intensities drain shields faster; see below.
#
#  - duration: how long the interference will last, in seconds; must be integer
#
#  - interval (defaults to (duration - 1) if not specified): how often to send out radiation pulses; must be integer
#
# Shields: every time a pulse hits the unit, (intensity * duration) joules are drained from the shield, so a high-intensity field will drain shields faster
#
# Since interference is an ACS protocol, the radiation generator uses the ACS protocol to detect units that can be affected by it. This includes ATOS/CX units and ACS CCUs. As a sim owner you can expect shock and anger from ACS constructs who have, until now, never had to deal with the existence of interference because so few things make use of it other than NS products.
#
# Overlapping rad zones: try to avoid these if they have different types or intensities, as you'll create a LOT of 'fault detected/resolved' spam. The controller can only accept one type/intensity from a given source at a time, and in this case the source is always the server (to avoid the lag caused by having each zone manage its own occupants).
#

# example zone definition: a cube around the object will be filled with Cortex and memorY interference
zone c0a7d04e-e1d9-3c2f-6eca-f9be65367d19
shape volume
type CY
intensity 4
duration 6
interval 2

# this second zone is a point source, so anything within 5 m of its center will be unable to think, speak, see, or hear
zone 45fb1b99-b1c3-89bd-a113-8952c8cb670d
shape point
radius 5
type CSN
intensity 4
duration 6
interval 2