This is the home of my WoW Combat Log Parser. I've completely rewritten it for the 2.4 combat log changes. Also, it is no longer a web-hosted perl script, it is now a C++ console application.
There are several reasons for this change, the primary reason being performance. The combat log files can get pretty large, as most of you know. For example, I logged two hours of a BT raid with my guild and the resulting log file was over 200,000 lines long and about 30 MB. I wanted my parser to crunch the data as quickly as possible, and I think I was fairly successful. My parser was able to process this file in about one second.
Another nice thing about it is that it is cross platform. I am providing the source code below (if you choose to build it yourself, or want to make sure I'm not running a keylogger or anything) as well as select pre-built executables for Windows and Linux.
I'll be enhancing it as time allows. If you find this parser useful and would like to request a feature, feel free to email me.
Here is a sample of the current output format, I ran my parser with a "-s Bytor" argument to filter on my character as the source, there is some PvP data as well as some Black Temple data.
wowparse [-f filename] [-s sourcename] [-d destname]
| -f filename | allows you to specify the path to the file you wish to process, defaults to WoWCombatLog.txt in the current directory |
| -s sourcename | allows you to filter on a particular source (e.g., "-s Bytor" will only process damage and healing done BY player/NPC named Bytor) |
| -d destname | allows you to filter on a particular destination (e.g., "-d Bytor" will only process damage and healing done TO player/NPC named Bytor) |
The source code for my parser is here.
A 64-bit Linux executable can be found here.
A 32-bit Windows executable can be found here.
2008-10-13
- Initial release, limited to damage and healing amounts/averages