Allow warhead to only affect invoker

[DeathFishAtEase]

• In the past, modders used many methods such as Dropping and extremely small CellSpread to prevent a weapon fired by a unit from affecting others, thereby achieving complex combination logic. However, existing methods merely reduced the range of affected objects through various means. Now, you can directly use the following flag to check whether the victim is the unit itself:
  • AffectsInvokerOnly can be used to make the affected object only the unit itself.
  • AffectsInvokerOnly.Reverse can be used to exclude the unit from the affected objects.
  • AffectsInvokerOnly.IgnoreInvokerState can be used to determine whether to consistently avoid affecting other objects regardless of the unit's state.

[CombatDamage]
AffectsInvokerOnly.IgnoreInvokerState=true  ; boolean

[SOMEWARHEAD]                               ; WarheadType
AffectsInvokerOnly=false                    ; boolean
AffectsInvokerOnly.Reverse=false            ; boolean
AffectsInvokerOnly.IgnoreInvokerState=      ; boolean, default to [CombatDamage] -> AffectsInvokerOnly.IgnoreInvokerState

Tip

If you have enabled ApplyPerTargetEffectsOnDetonate to make affects handling completely follow damage propagation, then most of the time you can just use DamageSelf and AllowDamageOnSelf without needing AffectsInvokerOnly.Reverse.

[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/541/1

[github-actions]

Nightly build for this pull request:

• compiled-dll-859f43807a19c7237a979f14d208a6a139b95177.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.

[Otamaa]

Just an reminder , if you do keep old invoker pointer always make sure that is really valid invoker , because in the middle of damaging/detonating state the invoker itself may get killed or deleted and need to be cleanup , if you keep it like this that mean you will potentially referencing an dangling pointer.

[TaranDahl]

Just an reminder , if you do keep old invoker pointer always make sure that is really valid invoker , because in the middle of damaging/detonating state the invoker itself may get killed or deleted and need to be cleanup , if you keep it like this that mean you will potentially referencing an dangling pointer.

From my understanding, this step is unnecessary.
IIRC UnInit will be invoked when an entity dies from damage. It marks the entity with IsAlive=false and adds it to the pending deletion list instead of deleting it immediately. All such entities will be cleaned up collectively at the end of the frame.