# CLASH\_THRESHOLD\_G setting not "working" **URL:** \ **Category:** ProffieOS\ **Created:** [February 16, 2024, 5:07pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883 "2024-02-16T17:07:53Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\ **Post date:** [February 16, 2024, 7:12pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/2 "2024-02-16T19:12:52Z")
See this thread maybe? > [@Clash Settings and Questions](https://crucible.hubbe.net/t/clash-settings-and-questions/4651): > > Yo, it’s me again XD This time I want to take a more in depth look into the changes that’ve been made to Clashes through the years. My stock saber has a relatively low clash threshold, so that phantom clashes (clashes where nothing is touching the saber) happen if you’re trying to make them happen. Now, I happen to LIKE these phantom clashes, especially where you can set them off if you’re practicing blocking movements and such. Full disclosure, I have NO idea what my stock settings are, I never got the manufacturer’s config, just a similar one that works, so I don’t know what the original settings are. Fast Forwards to OS7, and the clash detection is WAY different. Better in some ways and worse in others (IMO! Fett and Fred are doing amazing work always :D) but I’ve messed around with all sorts of clash thresholds and top config defines, but nothing seems to be able to replicate these phantom clashes I like. I’ve noticed that there’s nearly no way to make a clash happen mid-swing, which seems very intentional, but… Is there a way to change this? How could one go about messing with the clash detection on a more fundamental level? Any thoughts or ideas…? --- _[View the full topic](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883)._