Hi RunGeeGeeRun,
We believe the crashings will reduce after we use a different code protection software, which we'll testing at the moment.
It is true that if you restart the program or reload the triggers, their states will be reset. But you can use two workarounds for such situations:
1. For those constants that need to keep their values in between program sessions, you can set "remember last value" instead of "start with initial value".
2. You can prevent triggers from placing double bets by actually checking if there is already a bet in the market:
Market's Number of Matched/Unmatched Back/Lay bets is equal to 0
or use a similar condition that will return false if the trigger has already placed some bet. Of course it does not apply to the situations where you use conditions starting with "Trigger XY number of runs".