To the impartial observer, the process appears to be a guy staring at the screen for a long time without typing much, and swearing occasionally. Really most of what I do is make documentation on how Morrowind works. Run it through a debugger, change one thing in Morrowind and note what functions are called, and what data structures change. Then there's a lot of logical deduction to guess the side effects of each function, and exactly what the data is supposed to represent. Once everything is explained in maximum detail then it is usually clear what to change. I rely on a solid base of knowledge on how things are supposed to work to be able to spot mistakes.
Haha, don't mind me, but I do program. Python, Java, a little C, and a lot of web dev with PHP, AJAX, and all sorts of other stuff, using abstraction techniques.
So I'm not completely clueless. Just aware of how much I don't know.
I am
very curious as to how you made this. All I can gather, is that your methods sound a lot like some of the things I read about making trainers and cracks. (No I don't.)
When you have the time, please, point me towards something that would help me learn how to "repair the cogs of Morrowind" as you are doing
(I will be doing my own research soon as I am done with exams. Trying to keep my information mooching at a minimum.)