Jump to download
Jump to release notes
Latest News:
Tuesday May 20th, 2008:
So it seems I got a new computer and am experiencing some access violation when it's running in auto archive mode...not sure where it's occuring. I put in some code a few revisions ago to pick up unhandled exceptions and log them, but I'm not seeing it log it, and of course, it doesn't happen from the debugger...so if you have it happen please let me know and send me any error logs that are written to the program's directory.
I also found an interesting bug, well more or less a small issue with the way the zip files are created. Seems it will create an empty zip file if you time/date stamp the zip file filenames and there are no files to zip up lol. I'll be fixing that soon and releasing a small patch.
I have some code put in for checking for updates from the main site, but I haven't really implemented it on my webserver yet, so that's something else coming as well.
The main website will be having some of the features of the program like mob locator, and some other stuff in the future based on data I've collected from my own logs. I may let people submit their item and kill data as well through the program. I'm just starting on the project so it will be quite a bit of work, I wouldn't expect to see it anytime in the next few months.
I will also be adding a feature to have the program go through all of your archived log files and reprocess the data, as well as migration tools for migrating your data from the different storage methods provided, just in case you change your mind on database platforms.
I still need to include a new BDE configuration for larger tables and a little bit of code to restructure your existing paradox tables to handle up to 1 gig worth of data. Currently all tables are maxed at 256mb of data, due to a block size of 2048 bytes. This ONLY affects local storage (paradox tables) the other platforms are pretty much unaffected by this. I found that just running the storage to paradox for chat data will blow out the limit for a 2048 blocksize within a month LOL.
Tuesday May 6th, 2008:
Raid stat info has been released as well as a number of bug fixes.
Monday March 24th, 2008:
Mob locator is now complete and ready for use. (Tools > Quick Search > Mob Locator) If you are going to use any other method for looking up stuff other than a freshly loaded log file you will have to load a new one and store the data in order to execute the procedures for calculating unique locations. When storing mob data to permanent databases, a new table is created called "uniquekill". I decided to actually store them instead of recalculate the unique locations each time you open the search. The longer you have been storing the data in your log files to databases, the longer the routine would take, so in order for people to be able to use it without waiting for a long involved process of picking out the unique locations for mobs, it's done when you store the data from a log file to any one of the database platforms the program supports. During the storage routine, it will only update the zones that are present in the current log file, unless it is the first time it's being run. In order to build the initial set of data for usage with the program, you will either have to store a log file or just let the next archival process take care of it for you (if you chose to store the data from logs when archiving).
I've also added the ability to change the database options from most of the windows that are used for accessing data stored in any of the database platforms supported in the program.
I found one limitation with the local storage method at the moment. It seems the configuration for the BDE I've been distributing has the block size on the tables set to 2048. This means the max size of a table is 256mb. I will be updating the configuration to be able to utilize 1gig tables, but I need to write something to go through and restructure your existing tables with a 16,384 byte block size. I might even just include it as a separate little utility, as well as a table repair/packing utility. MySQL and PostgreSQL users are not affected by any of this.
There have been a few changes to the structure of some tables. MySQL floating-point fields have been changed from a floating point decimal to a fixed decimal with 2 places. This was done on coordinate storage since some mathematical functions in MySQL will treat a float as a double instead, which wasn't working out so well when calculating the distance between coordinates. A few character fields have been widened, mostly just zone names. More uniformity across tables that store the same types of information has been looked at. Primarily something that stores a zone name will have the same length across all tables instead of varying between 40 and 50 characters.
I've found some random bugs here and there and squished them. I also improved the speed of the PostgreSQL moving of text files to the server. I wasn't able to do it previously using the methods in their API so that the server did not have to have physical access to the file. That has been taken care of, now instead of executing a number of insert statements, it's loaded and transmitted across the database session. The insert statements would actually hang the program if you got in excess of 5,000 insert statements due to the way the query components handle string lists.
Next thing coming up is an easy raid stat generator. It basically will format out some information like raid participants listed with /whoraid and loot for a particular zone. It will output a bunch of text for making it easy to post on your guild website etc.
EQ2 Log Processor is an application designed to extract various bits of data from your EverQuest 2 log files. Currently it will separate chat, mob data (kill locations, names, zones), items, loot data (dropped by what mob/where), location commands (using /loc from in game), mail, sales, and system messages.
Future releases will include a combat parser.
It's a work in progress, so some of the functionality isn't there yet, but it does have a help file (not completely finished) and a number of utilities built in, and everything it does can get dumped to MS Excel (if you have Excel installed). Just drag and drop your log file on it and off you go.
If anyone decides to use it and has any issues with it please feel free to let me know and I'll fix em for you. There will be some minor bugs here and there I'm sure, I'm still finding some and it's almost been a year in development.
I work on it an hour a day, twice a day (during my commute to and from work) 5 days a week so I'm constantly adding/fixing things. Since it still has a lot more work. Suggestions and comments are always welcome in addition to bug reports.
The chat processing will let you filter the output based on various criteria and will also let you format the output in various ways. If you are lost with any part of it, just press F1 and if the help doesn't explain something sufficiently let me know and I'll answer your questions and make a note to update the help to address the lack of clarity.
Right now this is mainly geared towards a tool to be used in setting up and maintaining data on fansites, but works quite well for everyday use.
It will also archive your logs and organize them in zip files based on the options you select for it.
There is no installation necessary, just unzip where you want it and run the executable. I can't guarantee it will work under Vista, it should, but there is the possibility some of it won't.
It was written in Delphi 5 (object oriented pascal) and the local storage platform utilizes Paradox 7 tables. The functionality of SQL is quite limited when querying the local tables, so if you want expanded functionality I would recommend using MySQL or PostgreSQL at the moment. I built it for MySQL 5, I have not tested it on releases prior to that. PostgreSQL support is built for PostgreSQL 8, but will probably work on earlier versions as well.
Information and Tutorials:
General Usage
Walkthrough Creation
Chat Filtering
No special installer required, just unzip to wherever you want the program
to reside and run the executable. In order for the program to operate you must
have read/write access to the directory you place the software in. You must
also have read/write access to the registry under HKEY_CURRENT_USER\Software.
Latest version of executable only: (build: 1.0.0.46, must have already unzipped the full package before downloading and using this executable)
NOTE: THIS DOWNLOAD DOES NOT INCLUDE THE LIBRARIES REQUIRED TO RUN THE POSTGRESQL FEATURES
EQ2Log_update.zip (updated May 5th 2008)
1. Item information editor.
2. Add a quick loot search with the ability to send to the windows clipboard
/waypoint xxx,xxx,xxx for the mob you select.
3. Add the ability to send item links to the windows clipboard.
Future Additions:
1. Mob information editor.
2. A whole mess of stuff to do with tradeskills that I haven't decided what
I need to do with yet.
Latest patch notes: (May 6th, 2008 - build 1.0.0.46)
1. Raid Stats - you will need to enable logging of where a mob dies inside
eq2 for the start time of the raid to populate correctly.
2. Auto save all options to registry except chat filters
3. Fixed playername on sales data
4. Default database selection
5. Fixed auto archive time window
6. Fixed couple misc errors
7. If you restore the app from the tray while in auto archive mode it shouldn't
minimize the window to the tray anymore on it's interval for checking to see
if it should archive your logs.
8. Archive time window should actually function correctly now.
Patch notes: (March 24th, 2008 - build 1.0.0.45)
1. Various bug fixes (don't ask it's been over a month of working on stuff,
so I forgot some of them)
2. Mob Locator added Tools > Quick Search > Mob Locator
3. Improved storage for PostgreSQL.
4. Normalized the structures of some tables.