# 'Shattering impact' doesn't apply to enemies who aren't directly hit

**URL:** <https://forums.fatsharkgames.com/t/shattering-impact-doesnt-apply-to-enemies-who-arent-directly-hit/71028>\
**Category:** Bugs\
**Tags:** acknowledged\
**Created:** [December 24, 2022, 8:40am UTC](https://forums.fatsharkgames.com/t/shattering-impact-doesnt-apply-to-enemies-who-arent-directly-hit/71028 "2022-12-24T08:40:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![gpkgpk](https://dub1.discourse-cdn.com/flex013/user_avatar/forums.fatsharkgames.com/gpkgpk/32/119406_2.png) [@gpkgpk](https://forums.fatsharkgames.com/u/gpkgpk)\
**Post date:** [January 2, 2023, 7:33am UTC](https://forums.fatsharkgames.com/t/shattering-impact-doesnt-apply-to-enemies-who-arent-directly-hit/71028/2 "2023-01-02T07:33:16Z")

</div>

I’m perplexed why stuff that’s LUA script/table(data) driven isn’t hotfixed a la BL2.

Looking at the LUA files we see `templates.weapon_trait_bespoke_ogryn_thumper_p2_targets_receive_rending_debuff.check_proc_func = CheckProcFunctions.on_ranged_hit`  
for the Rumbler.

Which is simply

```auto
CheckProcFunctions.on_ranged_hit = function (params)
	return params.attack_type == attack_types.ranged
end

```

There’s also a separate

```auto
CheckProcFunctions.on_explosion_hit = function (params)
	return params.attack_type == attack_types.explosion
end

```

There are other functions ANDing stuff, like ranged crits.  
Why is there no compound  
`return (params.attack_type == attack_types.ranged OR params.attack_type == attack_types.explosion)`  
for the Rumbler Shattering Impact?

Seems like silly oversights like this that greatly affect gameplay could and should be hotfixed over-the-air without official patches.

---

_[View the full topic](https://forums.fatsharkgames.com/t/shattering-impact-doesnt-apply-to-enemies-who-arent-directly-hit/71028)._