Correct, there is alot of the code that I could not access in HL, and I don't intend to. And I'm not entirely sure how I would ensure parsing order in all the scripting (though making something that can parse the HL scripting language is something I've done on far more complex languages before, getting it to work is another thing). What Mathias suggested is more in the vein of where I was heading, parsing the language into a format that can be read into an application I create, that then runs a tactical console. I don't intend to run a true representation of the characters in HL, as that product does a fine enough job for that, I just want to make certain combat related issues work as expected or intended.
Now, that brings up another point. I could make an application that works hand in hand with HLs tactical console, an effect tracker, a duration tracker, spells, but I would need to know alot more about what is going on under the hood. Since HL is a proprietary property, I don't expect that to happen, so I'm left dreaming up this possible 3rd party application. I haven't decided to do it just yet, because I'm not entirely sure how much I have bitten off, so to say, I'm just in the software planning stage. When and if I feel like I can accomplish this, I will, but until then, this is just a thought exercise for me.
As for parsing the files themselves, it's not that difficult if you understand XML and XPath technology, however, I will still have to know what tags I am looking for. That will take some time to figure out, as I am sure there are many tags that are not in much use, and there are tags that are obsolete (but still hang around in legacy mode), and there are tags in some systems that are not in others (the difference in tags between PF and d20 along is an ever-widening one). And that's another issue altogether, because though there is much standardization in the XML structure, its 3rd party flexibility and efficiency are extremely limited the more it deviates from system to system. Which is why CM is strictly PF based.