View Issue Details

IDProjectCategoryView StatusLast Update
0001973FSSCPtablespublic2010-02-20 18:04
ReporterFUBAR-BDHR Assigned ToWanderer  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version3.6.11 
Summary0001973: $Shockwave Damage Type: overrides $Damage Type: if $Shockwave Speed: > 0
DescriptionAttempting to make a secondary weapon that has different armor types for the impact and shockwave damage. $Damage is set at 65000, $Damage Type: is Nuke, it has an inner and outer radius and $Shockwave Damage Type is Shockwave. Armor table is set up with Nuke being one value and Shockwave being another dependent on the ships armor. Shockwave is usually a fraction like .001. Problem is the weapon uses the Shockwave damage factor for the impact damage as well as the shockwave. Removing $Shockwave Damage Type: entry results in normal expected damage based on $Damage Type and the ships armor. Setting the Shockwae Speed: to 0 but leaving the inner and outer radius actually increases the damage done by the weapon. Guessing it's doing the 65k * $Damage Type: + 65k * $Shockwave Damage Type:. Adding a $Shockwave Damage: value doesn't change the behavior.
TagsNo tags attached.

Activities

Wanderer

2009-08-28 13:49

developer   ~0011167

Fix for this has been added to r5548. '$Flags: ( "ignore subsystem armor" )' after the last 'armor/damage' pair (and their calculations) just before the '#end' if that armor entry. If that flag has been set to the ship's armor type then it should no longer allow damage to pass via the subsystems but instead force the hull armor even against that damage.

Please report if the issue has been fixed with this addition.

Wanderer

2010-02-20 18:04

developer   ~0011704

No feedback.. issue assumed to be resolved

Issue History

Date Modified Username Field Change
2009-08-08 19:51 FUBAR-BDHR New Issue
2009-08-28 13:45 Wanderer Status new => assigned
2009-08-28 13:45 Wanderer Assigned To => Wanderer
2009-08-28 13:49 Wanderer Note Added: 0011167
2009-08-28 13:49 Wanderer Status assigned => feedback
2010-02-20 18:04 Wanderer Note Added: 0011704
2010-02-20 18:04 Wanderer Status feedback => resolved
2010-02-20 18:04 Wanderer Resolution open => fixed