Since I think it's fairly solid now, I'll go ahead and add my own parser to the growing list in this thread: http://code.google.com/p/kparser/
Note on requirements: You need to have .NET 3.5 and SQLCE 3.5 installed. The readme.txt on the google site has the link addresses of where to download the installations from Microsoft if you need them.
While DirectParse is more summary-oriented, KParser is more details-oriented. The potential amount of data is huge. I've written a number of tab/plugins, and am hoping to solidify an API so others can do so as well if they wish. Unfortunately that comes at a price.
Report pages can get long, and if you have the tabs active while parsing it can get very resource intensive (the worst at the moment is the Buffs page), possibly slowing your system during a parse. I'm still working on ways to better optimize code speed without making the code itself overly cumbersome, however you can turn off tabs you don't want to view at the moment and they won't eat up time on an active parse. Note that the vast majority of the processing cost is in the datamining and display; the parsing itself is quite fast.
Side note: I know there exist some issues with using it on Vista/Vista x64, at least for reading from RAM, but I'm limited in what I can do there at the moment since I don't have that OS. Switch it to log-reading mode if RAM mode doesn't work. Also applicable in case a patch changes the base RAM address.
Comments welcome.
XI Wiki


