Inflict Bombing Damage On Capture

Hepps

Currently, there isn't any way to inflict bombing damage on captured infrastructure units.

Proposal
Create a new property to add bombing damage when a unit is captured:

<option name="whenCapturedSustainsDamage" value="10"/>

redrum

@hepps You could do something like whenCapturedChangesInto but without some sort of trigger, I don't think there is anyway to set bombing damage.

Hepps

@redrum Yah, that's what I thought.

since damaged and disabled units are in fact separate units... you can in theory use the "whenCapturedChangesinto"... but there is no mechanism to set the damage level.

Hepps

@redrum Would this be worthy of a feature request?

I mean would it be easy to add?

redrum

@hepps Should be doable though depends on the implementation. Options:

Probably the simplest thing would be to add another parameter to "whenCapturedChangeInto" like this so you could replace the existing infra unit with a new damaged one:
"fromPlayer:toPlayer:transferAttributes:unitType:numberOfUnits:bombingDamage"

<option name="whenCapturedChangesInto" value="any:any:true:factory:1:10"/>

You could instead create a new property like "whenCapturedSetBombingDamage":
"bombingDamage"

<option name="whenCapturedSetBombingDamage" value="10"/>

*** One potential issue is that if you actually change into multiple different types of units then setting bombing damage to all of them might not make sense. So you couldn't for instance have a factory change into 2 new infra units and have different bombing damages set for each of them.

Hepps

@redrum Well I'm not sure whether you would ever apply bombing damage to multiple different units. Normally I would think that you would have the original unit changing into a damaged version of itself.

But would it work just applying the second of your examples?

For example if a infrastructure unit is already set to is capture-able...

then you set it to....

Would there need to be other attachments? Or would the engine automatically interpret the data and determine whether the unit needs to be changed into a damaged or disabled version of itself?

redrum

@hepps That the idea similar to how whenCapturedChangesInto works. I think the question is should whenCapturedChangesInto and whenCapturedSetBombingDamage be able to work together? I think if you apply them in that order than I could make it work at least for most cases.

Hepps

@redrum Yes. But what I was asking is.... If you just eliminated the "whenCapturedChangesinto".

Because if you set a unit to "isinfrastructure" then the unit is capturable...

What I'm asking is would the engine automatically change a unit into the damaged version of itself if .... "whenCapturedSetBombingDamage" is applied.

The reason I ask is that if you want a unit to turn into something (or somethings) else... then you probably don't need to apply damage to those.

redrum

@hepps Yeah, it would make sure to change to the _hit image if necessary and disable if bombing damage is reaches max operational damage.

I was thinking more along the lines if say you wanted a Factory to change into 2 materials and have those materials start with an amount of bombing damage. Essentially, whether we should in some way support using both "whenCapturedChangesInto" and "whenCapturedSetBombingDamage" on the same unit.

Hepps

@redrum Well I hadn't pondered a combination effect. Not sure why you would want to do both at the same time. Feel like if you wanted something to be damaged.... it wouldn't then change into a different damaged unit or units.

redrum

@hepps Yeah, I think just focusing on being able to inflict bombing damage on capture first.

The only remaining question I have is:

Should the bombing damage amount be "set" or "added"? Example: I have a factory with 2 damage already that is then captured, should this property add say 5 more damage for a total of 7 damage or set the damage to 5?

Hepps

@redrum Additive for sure.

Hepps

@hepps Oooooooo moved to Feature Request.... and on that day the Grinch's pants grew 3 sizes more tight.

redrum

@hepps And even added to the list. If only the list didn't grow faster than things were checked off...

Hepps

@redrum To quote what a somewhat wise man said to me not to long ago...

"All depends how dedicated you are and how late you are willing to stay up :)"

prastle

@hepps @redrum this reminds me of the pre release list It grows and grows and grows

Hepps

@prastle As does the rich tapestry that is our game experience.

redrum

Thinking the new property should be called: whenCapturedSustainsDamage

Alternatives:
damagedWhenCaptured
whenCapturedAddsDamage
whenCapturedTakesDamage
whenCapturedReceivesDamage

Hepps

@redrum "Sustains" is the clearest wording that cannot really be misinterpreted as meaning anything else.