It will be done when it's done. I can't really be more specific than that in terms of actual time. I can't overstate enough that while it mostly looks the same it is essentially a new program on the inside. There are approximately 20,000 lines of code and a large percentage of that has been rewritten over the last 2 months. To make matters worse, there were several errors in how prior versions of GamParse calculated things which means that in many cases it can NOT be used as a reference to verify that it is working correctly. This means I have to manually examine logs and compare that to the parser output to make sure it is correct. Just because GamParse spits out a number and doesn't give an error message does NOT mean it spit out the *correct* number. And of course there has been the ever-present issue of the majority of the old code not having comments to explain exactly what it does and (more importantly) *why* it does it. In several instances already I've either removed or changed older code and then had to later come back and either revert the changes or make additional changes because I found out the code served an important purpose that wasn't obvious and wasn't explained.