News

[1.0.3.3] Minor cost progression error for sensor components

Posted on Saturday, June 6, 2015

In the latest update the sensors were corrected to more sensible values, however there are some cost progression anomalies.

The current overview:

  Stats   Deltas
  Build Cost Mass Range Maintenance Immune to Nebula   BC/mass BC/Range Range/Mass MC/Mass MC/Range
Navigational Sensors 13,00 8,00 1,00 0,25 0,00   1,63 13,00 0,13 0,03 0,25
Intersteller Sensors 23,00 9,00 2,00 0,25 0,00   2,56 11,50 0,22 0,03 0,13
Sensor Array 41,00 10,00 3,00 0,50 0,00   4,10 13,67 0,30 0,05 0,17
Field Detectors 71,00 12,00 4,00 0,75 0,00   5,92 17,75 0,33 0,06 0,19
Subspace Sensor 123,00 14,00 5,00 1,25 1,00   8,79 24,60 0,36 0,09 0,25

But there is an easy fix:

  Stats   Deltas
  Build Cost Mass Range Maintenance Immune to Nebula   BC/mass BC/Range Range/Mass MC/Mass MC/Range
Navigational Sensors 13,00 8,00 1,00 0,10 0,00   1,63 13,00 0,13 0,01 0,10
Intersteller Sensors 27,00 9,00 2,00 0,25 0,00   3,00 13,50 0,22 0,03 0,13
Sensor Array 41,00 10,00 3,00 0,50 0,00   4,10 13,67 0,30 0,05 0,17
Field Detectors 71,00 12,00 4,00 0,75 0,00   5,92 17,75 0,33 0,06 0,19
Subspace Sensor 123,00 14,00 5,00 1,25 1,00   8,79 24,60 0,36 0,09 0,25

Fix in the xml

For the NavigationalSensors change the Value for Maintenance from 0.25 to 0.1

<Stats>
<EffectType>Maintenance</EffectType>
<Target>
<TargetType>Ship</TargetType>
</Target>
<BonusType>Flat</BonusType>
<Value>0.1</Value>
</Stats>

For the InterstellerSensors change the Value for SensorRangeManufacturingCost from 23 to 27:

<Stats>
<EffectType>SensorRangeManufacturingCost</EffectType>
<Scope>Queue</Scope>
<Target>
<TargetType>Ship</TargetType>
</Target>
<BonusType>Flat</BonusType>
<Value>27</Value>