Old News:
Friday February 15th, 2008:
So I'm almost done with the mob locator. I need to write the stuff for MySQL and PostgreSQL still, but it's working pretty well. It will allow you to put in your current coordinates then update the distance of all the displayed mobs and order them by the closest to you. It will also copy the command to set a waypoint for the selected mob in game to the windows clipboard for easy access to waypoints while playing.
Monday February 13th, 2008:
Fixed all the stuff noted below, as well as fixed an oddity with the tray icon popping up the popup menu multiple times or showing it for no reason.
Monday January 21st, 2008:
After a little feedback from a friend on usage there are a few things I'm going to have to address this week and probably next:
1. Auto Archive time editors are behaving badly with a clean set of options.
2. Visual Query Builder is taking an access violation when opening a query then switching datasource to something else.
3. I need to do something to get the temp tables created before opening the Visual Query Builder if there is a log loaded, otherwise disable the ability to select temporary tables as a datasource from the Visual Query Builder.
4. Make the "filter" button and chat filter menu item more clear that it only affects chat data.
5. The program is missing some loot data for stuff that is looted and assigned by the group leader, rather than using lotto or free for all looting options.
6. Need to add the name of the person who looted an item to the loot data.I will be adding a quick mob search with the ability to send to the windows clipboard /waypoint xxx,xxx,xxx for the mob you select so it's easy to paste into EQ2 to track down mobs. This will use the same logic that the walkthrough creation part of the program uses for finding all unique locations within 30 meters of each other so that you don't have a million locations to pick from when you're looking for a particular mob. Eventually I'll add the same thing for a quick loot search. It will display mobs that drop a particular item and copy the waypoints for the mobs to the windows clipboard for pasting into the game. I will probably be adding the ability to send an item link to the clipboard as well for any items you may have stored.
Friday January 18th, 2008:
So it seems that the BDE freespace bug has popped up. See this article for an explanation of it: http://qc.borland.com/wc/qcmain.aspx?d=7089
This only affects the local storage of data for the most part, I saw this happen to my installation last night. I was hoping it wouldn't be an issue since I've only seen it happen when having your Paradox NET file specified on a network location. I've put in a fix for it and should be good now. If you are getting "Insufficient Disk Space" when trying to store your data locally (not using MySQL or PostgreSQL) then go ahead and download a new version of the log processor.
Thursday January 17th, 2008:
Added visual query builder with exports for Excel, HTML, Word, RTF and comma delimited. Fixed a few bugs and reorganized some of the interface. I will probably not be making any more updates unless someone reports a bug for a while, I need to get around to updating the help files.
Wednesday December 19th, 2007:
Seems adding the sales and mail storage in the local storage procedures broke some stuff with aligning items and mobs. It's fixed.
Thursday December 6st, 2007:
Finished the PostgreSQL portion of sales and mail data storage. I also revamped the realignment of item ids on mail, sales and loot data so that it works better. The way the whole system works, at the time of processing a log file unique ids are assigned to every record of the given datatype. That includes items, chat, mail etc. Items get a unique numeric id in order to maintain relations if some of the data about the item that would usually uniquely identify it is changed. When pushing the data to permanent storage, the ids have to be reassigned for items that have already been stored. So the procedures that do this needed a little tweaking and a bit of stuff had to be restructured since the code that realigned the item ids was only written to work on loot data. Also fixed some issues that no one has reported yet, but could cause the program to terminate unexpectedly. I also added a time window for archiving data so that when your log data is also stored to a database during archival it doesn't interfere with anything since it can be processor intensive.
Wednesday November 21st, 2007:
MySQL storage of mail and sales data finalized. There were also some bugs where items were still not getting aligned correctly in a new update on loot, mail and sales data, that's been fixed now as well. Still seeing a key violation when using the local storage method when auto archiving. Haven't tracked that one down since the machine I've been testing it on does not have a development environment installed. I've been testing it that way in order to ensure it will work on machines that don't have the Borland Database Engine installed in any form. I'm not sure if it's just particular to just one log file from my installation of EQ2, the computer, the BDE installation or some random error. I haven't been able to reproduce it in my development environment so if any of you get an error message that pops up saying "Key Violation" please let me know.
I'm planning on implementing some sort of scheduling for archiving log files other than what has already been designed. Probably try using the Windows Task Scheduler instead of keeping the program running, or at least specifying a time window in which to perform the auto archiving of your log files. Granted the program shuts itself down when EQ2 or the Launchpad is detected in memory, but due to the intensive nature of some of the archival procedures, I think I want to add the option of only doing it during a specific time window.
Sunday November 18th, 2007:
Bugs with the storage of log data to databases during the auto archive process have been fixed.
Friday November 16th, 2007:
Bugs with the storage of MySQL and PostgreSQL, and Mob ID assignments fixed. Mail storage for MySQL also added. Let me know if there's anything weird while processing. I also noticed that large numbers of records being pushed to PostgreSQL will take longer than MySQL, if the program looks unresponsive while storing data to PostgreSQL, just be patient, it will finish, I promise :P
Wednesday November 14th, 2007:
Discovered some possible bugs with storage under MySQL and PostgreSQL, it only affects trying to store data for the second time. Also found a bug where Mob IDs are not populating correctly under certain conditions. It seems that if you end up getting a loot logged without the prior kill of the mob, the mob ID is not being generated properly. I thought I had fixed that a month or two ago, but it seems to have surfaced again, so I'll be working on that and hopefully have both issues taken care of by the end of the week.
Monday November 12th, 2007:
Local storage of sales data added..
Friday November 9th, 2007:
Have mail processing and storage completed for just the local storage method. MySQL and PostgreSQL storage coming sometime next week. Sales data processing finished, exports to Excel, but does not store yet. See downloads for latest version with both mail and sales data included. It seems to be working ok, tested it on a few characters and all seems well. Let me know if you have issues.
Monday November 5th, 2007:
Been working on sales and mail processing. Should have an update out for both by the end of the week. Currently doing the storage of the mail and sales data.
Tuesday October 30th, 2007:
Bleh, seems I forgot to push the update I had ready on the 17th. PostgreSQL support now enabled! w00t! Please download the full version to be able to use PostgreSQL features since there are libraries that must be present in the executable's directory to work, and you could probably use a new help file anyways ;-)
Friday October 5th, 2007:
Oops, commented out 1 line of really important code. If you downloaded it yesterday, please get the update today so it will actually process the data :P
New version released, some fixes for some oddness and the MySQL support is now complete. Added some tweaks to the GUI and moved some code between units as well. If you encounter any errors during startup just ignore them, go into the parsing options, save them, then select "Set current options as default" from the main window and it shouldn't happen again.
I've fixed the problem with chat parsing, there's still just a tentative fix published (same one I tossed up there Friday). I'm working on how to deal with the new options added and older clients. Part of the issue is getting the new options in the right sections in the registry, and I think it will be an issue later as well, so I'm trying to come up with a catch-all for reorganizing the default options in the registry when there's an update to them. I'll probably have something done with that in the next few days, then I will release a new version that has the added filtering and new parsing options for OOC, RaidSay and Shout.
Today I discovered a number of inconsistencies and changes to the way chat is logged that happened sometime between the last time I touched the chat portion of the program and the last update pushed out by SOE to EQ2. While adding OOC, Shout, and RaidSay to the parsing procedures I discovered a lot of the data parsed was getting mis-categorized due to changes in spacing between commas and double quotation marks. I've been working on getting it fixed up today and should have a new patch out to fix any mis-categorizations/dropping of some chat info. There is a tentative release that should work ok out right now, I expect to be confident in the fixes by Monday.
Patch notes: (February 13th, 2008 - build 1.0.0.44)
1. Auto Archive time editors behaving badly with a clean set of options fixed.
2. Visual Query Builder taking an access violation when opening a query then
switching datasource to something else fixed.
3. Temp tables created before opening the Visual Query Builder if there is a
log loaded, otherwise the ability to select temporary tables as a datasource
from the Visual Query Builder is disabled.
4. Made the "filter" button and chat filter menu item clear that it
only affects chat data.
5. Fixed loot data for stuff that is looted and assigned by the group leader,
rather than using lotto or free for all looting options.
6. Added the name of the person who looted an item to the loot data.
7. Fixed some oddities with the tray icon when running in archive mode.
Patch notes: (January 18th, 2008 - build 1.0.0.43)
1. Fixed a bug with the BDE reporting insufficient disk space when your free space is divisible by 4.
Patch notes: (January 17th, 2008 - build 1.0.0.42)
1. Fixed a bug with the alignment of item IDs new items storing the data using
local storage.
2. Added a visual query builder with a number of additional export formats.
Patch notes: (December 19th, 2007 - build 1.0.0.41)
1. Fixed a bug with the alignment of item and mob IDs on loot data when storing
the data using local storage.
Patch notes: (December 6th, 2007 - build 1.0.0.40)
1. PostgreSQL storage of mail and sales data complete.
2. Bug with realigning item IDs on loot, mail and sales data in a new update
fixed.
3. Fatal bug where connecting to a MySQL or PostgreSQL database that isn't available
during the storing of data caused an access violation that terminated the program
has been fixed.
4. Time window for archiving data has been implemented.
Patch notes: (November 21st, 2007 - build 1.0.0.39)
1. MySQL storage of mail and sales data complete.
2. Bug with realigning item IDs on loot, mail and sales data in a new update
fixed.
Patch notes: (November 18th, 2007 - build 1.0.0.38)
1. A bug with storing log data to databases during auto archiving has been fixed.
Patch notes: (November 16th, 2007 - build 1.0.0.37)
1. Storage of mail data via MySQL finished.
2. Fixed some bugs with storing mob and loot data where item IDs and mob IDs
would get misaligned, or just not store records all together.
3. Fixed mob IDs being assigned random large integers, rather than a properly
generated ID.
Patch notes: (November 12th, 2007 - build 1.0.0.36)
1. Storage of sales data via local storage method (BDE) finished.
Patch notes: (November 9th, 2007 - build 1.0.0.35)
1. Mail and sales data processing completed, with exports to Excel.
2. Storage of mail data via local storage method (BDE) finished.
Patch notes: (October 30th, 2007 - build 1.0.0.34)
1. Completed the PostgreSQL additions. Please download the full thing for the
updated help file and to also get the PostgreSQL libraries required to use the
PostgreSQL storage stuff.
2. Various bug fixes, don't remember all of them ;-)
3. Updated help file.
Patch notes: (October 4th, 2007 - build 1.0.0.32)
1. Completed the MySQL additions.
2. Finalized fixes for chat processing.
3. Finalized chat categories for OOC, Shout and RaidSay.
4. Added filtering for OOC, Shout and RaidSay as well as text replacement options
under the parsing options section.
5. Fixed some issues with the auto archive and extracting and storing the data
during the archival process.
6. Compiled without the "DEBUG" compiler directive so the auto archiving
stuff actually schedules to start the program with windows. I also turned off
including debugging symbols and information on this compile which makes the
executable a little smaller usually. (I always forget to remove compiler directives
and take out the debugging info from the executable lol.)
Patch notes: (September 28th, 2007 - build 1.0.0.27)
1. Fixed a number of issues with categorization of chat to be more reliable.
2. Found a few memory leaks and squished them.
3. Added chat categories for OOC, Shout and RaidSay. (will add filtering for
them in the next release)
4. Fixed issues with lookup of the target of chat's type.
Patch notes: (September 27th, 2007 - build 1.0.0.24)
1. Added splitter to the Walkthrough Creation window between the list of items
and mobs.
2. Fixed with incorrectly assigning IDs to mobs that are presented from processing
loot where the mob has not been previously logged
3. Fixed issue with the "File" menu item in the parsed log window
where it would automatically prompt the user to save the parsed log file instead
of drop down the file menu.
4. Random access violations happening with the MySQL portion of the storage
engine.
5. Added MySQL to the Query Data portion of the software.
6. Added which database platform is in use to the query form, table structure
view and table data view windows.
7. Using any of the export functions or using the walkthrough creation before
the current log file has been parsed will now parse the current log file before
attempting to export data or open the walkthrough creation window.