Fix ApplyMultiDamage duplicated call on MultiDamage routine #946
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This seems redundant but avoids an API call from ApplyMultiDamage at the first AddMultiDamage call since there's no pEntity, forcing a call to this function without success. This expects to straighten subplugin's hooks to work as expected since ApplyMultiDamage should be called at the end of the MultiDamage routine, or when other entity is hit (penetration or shotgun spread).
In case of a weapon with no penetration (usp, for example) a simple FireBullets3 call will result in: