Comment 17 for bug 895180

Revision history for this message
WoRmINaToR (worminator) wrote :

(in light of the recent duplicate, I thought I might...)

{quote}unless =no was a special value which dissabled the cloaking logic. But fiiine, if yoou want to overcomplicate it... {un-quote}

nonsense. Your idea to change the data type of an already existing flag and then force it to take exceptions is unnecessarily complex. As marshall suggested, starting on a fresh block of code would be much more efficient.

And the more I look at it, the more sense Tesla's idea seems to be making...

Having strictly and individually defined types of stealth with their own sounds and behaviors is a nice idea, actually. The only thing I would change is that I definitely think the "Can be detected by" part for the stealth types should be defined by a "SensorsType=" flag on the individual unit, instead of being defined by the stealth type definition (wow, I just used 4 words in a single sentence beginning with 'defin-'!).