Restricted Bombard Casualties Firing Back

[DanVanAtta]

Reproduction Steps

1. open attached save game
2. click 'done' to end purchase turn
3. say 'yes' for units to bombard, battle will then auto-start
4. notice in the first round of combat that the defender fires back

Expected: defender should not fire back, bombard casualty should be removed immediately

Attach a Save Game

restricted-bombard-firing-back.tsvg.zip

Engine Version

Engine Version: 2.6 @ e1cf9ee

Is there anything else we should know?

[stale]

I noticed there has not been much activity on this issue. Please check this issue and close it if it no longer applies.
Otherwise to help move this issue move forward, please add a comment summarizing any further actions that need to be taken in order to resolve this issue.

[asvitkine]

I actually get an NPE with the above saved game. Will investigate.

[Cernelius]

For general information, this is also related to an old problem.

V1 (Classic) being the default for TripleA, naval bombard casualties should fire back as default (like if I make a map with no properties at all in the game XML file), whereas TripleA has naval bombard casualties fire back disallowed as default and a property for allowing them to fire back (which is the exact opposite of how it should be).

For general information, naval bombard casualties fire back in v1 as well as in all rule-sets from v3 onwards and do not fire back in v2 only.

[Cernelius]

I actually get an NPE with the above saved game. Will investigate.

Same for me. I reported it here:
#11784