So I've got basic .GAME support for NES happening. Unfortunately it's in a very simple state right now because I don't want to waste too much time on getting it perfect until I've done all the research about mapper requirements. I'll likely put my feelers out to the NES gurus and see what they think.
I spent most of today going over my NES core getting it in a more presentable way. My coding style usually revolves around getting something working as quickly as possible. I rarely plan out my code, after doing it for close to 12 years commercially it's like what building a brick house is to a labourer. But going back over your code and making it nice and neat is important.
It may surprise a lot of you but when you emulate anything a lot of the knowledge dissipates fairly quickly. Your brain is good at knowing what it doesn't need to know, and the VRAM timing of a machine is one of them I guess. So having good comments and clean well desigend code helps a lot, especially in emulators, especially when you have new research in there.
Back when I first started coding, after about a week any project started to be a real pain to work on, and I lost motivation very quickly after that point. It is why there are so many unfinished works on sourceforge and things of this nature in my opinion. Still, doing badly designed things is part and parcel of becoming a better programmer so it's one of those things we have to live with.
Today RetroCopy involves over 4 different and rather large projects, totaling close to a million lines of code, most of it written by one person, myself. Going from the spaghetti western type coding style all those years ago to RetroCopy is almost a quantum leap. It amazes even me.