[TF2] Fixes for Exorcism spell not properly triggering

[ThatBapGuy]

Within TF2, the Exorcism spell does not apply to any sentry kills when it is on the wrench. This PR fixes this issue alongside fixing the wrangler spells. This fix also applies to the sentry rockets.

The Exorcism spell also does not properly apply to shields within TF2. This is also fixed within this PR.

Fixes ValveSoftware/Source-1-Games#5018
Fixes ValveSoftware/Source-1-Games#4930

[FrozenDragon0]

Reckon you could fix Exorcism on stickybomb launchers and shields?

[ThatBapGuy]

Reckon you could fix Exorcism on stickybomb launchers and shields?

Shields I believe I fixed, I just didn’t push it cause I haven’t been able to track down a spelled shield owner to test it.

The stickybomb launchers I have no clue on what’s happening. It’s something happening with the particle being dispatched as even just having the particles being spawned on damage doesn’t work with the weapon. Although I still am digging into that issue.

[ALIEN31ITA]

Replying to #1555 (comment)

if i am not wrong you can just apply the spell to your or a bot weapon via Vscript, it's an attribute.

[ThatBapGuy]

Replying to #1555 (comment)

I've actually never tinkered with VScript yet. Will look into it

[FrozenDragon0]

Replying to #1555 (comment)

An easier solution is to use a modified item schema within the TF2 SDK and add the Exorcism spell as an attribute to any shield.

[ThatBapGuy]

Replying to #1555 (comment)

I entirely forgot that the item schema was easily modifiable lmfao. I ended up adding the shield fixes.

[FrozenDragon0]

Replying to #1555 (comment)

Great, now I wonder if we could ping Eric Smith to get these changes added into the vanilla game.

[ThatBapGuy]

Ok so, I have dug as deep as I can into the Stickybomb Launcher Exorcism issues, I do not believe I will be able to fix the issue with that weapon with this PR because from everything I have tested, it seems like it should work.

From the testing I have done (relocating the particle effect code to on damage and other functions) the issue appears to stem from somewhere in the DispatchParticleEffect function if anyone wants to dig deeper into that issue. I could be entirely wrong with that though.