2025-07-29 19:54 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0000147Spring engineGeneralpublic2006-04-11 12:59
ReporterArgh 
Assigned To 
PrioritynormalSeveritytrivialReproducibilityalways
StatusclosedResolutionfixed 
Product Version 
Target VersionFixed in Version 
Summary0000147: Zero damage is not zero.
DescriptionSimple as that. Setting weapon damage to zero results in a damage of 1. Why, I dunno- my guess is that damage is being rounded up to prevent divide-by-zero somewhere, probably in the code for ImpulseFactor and the map deformation handler.

Big problem for mod developers, on a variety of levels. Why would we want a damage of zero?

1. Because then we can have units that are 100% completely immune to a category of weapon, via the ARMOR system.

2. We might want to have a "weapon" that is really just being used for a form of special-effect (which sounds weird, but since we don't have control over the particle system...).

3. We might want a weapon that *just* has an ImpulseFactor. No damage, just a push.
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0000150

Nemo (reporter)

Last edited: 2006-04-01 23:46

Well, a bit of a kludge for a fix: apparently spring accepts decimal value damages.

So, if you have a weapon that needs to do zero damage, have it do 0.0000000001hp of damage. Its close enough that nobody will notice the difference.

Edit: the problem with this is that impulsefactor will be badly broken. However, I *think* that impulsefactor works off of default damage, so if you tell it to do 0.0000000001 damage to the units/armor group, while leaving the default damage high, it should still work as just a push.

~0000157

NOiZE (reporter)

Already reported Mantis entry: 140
+Notes

-Issue History
Date Modified Username Field Change
2006-03-27 04:57 Argh New Issue
2006-04-01 23:44 Nemo Note Added: 0000150
2006-04-01 23:46 Nemo Note Edited: 0000150
2006-04-11 12:59 NOiZE Status new => closed
2006-04-11 12:59 NOiZE Note Added: 0000157
2006-04-11 12:59 NOiZE Resolution open => fixed
+Issue History