SOLVED!Update, apparently it was the software. The lower the minimum time between impacts and the impact debouncing time settings, the more likely it is to bug and not register clashes properly. This is probably due to the saber detecting too many impacts and trying to show them all at once, bugging itself just after. When I set these two to near zero and tried to ignite the saber, it tried to show the ignition sound, but it was interrupted by many clashing sounds and a lot of flashing all mixed together and didn't show flash on clash again after that.
If you ever have this problem, raise the settings of these two a bit, do not let despair take over you!