Allows defining whether passengers of an OpenTopped transport unit can fire when it is affected by a locomotor warhead

[DeathFishAtEase]

Allow using OpenTopped.AllowFiringIfDeactivated=false for the case where a transport unit is being attacked by a weapon that uses a warhead with IsLocomotor=true.

Use OpenTopped.AllowFiringIfAttackedByLocomotor to control whether the passengers of a non-building transport unit can fire when the unit is being attacked by a weapon whose warhead has IsLocomotor=true

[github-actions]

Nightly build for this pull request:

• compiled-dll-b5dea82d11f5af2538bf8aeb85075f2c20125334.zip
  These artifacts will expire in 90 days and will not be available for download after that time.

This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build.

[phoboscn-bot]

To Chinese users:
This pull request has been mentioned on Phobos CN. There might be relevant details there:

致中文用户：
此拉取请求已在 Phobos CN 上被提及。那里可能有相关详细信息：

https://www.phoboscn.top/t/topic/375/1

[DeathFishAtEase]

Tested by https://www.phoboscn.top/t/topic/375/3

[Coronia]

I'm not sure if this needs a standalone tag, since locomotor change is a different scenario from EMP/deactivated

[DeathFishAtEase]

I'm not sure if this needs a standalone tag, since locomotor change is a different scenario from EMP/deactivated

Considering the accuracy issue of the INI flag name, it is indeed best to add a separate flag and allow setting a global default value to change the original behavior, rather than simply treating both as a deactivated state to handle them equivalently.

[Starkku]

Realistically the locomotor WH specifically disabling firing could be considered a special case of 'deactivation' but semantically I suppose it is clearer to split the two because of, as you put it, the 'accuracy issues' with the INI key name.