Fixes #4337 - Fix duplicate onClientExplosion events for satchel #4340
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.
Fixes : #4337 , Tested.
I removed the manual event call from DestroySatchelCharges and let only the explosion manager handle the event firing, ensuring satchel explosions behave consistently with other explosives like grenades and eliminating the duplicate event triggers.
Before:
❌ Event was being triggered twice due to both manual and automatic invocation.
After:
✅ Now triggered only once as expected, preventing duplicate event calls.
Also Tested all Explosion types :