I loved this addon. It makes a great way for my guild to keep track of its history. We are small, not DKP-oriented, and like to have a record of where things went. I've missed it sorely. =)
I make absolutely no promises on release time, total feature set, or even completion at this point, but I will say that I've been working on a version as well. I want to reiterate, I'm not trying to get people's hopes up because my time is pretty hectic.
As a build parameter, at this point, I've taken some of the suggestions put forth for the new version release that Polo asked for, and have begun writing a new 1.7.3 addon borrowing some from the original code and making a lot of changes. I am using the
MLdkp and EQdkp modified tracker as a starting point, though a considerable amount of my data is from the older EQdkp mod, and even a few from the original CTRaidtracker. It will be an interesting ride.
What I've put in the framework so far (not finished code, but framework):
- Code: Select all
Overall:
o Rebuild of the parsing engine to allow "collation" of data from multiple uploaders.
o Addition of an Administrator menu using the new password features of the 1.7x line.
o Configuration variables contained within the administration menu.
o Changes to the overall usability and internal linking:
* Clicking on a name will show their loot history.
* Clicking on an item will show its drop history, and who got it.
Admin Menu:
o Manage people allowed to upload
o Manage which encounter data is stored and/or viewed
o Delete a raid and its associated data (for reupload)
o Mark a raid as "hidden", to remove it and its data from the overall list.
* I may do this as a class, like "hide all outdoor encounters" as well,
it depends how much time I have.
I have not yet decided whether to add the ability to add items or raids by hand. It can be done, but really, without a search and retrieve feature, adding items is a bit of a pain for people. (You'd need to have the raw item ID from inside the game) This is time intensive, and not my first goal.
Data collation is a problematic thing. There are some stumbling blocks. First, it seems that raid time is stored off the local machine clock (or at least used to be), rather than the server time. I'm not sure if this is an easy change, but I plan to email the devs of the ML/EQ addon and ask. I do not know LUA, even if I can puzzle out some of the functions.
I had originally intended to work out a "margin of time" that multiple uploaders data to the same zone would end up in the same raid. (IE: If two uploaders send up data with similar bosses, one boss missing from new data incoming, and it's within a window of 4 hours, they are the same raid, add them.) This method, however, has a couple holes: Guilds that run multiple raids simultaneously (like Karazhan raids for many guilds), or dungeon runs on two sides of a reset. It's something that I'll need to address. If anyone has any good ideas, let me know.
Anyway, this is longer than I intended. Just wanted people to know there's others out here missing it, and trying to find time to remedy the loss, knowing Polo is so swamped in RL. =)
G.