>>11107
Another thought. Have you considered implementing changes slowly instead of all at once?

Maybe update one thing at a time, see if it breaks anything, and then revert it if it breaks anything? Basically agile development? I don't know. Whatever works best